How does PageSourceSearch know what satoiin.jp 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 satoiin.jp 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 satoiin.jp?

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 satoiin.jp?

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

satoiin.jp

No known library was recognised in its stored source. 5 pages and 8 stored files, last crawled 2026-10-06.

rank 11,749,698 0 libraries 2 identifiers 3 third-party hosts 1 crawl open the site

Technologies and libraries

No library file or bundled library code was recognised in the stored source. The site may use code of its own, load its libraries from a host the crawler does not fetch, or be too new in the index.

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)	7A739090A5CF47E1E46AF9E7777BD977	view source
Google site verification (Google)	ZMVbXq-Xz6BgHnRFg8vZPfZuI1kksW_m698KFqL2sdw	view source

Third-party hosts

Hosts outside satoiin.jp 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
docs.google.com	iframe	view source
module.bindsite.jp	connect	view source
www.google.com	iframe	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://satoiin.jp/_module/js/script.js?l=1,t=default08,f=g,fs=l,c=blank	js	10.1 KB	2026-10-06	2026-10-06
https://satoiin.jp/_userdata/js/jquery_auto_j.js	js	2.4 KB	2026-10-06	2026-10-06
https://satoiin.jp/_module/js/script.js?l=0,t=default08,f=g,fs=l,c=blank	js	10.1 KB	2026-10-06	2026-10-06
https://satoiin.jp/info/accessmap.html	html	32.1 KB	2026-10-06	2026-10-06
https://satoiin.jp/sitemap.html	html	30.8 KB	2026-10-06	2026-10-06
https://satoiin.jp/contact.html	html	28 KB	2026-10-06	2026-10-06
https://satoiin.jp/news/news.html	html	60.7 KB	2026-10-06	2026-10-06
https://satoiin.jp/	html	37.5 KB	2026-10-06	2026-10-06

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

5 pages, 8 files, 211.7 KB; 0 libraries, 2 identifiers, 3 third-party hosts
2 identifiers added
- ZMVbXq-Xz6BgHnRFg8vZPfZuI1kksW_m698KFqL2sdw Google site verification
- 7A739090A5CF47E1E46AF9E7777BD977 Bing site verification
3 third-party hosts added
8 files added

Questions about satoiin.jp

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