How does PageSourceSearch know what die-tagespost.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 die-tagespost.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 die-tagespost.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 die-tagespost.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

die-tagespost.de

Built with gtm, lodash 1.4.4, @vitest/utils 5.0.2, @unhead/vue 3.4.1. 5 pages and 10 stored files, last crawled 2026-10-02.

rank 584,881 4 libraries 6 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
gtm		2026-10-02
lodash	1.4.4	2026-10-02
@vitest/utils	5.0.2	2026-10-02
@unhead/vue	3.4.1	2026-09-24

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
AdSense publisher id (Google)	ca-pub-6948820955633789	view source
AdSense publisher id (Google)	ca-pub-7152402105127515	view source
Facebook app id (Meta)	360442021262126	view source
Google site verification (Google)	EU_vDdKuw7a6LoePGYolNqMf-lBiazzaWUY81udqqV4	view source
Google site verification (Google)	ieZFAE-dZbgowd2vjmAMpugdRWDfvFSVy0jDqfG8PyM	view source
Google Tag Manager container (Google)	GTM-TN7KJJD	view source

Third-party hosts

Hosts outside die-tagespost.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
code.etracker.com	script	view source
pagead2.googlesyndication.com	script	view source
securepubads.g.doubleclick.net	script	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 10) }. 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.die-tagespost.de/_/scripts/fcmsuser/…?version=1790762230	js	6.5 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/_fWS/jsoninplainout…/init.js?version=1790762230	js	55.7 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/currentUser.js	js	227 B	2026-10-02	current
https://www.die-tagespost.de/mein-profil/registrieren/	html	92.4 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/mein-profil/passwort-vergessen/	html	87 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/mein-profil/merkliste/	html	87.8 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/login/	html	97.5 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/	html	271.3 KB	2026-10-02	2026-10-02
https://www.die-tagespost.de/_/scripts/fcmsuser/…?version=1786009017	js	6.5 KB	2026-09-24	current
https://www.die-tagespost.de/_fWS/jsoninplainout…/init.js?version=1786009017	js	55.7 KB	2026-09-24	current

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-02 first crawl

5 pages, 8 files, 698.4 KB; 3 libraries, 6 identifiers, 3 third-party hosts
3 libraries added
- @vitest/utils 5.0.2
- gtm
- lodash 1.4.4
6 identifiers added
- GTM-TN7KJJD Google Tag Manager container
- ca-pub-6948820955633789 AdSense publisher id
- EU_vDdKuw7a6LoePGYolNqMf-lBiazzaWUY81udqqV4 Google site verification
- ieZFAE-dZbgowd2vjmAMpugdRWDfvFSVy0jDqfG8PyM Google site verification
- 360442021262126 Facebook app id
- ca-pub-7152402105127515 AdSense publisher id
3 third-party hosts added
8 files added

Questions about die-tagespost.de

How does PageSourceSearch know what die-tagespost.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 die-tagespost.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 die-tagespost.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 die-tagespost.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.