How does PageSourceSearch know what dj-fischer-spezial.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 dj-fischer-spezial.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 dj-fischer-spezial.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 dj-fischer-spezial.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.

Site profile

dj-fischer-spezial.de

Built with gtm, gtag, @vitest/utils 5.0.2. 5 pages and 6 stored files, last crawled 2026-10-04.

rank 9,994,521 3 libraries 7 identifiers 7 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-04
gtag		2026-10-04
@vitest/utils	5.0.2	2026-10-04

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
Bing site verification (Microsoft)	96A7AE2BED756144C48C74F9A310C03C	view source
Google site verification (Google)	MRZmpmX-IlItJHZqDsGIQZ0iYvuxrw0-d_OUEjx4Ro4	view source
Google Tag Manager container (Google)	GTM-KBSSNKQ	view source
Pinterest site verification (Pinterest)	4d57b70b48c358579c54a8e5f7cc31ad	view source
Pinterest site verification (Pinterest)	8f74ed0d77eeb8311c64cfe592a1d1a6	view source
Pinterest site verification (Pinterest)	df0a5772ef90da16109258a37162bfba	view source
Universal Analytics property id (Google)	UA-131759196-1	view source

Third-party hosts

Hosts outside dj-fischer-spezial.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
browser.sentry-cdn.com	script	view source
cdn.consentmanager.mgr.consensu.org	stylesheet	view source
cdn.pagebooster.net	script	view source
dlnil54eooeso.cloudfront.net	script	view source
static.parastorage.com	script stylesheet	view source
wixwebsitespeedy8.b-cdn.net	script	view source
www.googletagmanager.com	script iframe	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 6) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

File	Kind	Size	Collected	Versions
https://www.googletagmanager.com/gtag/js?id=UA-131759196-1	js library	not fetched	2026-10-04	2026-10-04
https://www.dj-fischer-spezial.de/kontakt	html	914.1 KB	2026-10-04	2026-10-04
https://www.dj-fischer-spezial.de/about	html	996.4 KB	2026-10-04	2026-10-04
https://www.dj-fischer-spezial.de/post/planung-i…em-richtigen-hochzeit-dj-ruegen	html	1.1 MB	2026-10-04	2026-10-04
https://www.dj-fischer-spezial.de/blog	html	1.4 MB	2026-10-04	2026-10-04
https://www.dj-fischer-spezial.de/	html	1.4 MB	2026-10-04	2026-10-04

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.

2026-10-04 first crawl

5 pages, 6 files, 5.7 MB; 3 libraries, 7 identifiers, 7 third-party hosts
3 libraries added
- @vitest/utils 5.0.2
- gtm
- gtag
7 identifiers added
- GTM-KBSSNKQ Google Tag Manager container
- UA-131759196-1 Universal Analytics property id
- MRZmpmX-IlItJHZqDsGIQZ0iYvuxrw0-d_OUEjx4Ro4 Google site verification
- 96A7AE2BED756144C48C74F9A310C03C Bing site verification
- 4d57b70b48c358579c54a8e5f7cc31ad Pinterest site verification
- 8f74ed0d77eeb8311c64cfe592a1d1a6 Pinterest site verification
- df0a5772ef90da16109258a37162bfba Pinterest site verification
9 third-party hosts added
6 files added

Questions about dj-fischer-spezial.de

How does PageSourceSearch know what dj-fischer-spezial.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 dj-fischer-spezial.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 dj-fischer-spezial.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 dj-fischer-spezial.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.