Site profile
landkreistag-bw.de
Built with jquery 3.6.0, immortal-db 1.1.0, slick-slider 1.8.2, slick-carousel-latest 1.9.0, @vitest/utils 5.0.2, @chakra-ui/theme 3.4.6. 4 pages and 44 stored files, last crawled 2026-10-02.
rank 1,154,698 6 libraries 0 identifiers 2 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 |
|---|---|---|
| jquery | 3.6.0 | 2026-10-02 |
| immortal-db | 1.1.0 | 2026-10-02 |
| slick-slider | 1.8.2 | 2026-10-02 |
| slick-carousel-latest | 1.9.0 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @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 landkreistag-bw.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 |
|---|---|---|
| code.jquery.com | script | view source |
| dashboard.stage.bio | script | 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
4 pages, 29 files, 626.5 KB; 5 libraries, 0 identifiers, 2 third-party hosts
5 libraries added
- @vitest/utils 5.0.2
- slick-slider 1.8.2
- immortal-db 1.1.0
- slick-carousel-latest 1.9.0
- jquery 3.6.0
2 third-party hosts added
29 files added
- https://www.landkreistag-bw.de/ html
- https://www.landkreistag-bw.de/special-pages/search html
- https://www.landkreistag-bw.de/social-media html
- https://www.landkreistag-bw.de/positionen html
- https://www.landkreistag-bw.de/typo3temp/assets/js/62b8391210.js?1706811810 js
- https://www.landkreistag-bw.de/typo3conf/ext/sli…/slick/slick.min.js?1628065453 js
- https://www.landkreistag-bw.de/typo3conf/ext/sli…/randomize.js?1628065453 js
- https://www.landkreistag-bw.de/typo3temp/assets/js/0537b384be.js?1706811810 js
- https://www.landkreistag-bw.de/typo3temp/assets/…s-assets-jscookie.js?1790927106 js
- https://www.landkreistag-bw.de/typo3temp/assets/…s-magnificpopupjs.js?1790927106 js
- https://www.landkreistag-bw.de/typo3temp/assets/…Js-script-script2.js?1790927106 js
- https://www.landkreistag-bw.de/typo3temp/assets/vhs-assets-slickJs.js?1790927106 js
- and 17 more
Questions about landkreistag-bw.de
- How does PageSourceSearch know what landkreistag-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 landkreistag-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 landkreistag-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 landkreistag-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.