How does PageSourceSearch know what content-security-policy.com 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 content-security-policy.com 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 content-security-policy.com?

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 content-security-policy.com?

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

content-security-policy.com

Built with gtag. 5 pages and 8 stored files, last crawled 2026-10-02.

rank 387,524 1 library 2 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
gtag		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 Analytics 4 measurement id (Google)	G-3GD6TMCQ54	view source
X (Twitter) pixel id (X)	oiuel	view source

Third-party hosts

Hosts outside content-security-policy.com 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
cdnjs.cloudflare.com	stylesheet	view source
static.ads-twitter.com	connect	view source
www.googletagmanager.com	script	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 8) }. 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://content-security-policy.com/js/browser-test.js	js	783 B	2026-10-02	current
https://www.googletagmanager.com/gtag/js?id=G-3GD6TMCQ54	js library	not fetched	2026-10-02	current
https://content-security-policy.com/js/google-analytics.js	js	471 B	2026-10-02	current
https://content-security-policy.com/examples/meta/	html	5.7 KB	2026-10-02	current
https://content-security-policy.com/examples/	html	7.7 KB	2026-10-02	current
https://content-security-policy.com/browser-test/	html	4.1 KB	2026-10-02	current
https://content-security-policy.com/skill/	html	15 KB	2026-10-02	current
https://content-security-policy.com/	html	33.8 KB	2026-10-02	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, 67.5 KB; 1 library, 2 identifiers, 3 third-party hosts
1 library added
- gtag
2 identifiers added
- G-3GD6TMCQ54 Google Analytics 4 measurement id
- oiuel X (Twitter) pixel id
3 third-party hosts added
8 files added

Questions about content-security-policy.com

How does PageSourceSearch know what content-security-policy.com 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 content-security-policy.com 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 content-security-policy.com?: 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 content-security-policy.com?: 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.