Site profile
ammerland-touristik.de
Built with gtm, cookiebot. 5 pages and 42 stored files, last crawled 2026-10-02.
rank 1,209,173 2 libraries 1 identifier 4 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 |
|---|---|---|
| gtm | 2026-10-02 | |
| cookiebot | 2026-10-02 |
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 |
|---|---|---|
| Google Tag Manager container (Google) | GTM-NZBRVGL | view source |
Third-party hosts
Hosts outside ammerland-touristik.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 |
|---|---|---|
| api-oa.com | connect | view source |
| consent.cookiebot.com | script | view source |
| resc.deskline.net | script | view source |
| web5.deskline.net | 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
5 pages, 36 files, 1 MB; 2 libraries, 1 identifier, 4 third-party hosts
2 libraries added
- gtm
- cookiebot
1 identifier added
- GTM-NZBRVGL Google Tag Manager container
4 third-party hosts added
36 files added
- https://www.ammerland-touristik.de/ html
- https://www.ammerland-touristik.de/region-urlaubsorte html
- https://www.ammerland-touristik.de/region-urlaubsorte/apen html
- https://www.ammerland-touristik.de/region-urlaubsorte/bad-zwischenahn html
- https://www.ammerland-touristik.de/region-urlaubsorte/edewecht html
- https://www.ammerland-touristik.de/dist/js/ndsbase/document-BuSKHmje.js js
- https://www.ammerland-touristik.de/dist/js/ndsbase/background-focus-bruEKyTc.js js
- https://www.ammerland-touristik.de/dist/js/ndsbase/srcset-focus-Bsz-zXnK.js js
- https://www.ammerland-touristik.de/dist/js/ndsbase/svg-loader-DP8peAPO.js js
- https://www.ammerland-touristik.de/dist/js/ndsbase/lazyimages-OPvpAfRN.js js
- https://www.ammerland-touristik.de/dist/js/ndspa…/data-layer-Dky5-B0G.js js
- https://www.ammerland-touristik.de/dist/js/ndspa…/simplelightbox-ZmObMCDz.js js
- and 24 more
Questions about ammerland-touristik.de
- How does PageSourceSearch know what ammerland-touristik.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 ammerland-touristik.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 ammerland-touristik.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 ammerland-touristik.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.