Site profile
landkreis-bautzen.de
Built with json-db-admin 0.0.1, stickyfilljs 2.1.0, is-in-viewport 3.0.4. 5 pages and 28 stored files, last crawled 2026-10-02.
rank 1,150,948 3 libraries 1 identifier 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 |
|---|---|---|
| json-db-admin | 0.0.1 | 2026-10-02 |
| stickyfilljs | 2.1.0 | 2026-10-02 |
| is-in-viewport | 3.0.4 | 2026-09-25 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Facebook domain verification (Meta) | peju775thqfoh904u5a3qtbgr2kfx9 | view source |
Third-party hosts
Hosts outside landkreis-bautzen.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 |
|---|---|---|
| fs.egov.sachsen.de | iframe | view source |
| userlike-cdn-widgets.s3-eu-west-1.amazonaws.com | script | view source |
| wks-xm-eko.xima.de | stylesheet | 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, 28 files, 648.1 KB; 2 libraries, 1 identifier, 4 third-party hosts
2 libraries added
- json-db-admin 0.0.1
- stickyfilljs 2.1.0
1 identifier added
- peju775thqfoh904u5a3qtbgr2kfx9 Facebook domain verification
4 third-party hosts added
28 files added
- https://www.landkreis-bautzen.de/ html
- https://www.landkreis-bautzen.de/news.php html
- https://www.landkreis-bautzen.de/index.php html
- https://www.landkreis-bautzen.de/kontakt.php html
- https://www.landkreis-bautzen.de/notrufe.php html
- https://www.landkreis-bautzen.de/resources/maste…/loadcomponent.js?v=1.0.0 js
- https://www.landkreis-bautzen.de/resources/master/base.es6.js js
- https://www.landkreis-bautzen.de/resources/master/image/image.es6.js js
- https://www.landkreis-bautzen.de/resources/master/icon/icon.es6.js js
- https://www.landkreis-bautzen.de/resources/master/anchor/anchor.es6.js js
- https://www.landkreis-bautzen.de/resources/master/header/header.es6.js js
- https://www.landkreis-bautzen.de/resources/master/footer/footer.es6.js js
- and 16 more
Questions about landkreis-bautzen.de
- How does PageSourceSearch know what landkreis-bautzen.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 landkreis-bautzen.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 landkreis-bautzen.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 landkreis-bautzen.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.