PageSourceSearch

Site profile

berchtesgadener-anzeiger.de

Built with js-cookie 3.0.1, jquery 3.5.1, jquery-ui 1.14.2, lightbox2 2.12.0, fancybox 3.0.1, jquery-ui-dist 1.13.3, luckysheet 2.1.13, dygraphs 2.2.2, jquery-touchswipe 1.6.19, jquery-slim 3.0.0, slick-slider 1.8.2, tablesaw 3.1.2 and more. 5 pages and 13 stored files.

rank 548,549 14 libraries 0 identifiers 0 third-party hosts 0 crawls 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
js-cookie 3.0.1 2026-09-24
jquery 3.5.1 2026-09-24
jquery-ui 1.14.2 2026-09-24
lightbox2 2.12.0 2026-09-24
fancybox 3.0.1 2026-09-24
jquery-ui-dist 1.13.3 2026-09-24
luckysheet 2.1.13 2026-09-24
dygraphs 2.2.2 2026-09-24
jquery-touchswipe 1.6.19 2026-09-24
jquery-slim 3.0.0 2026-09-24
slick-slider 1.8.2 2026-09-24
tablesaw 3.1.2 2026-09-24
holderjs 2.9.9 2026-09-24
@commercelayer/drop-in.js 2.27.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

The stored pages and scripts reference no host outside berchtesgadener-anzeiger.de.

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 13) }. 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.berchtesgadener-anzeiger.de/REST/community/login/js?r=6ab55203237db js 2.8 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/REST/community/login/js?r=6ab51ad197751 js 2.8 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/REST/community/login/js?r=6ab5168725b07 js 2.8 KB 2026-09-24 current
https://data-80d2d17df3.berchtesgadener-anzeiger…/manager/base/es6/bundle.js js 62.2 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/REST/community/login/js?r=6ab5163d10dc0 js 2.8 KB 2026-09-24 current
https://data-80d2d17df3.berchtesgadener-anzeiger…/latest/bootstrap/loader.js js 739 B 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/REST/community/login/js?r=6ab5815246025 js 2.8 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/cms_mini…/javascript_1790251828.js js 566.6 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/region-u…kales-berchtesgadener-land.html html 78.7 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/kontakt.html html 22.2 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/abo-berc…sgadener-anzeiger/probeabo.html html 34 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/ html 99.6 KB 2026-09-24 current
https://www.berchtesgadener-anzeiger.de/abo-berc…/ihr-zeitungs-abo.html html 25.8 KB 2026-09-24 current

Timeline

No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.

Questions about berchtesgadener-anzeiger.de

How does PageSourceSearch know what berchtesgadener-anzeiger.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 berchtesgadener-anzeiger.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 berchtesgadener-anzeiger.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 berchtesgadener-anzeiger.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.