PageSourceSearch

Site profile

hochsauerlandkreis.de

Built with @wix/design-system 1.328.0, lightgallery 2.9.0, vis-timeline 8.5.4, @vitest/utils 5.0.2, @dynamic-framework/ui-react 2.10.0, wc-datepicker 0.13.0. 5 pages and 10 stored files, last crawled 2026-10-02.

rank 449,432 6 libraries 0 identifiers 4 third-party hosts 1 crawl open the site

Technologies and libraries

Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.

LibraryVersionSeen
@wix/design-system 1.328.0 2026-10-02
lightgallery 2.9.0 2026-10-02
vis-timeline 8.5.4 2026-10-02
@vitest/utils 5.0.2 2026-10-02
@dynamic-framework/ui-react 2.10.0 2026-10-02
wc-datepicker 0.13.0 2026-09-24

Tracking, tag and verification IDs

No analytics property, tag manager container, pixel or site-verification token was found in the stored source.

Third-party hosts

Hosts outside hochsauerlandkreis.de that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.

HostLoaded asFound in
chat.humanizing.com script view source
dashboard.stage.bio script view source
translate-cdn.eye-able.com script view source
www.eye-able-cdn.com script view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 10) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

FileKindSizeCollectedVersions
https://www.hochsauerlandkreis.de/typo3conf/ext/…/Form.min.js?1787653028 js 76.8 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/typo3temp/asse…41bc061d272fd51b2.js?1788350803 js 16.2 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/typo3conf/ext/…/humanizing_init.js?1780388672 js 38 B 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/typo3temp/asse…e71b7392c2950db72.js?1781514297 js 135.3 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/typo3temp/asse…cdbe6236bf4671169.js?1781514297 js 8.9 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/hochsauerlandk…politik-und-verwaltung/beihilfe html 105.7 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/hochsauerlandk…/verkehrsordnungswidrigkeiten2 html 177 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/regionale-themen/unsere-oeffnungszeiten html 110.3 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/kontakt html 96.7 KB 2026-10-02 2026-10-02
https://www.hochsauerlandkreis.de/hochsauerlandkreis html 123.9 KB 2026-10-02 2026-10-02

Timeline

One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.

  1. first crawl

    5 pages, 10 files, 850.9 KB; 5 libraries, 0 identifiers, 4 third-party hosts

    5 libraries added
    • @vitest/utils 5.0.2
    • @dynamic-framework/ui-react 2.10.0
    • lightgallery 2.9.0
    • @wix/design-system 1.328.0
    • vis-timeline 8.5.4
    4 third-party hosts added
    10 files added

Questions about hochsauerlandkreis.de

How does PageSourceSearch know what hochsauerlandkreis.de is built with?
From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
How far back does the history of hochsauerlandkreis.de go?
To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
Can I see an older version of a script from hochsauerlandkreis.de?
Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
Which other websites use the same tracking IDs as hochsauerlandkreis.de?
Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.

Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.