Site profile
bezirk-niederbayern.de
Built with magnific-popup 1.2.0, flexslider 2.7.2, vide 0.5.1, @vitest/utils 5.0.2, remodal 1.1.1, @chakra-ui/theme 3.4.6. 6 pages and 14 stored files, last crawled 2026-10-02.
rank 1,118,480 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.
| Library | Version | Seen |
|---|---|---|
| magnific-popup | 1.2.0 | 2026-10-02 |
| flexslider | 2.7.2 | 2026-10-02 |
| vide | 0.5.1 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| remodal | 1.1.1 | 2026-09-25 |
| @chakra-ui/theme | 3.4.6 | 2026-09-25 |
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 bezirk-niederbayern.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.
| Host | Loaded as | Found in |
|---|---|---|
| f1-eu.readspeaker.com | script | view source |
| vecta.io | connect | view source |
| www.eye-able-cdn.com | connect | view source |
| www.w3.org | connect | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
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.
-
first crawl
5 pages, 13 files, 270.8 KB; 4 libraries, 0 identifiers, 4 third-party hosts
4 libraries added
- @vitest/utils 5.0.2
- vide 0.5.1
- magnific-popup 1.2.0
- flexslider 2.7.2
4 third-party hosts added
13 files added
- https://bezirk-niederbayern.de/ html
- https://www.bezirk-niederbayern.de/presse/presse…rfer-kreistag-rede-und-antwort/ html
- https://www.bezirk-niederbayern.de/index.php?id=132 html
- https://www.bezirk-niederbayern.de/leichte-sprache/ html
- https://www.bezirk-niederbayern.de/bezirk/ html
- https://www.bezirk-niederbayern.de/fileadmin/tem…/jquery.min.js?1508832097 js
- https://www.bezirk-niederbayern.de/fileadmin/tem…/scripts/scripts.js?1699257667 js
- https://www.bezirk-niederbayern.de/fileadmin/tem…/jquery.cookie.js?1548172203 js
- https://www.bezirk-niederbayern.de/fileadmin/tem…/scripts/eyeAbleInclude.js js
- https://www.bezirk-niederbayern.de/typo3conf/ext…agnific-popup.min.js?1698739939 js
- https://www.bezirk-niederbayern.de/typo3conf/ext…r-isImageFile.min.js?1698739939 js
- https://www.bezirk-niederbayern.de/typo3conf/ext…ry.flexslider-min.js?1698742080 js
- and 1 more
Questions about bezirk-niederbayern.de
- How does PageSourceSearch know what bezirk-niederbayern.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 bezirk-niederbayern.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 bezirk-niederbayern.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 bezirk-niederbayern.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.