Site profile
kreis-soest.de
Built with js-cookie 3.0.8, lightgallery 2.9.0, vanilla-cookieconsent 3.1.0, @vitest/utils 5.0.2, @dynamic-framework/ui-react 2.10.0, @unhead/vue 3.4.1. 5 pages and 30 stored files, last crawled 2026-10-02.
rank 583,542 6 libraries 0 identifiers 3 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 |
|---|---|---|
| js-cookie | 3.0.8 | 2026-10-02 |
| lightgallery | 2.9.0 | 2026-10-02 |
| vanilla-cookieconsent | 3.1.0 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @dynamic-framework/ui-react | 2.10.0 | 2026-10-02 |
| @unhead/vue | 3.4.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
Hosts outside kreis-soest.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 |
| prod-chat-app.neurabot.neuraflow.de | script | 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, 30 files, 843.3 KB; 5 libraries, 0 identifiers, 3 third-party hosts
5 libraries added
- @vitest/utils 5.0.2
- @dynamic-framework/ui-react 2.10.0
- lightgallery 2.9.0
- js-cookie 3.0.8
- vanilla-cookieconsent 3.1.0
3 third-party hosts added
30 files added
- https://www.kreis-soest.de/ html
- https://www.kreis-soest.de/start/startseite/kontakt/kontakt html
- https://www.kreis-soest.de/ansprechpartner-a-z-ausgabe/ansprechpartner-a-z html
- https://www.kreis-soest.de/politik-verwaltung/ve…=karrierepictogramm html
- https://www.kreis-soest.de/verkehr-wirtschaft/ve…/kennzeichen/wunschkennzeichen html
- https://www.kreis-soest.de/typo3conf/ext/configk…/Dist/console.js?1769606853 js
- https://www.kreis-soest.de/typo3conf/ext/configk…/js/bootstrap.min.js?1756173047 js
- https://www.kreis-soest.de/typo3conf/ext/configk…/lightgallery.min.js?1759308355 js
- https://www.kreis-soest.de/typo3conf/ext/configk…/zoom/lg-zoom.min.js?1759308355 js
- https://www.kreis-soest.de/typo3conf/ext/configk…/lg-autoplay.min.js?1759308355 js
- https://www.kreis-soest.de/typo3conf/ext/configk…/lg-thumbnail.min.js?1759308355 js
- https://www.kreis-soest.de/typo3conf/ext/configk…ghtgallery_config.js?1780923858 js
- and 18 more
Questions about kreis-soest.de
- How does PageSourceSearch know what kreis-soest.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 kreis-soest.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 kreis-soest.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 kreis-soest.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.