How does PageSourceSearch know what tocado-fruit.tokyo 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 tocado-fruit.tokyo 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 tocado-fruit.tokyo?

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 tocado-fruit.tokyo?

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

tocado-fruit.tokyo

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

rank 10,527,015 1 library 5 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
@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)	4367FC7351BC659FDAB57154B91B3CAB	view source
Facebook domain verification (Meta)	rbugqnj4mbb5q9uaurnpzz268gq0dm	view source
Google site verification (Google)	5VXQhDeX9V6PA0U10nhpv3yl7DFA_ESvSutJ0vUKJco	view source
Pinterest site verification (Pinterest)	c6add68ae4b1725f67c0f0d223e487f6	view source
Yandex site verification (Yandex)	6c4ad2a18352db14	view source

Third-party hosts

Hosts outside tocado-fruit.tokyo 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
browser.sentry-cdn.com	script	view source
scontent-den2-1.cdninstagram.com	iframe	view source
static.parastorage.com	script stylesheet	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://www.tocado-fruit.tokyo/presskit	html	1.4 MB	2026-10-04	2026-10-04
https://www.tocado-fruit.tokyo/philosophy	html	1.3 MB	2026-10-04	2026-10-04
https://www.tocado-fruit.tokyo/aboutus	html	1.3 MB	2026-10-04	2026-10-04
https://www.tocado-fruit.tokyo/abouttocado	html	1.3 MB	2026-10-04	2026-10-04
https://www.tocado-fruit.tokyo/	html	1.7 MB	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

5 pages, 5 files, 7.1 MB; 1 library, 5 identifiers, 3 third-party hosts
1 library added
- @vitest/utils 5.0.2
5 identifiers added
- 5VXQhDeX9V6PA0U10nhpv3yl7DFA_ESvSutJ0vUKJco Google site verification
- 4367FC7351BC659FDAB57154B91B3CAB Bing site verification
- 6c4ad2a18352db14 Yandex site verification
- rbugqnj4mbb5q9uaurnpzz268gq0dm Facebook domain verification
- c6add68ae4b1725f67c0f0d223e487f6 Pinterest site verification
4 third-party hosts added
5 files added

Questions about tocado-fruit.tokyo

How does PageSourceSearch know what tocado-fruit.tokyo 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 tocado-fruit.tokyo 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 tocado-fruit.tokyo?: 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 tocado-fruit.tokyo?: 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.