How does PageSourceSearch know what 0x3.me 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 0x3.me 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 0x3.me?

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 0x3.me?

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

0x3.me

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

1 library 0 identifiers 10 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
@vitest/utils	5.0.2	2026-10-10

Tracking, tag and verification IDs

No analytics property, tag manager container, pixel or site-verification token was found in the stored source.

Third-party hosts

Hosts outside 0x3.me 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
0x5.me	script	view source
0x6.me	script	view source
0x7.me	script	view source
0x9.me	script	view source
cxcc.me	script	view source
dwz3.cn	script	view source
mlnk.me	script	view source
static-link-hub-assets.next3.cn	script stylesheet	view source
tblk.me	script	view source
weti.me	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://0x3.me/indentify/syncLogin?user_login=BFD3BCD50081F3F55B6E7868D383E97B	js	not fetched	2026-10-10	2026-10-10
https://0x3.me/indentify/syncLogin?user_login=CF98C3F0CFF9ABD8E2693D02E58E137E	js	not fetched	2026-10-10	2026-10-10
https://0x3.me/indentify/syncLogin?user_login=EAE69A17295FCA7A3710ED5D7CF7D448	js	not fetched	2026-10-10	2026-10-10
https://0x3.me/indentify/syncLogin?user_login=13F655E80FC99AA2046D6B814929C474	js	not fetched	2026-10-10	2026-10-10
https://0x3.me/indentify/syncLogin?user_login=F282142A74B254AAE3FD80A4F559E2F5	js	not fetched	2026-10-10	2026-10-10
https://0x3.me/info/about	html	94.7 KB	2026-10-10	2026-10-10
https://0x3.me/article/lists	html	18.6 KB	2026-10-10	2026-10-10
https://0x3.me/info/product?from=nav	html	23.3 KB	2026-10-10	2026-10-10
https://0x3.me/user/login	html	12.4 KB	2026-10-10	2026-10-10
https://0x3.me/	html	17.6 KB	2026-10-10	2026-10-10

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

5 pages, 10 files, 166.5 KB; 1 library, 0 identifiers, 10 third-party hosts
1 library added
- @vitest/utils 5.0.2
11 third-party hosts added
10 files added

Questions about 0x3.me

How does PageSourceSearch know what 0x3.me 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 0x3.me 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 0x3.me?: 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 0x3.me?: 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.