Site profile
landesarchiv-bw.de
Built with @wix/design-system 1.328.0, cookieconsent 3.1.1, @accessible360/accessible-slick 1.0.1, @flagship.io/js-sdk 5.2.2, dashjs 5.2.1, klaro 0.7.21, @reachfive/identity-core 1.42.0, configcat-js 9.6.1, kore-web-sdk 11.28.1, reverie-stt-sdk 0.24.0, pg-calendar 1.4.31, @json-editor/json-editor 2.17.2 and more. 5 pages and 9 stored files.
rank 430,207 15 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.
| Library | Version | Seen |
|---|---|---|
| @wix/design-system | 1.328.0 | 2026-09-24 |
| cookieconsent | 3.1.1 | 2026-09-24 |
| @accessible360/accessible-slick | 1.0.1 | 2026-09-24 |
| @flagship.io/js-sdk | 5.2.2 | 2026-09-24 |
| dashjs | 5.2.1 | 2026-09-24 |
| klaro | 0.7.21 | 2026-09-24 |
| @reachfive/identity-core | 1.42.0 | 2026-09-24 |
| configcat-js | 9.6.1 | 2026-09-24 |
| kore-web-sdk | 11.28.1 | 2026-09-24 |
| reverie-stt-sdk | 0.24.0 | 2026-09-24 |
| pg-calendar | 1.4.31 | 2026-09-24 |
| @json-editor/json-editor | 2.17.2 | 2026-09-24 |
| ovenplayer | 0.10.54 | 2026-09-24 |
| @recogito/annotorious | 2.7.14 | 2026-09-24 |
| @genpact/genome.mfe.solidify-app | 3.15.1 | 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 landesarchiv-bw.de.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://www.landesarchiv-bw.de/assets/js/analytics.js | js | 1.2 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/assets/encore/197.3cb5d020.js | js | 912.2 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/assets/encore/javascript.0697ef84.js | js | 16.5 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/assets/encore/runtime.9ffcc849.js | js | 1.5 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/de/aktuelles/presse---medien/67179 | html | 82.6 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/de/kontakt/67157 | html | 62.7 KB | 2026-09-24 | current |
| https://www2.landesarchiv-bw.de/ofs21/index.php | html | not fetched | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/de/recherche/recherchehilfen/finden-lernen/60705 | html | 87 KB | 2026-09-24 | current |
| https://www.landesarchiv-bw.de/ | html | 123.4 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 landesarchiv-bw.de
- How does PageSourceSearch know what landesarchiv-bw.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 landesarchiv-bw.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 landesarchiv-bw.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 landesarchiv-bw.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.