Site profile
voehringen-bw.de
Built with jquery 1.4.2, bxslider 4.2.17, dzxstatic 3.4.20211231, @vitest/utils 5.0.2, super-slide 2.1.4, h8k-components 2.2.0. 5 pages and 13 stored files, last crawled 2026-10-02.
rank 1,508,245 6 libraries 1 identifier 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 | 1.4.2 | 2026-10-02 |
| bxslider | 4.2.17 | 2026-10-02 |
| dzxstatic | 3.4.20211231 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| super-slide | 2.1.4 | 2026-10-02 |
| h8k-components | 2.2.0 | 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 |
|---|---|---|
| Matomo site id (Matomo) | piwikcm05.cmcitymedia.de#64 | view source |
Third-party hosts
Hosts outside voehringen-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 |
|---|---|---|
| components.cross-7.de | script | view source |
| www.adobe.com | 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, 346.1 KB; 5 libraries, 1 identifier, 2 third-party hosts
5 libraries added
- @vitest/utils 5.0.2
- dzxstatic 3.4.20211231
- bxslider 4.2.17
- super-slide 2.1.4
- jquery 1.4.2
1 identifier added
- piwikcm05.cmcitymedia.de#64 Matomo site id
2 third-party hosts added
13 files added
- https://www.voehringen-bw.de/de/startseite html
- https://www.voehringen-bw.de/de/leben-wohnen/buergerinfo-news html
- https://www.voehringen-bw.de/de/gemeinde-daten/inhalt-hilfe/suche html
- https://www.voehringen-bw.de/de/gemeinde-daten/grusswort html
- https://www.voehringen-bw.de/de/rathaus-gemeinderat/rathaus-aktuell html
- https://www.voehringen-bw.de/fileadmin/templates…/jquery-1.5.1.min.js?1752492158 js
- https://www.voehringen-bw.de/fileadmin/templates…jquery.easing.1.3.js?1752492158 js
- https://www.voehringen-bw.de/fileadmin/templates…/stylesheetToggle.js?1752492158 js
- https://www.voehringen-bw.de/fileadmin/templates/js/dropdown.js?1752492158 js
- https://www.voehringen-bw.de/fileadmin/templates/js/home.js?1752492158 js
- https://www.voehringen-bw.de/fileadmin/templates/js/page.js?1752492158 js
- https://www.voehringen-bw.de/typo3temp/assets/js/5508b6c4f0.js?1681895620 js
- and 1 more
Questions about voehringen-bw.de
- How does PageSourceSearch know what voehringen-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 voehringen-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 voehringen-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 voehringen-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.