How does PageSourceSearch know what mailboxes.info 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 mailboxes.info 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 mailboxes.info?

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 mailboxes.info?

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

mailboxes.info

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

rank 10,524,115 4 libraries 8 identifiers 6 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
google-analytics		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)	AA518F5E1BDDA70DB735DE123057247A	view source
Bing site verification (Microsoft)	C436E5180B055769311586EBC22EBDB9	view source
Google site verification (Google)	110B_AeKj6moZVzyc4h_y20z4uaeM9U8AJ3e6TaELT0	view source
Google site verification (Google)	8QaHJENhSoEO4PQv0z5FrpIxTctLAiX0wndmtnGu1AA	view source
Google site verification (Google)	f_ayX3Zi9XUBHuMI6HXzcoiUlbBAFASc1m7S24_jyMs	view source
Google Tag Manager container (Google)	GTM-P9TZK5P	view source
Pinterest site verification (Pinterest)	6ef86c70e9d278421a4a89ef46be3576	view source
Universal Analytics property id (Google)	UA-1518042-1	view source

Third-party hosts

Hosts outside mailboxes.info 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
downloads.mailchimp.com	script	view source
fonts.googleapis.com	stylesheet	view source
s.turbifycdn.com	script	view source
sep.turbifycdn.com	script stylesheet	view source
turbifycdn.com	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 5) }. 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://store.mailboxes.info/info.html	html	37.2 KB	2026-10-04	2026-10-04
https://www.googletagmanager.com/gtag/js?id=UA-1518042-1	js library	not fetched	2026-10-04	2026-10-04
https://store.mailboxes.info/store-install.html	html	31.3 KB	2026-10-04	2026-10-04
https://store.mailboxes.info/covid-items.html	html	35.9 KB	2026-10-04	2026-10-04
https://store.mailboxes.info/	html	31.9 KB	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

4 pages, 5 files, 136.3 KB; 4 libraries, 8 identifiers, 6 third-party hosts
4 libraries added
- gtm
- @vitest/utils 5.0.2
- google-analytics
- gtag
8 identifiers added
- GTM-P9TZK5P Google Tag Manager container
- UA-1518042-1 Universal Analytics property id
- 8QaHJENhSoEO4PQv0z5FrpIxTctLAiX0wndmtnGu1AA Google site verification
- 110B_AeKj6moZVzyc4h_y20z4uaeM9U8AJ3e6TaELT0 Google site verification
- f_ayX3Zi9XUBHuMI6HXzcoiUlbBAFASc1m7S24_jyMs Google site verification
- C436E5180B055769311586EBC22EBDB9 Bing site verification
- AA518F5E1BDDA70DB735DE123057247A Bing site verification
- 6ef86c70e9d278421a4a89ef46be3576 Pinterest site verification
8 third-party hosts added
5 files added

Questions about mailboxes.info

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