Site profile
kloster-bad-wimpfen.de
Built with @accessible360/accessible-slick 1.0.1, volantis-static 0.0.1761982841160, jq-accordion 1.0.3, jpanel-menu 1.4.1. 5 pages and 21 stored files, last crawled 2026-10-09.
rank 14,771,443 4 libraries 0 identifiers 5 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 |
|---|---|---|
| @accessible360/accessible-slick | 1.0.1 | 2026-10-09 |
| volantis-static | 0.0.1761982841160 | 2026-10-09 |
| jq-accordion | 1.0.3 | 2026-10-09 |
| jpanel-menu | 1.4.1 | 2026-10-09 |
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 kloster-bad-wimpfen.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 |
| www.openstreetmap.org | iframe | view source |
| www.w3.org | connect | view source |
| www.youtube-nocookie.com | connect | view source |
| www.youtube.com | iframe 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, 21 files, 2.8 MB; 4 libraries, 0 identifiers, 5 third-party hosts
4 libraries added
- volantis-static 0.0.1761982841160
- jpanel-menu 1.4.1
- @accessible360/accessible-slick 1.0.1
- jq-accordion 1.0.3
6 third-party hosts added
21 files added
- https://www.kloster-bad-wimpfen.de/ html
- https://www.kloster-bad-wimpfen.de/stiftskirche-st-peter.html html
- https://www.kloster-bad-wimpfen.de/uebernachten-tagen.html html
- https://www.kloster-bad-wimpfen.de/hauptmenue/kurse-veranstaltungen.html html
- https://www.kloster-bad-wimpfen.de/kontakt-und-service/ihre-ansprechpartner.html html
- https://www.kloster-bad-wimpfen.de/typo3temp/ass…0b899ce98dad6-min.js?1791490739 js
- https://www.kloster-bad-wimpfen.de/typo3temp/ass…baef5a12ec678-min.js?1791490739 js
- https://www.kloster-bad-wimpfen.de/_assets/56a96…/slick.min.js?1759194403 js
- https://www.kloster-bad-wimpfen.de/_assets/a0770…/toTopButton.js?1782908651 js
- https://www.kloster-bad-wimpfen.de/_assets/56a96…/jquery.accordion.js?1759194403 js
- https://www.kloster-bad-wimpfen.de/_assets/56a96…/isOnScreen.min.js?1759194403 js
- https://www.kloster-bad-wimpfen.de/_assets/a0770…/tobii.min.js?1759194403 js
- and 9 more
Questions about kloster-bad-wimpfen.de
- How does PageSourceSearch know what kloster-bad-wimpfen.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 kloster-bad-wimpfen.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 kloster-bad-wimpfen.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 kloster-bad-wimpfen.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.