How does PageSourceSearch know what op3.dev 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 op3.dev 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 op3.dev?

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 op3.dev?

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

op3.dev

Built with @shoelace-style/shoelace 2.20.0, cloudflare-insights, @feedmepos/mf-report 5.29.2. 5 pages and 7 stored files.

rank 390,127 3 libraries 1 identifier 0 third-party hosts 0 crawls 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
@shoelace-style/shoelace	2.20.0	2026-09-24
cloudflare-insights		2026-09-24
@feedmepos/mf-report	5.29.2	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
Cloudflare Web Analytics token (Cloudflare)	7da609030515408f9ec8b16c529cecaf	view source

Third-party hosts

The stored pages and scripts reference no host outside op3.dev.

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 7) }. 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://cdn.jsdelivr.net/npm/@shoelace-style/sho…/cdn/shoelace-autoloader.js	js library	not fetched	2026-09-24	current
https://op3.dev/privacy	html	28 KB	2026-09-24	current
https://op3.dev/show/dc1852e4d1ee4bce9c4fb7f5d8be8908	html	1.6 MB	2026-09-24	current
https://static.cloudflareinsights.com/beacon.min.js	js library	not fetched	2026-09-24	current
https://op3.dev/api/docs	html	196.6 KB	2026-09-24	current
https://op3.dev/setup	html	50.2 KB	2026-09-24	current
https://op3.dev/	html	95.2 KB	2026-09-24	current

Timeline

No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.

Questions about op3.dev

How does PageSourceSearch know what op3.dev 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 op3.dev 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 op3.dev?: 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 op3.dev?: 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.