How does PageSourceSearch know what kodansha.co.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 kodansha.co.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 kodansha.co.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 kodansha.co.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

kodansha.co.jp

Built with gather-vue 8.20.3, @pairbo/ui-kit 0.4.23, @vitest/utils 5.0.2, @wavoip/wavoip-webphone 1.9.1, pushfeedback 0.1.85. 6 pages and 7 stored files.

rank 11,448 5 libraries 0 identifiers 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
gather-vue	8.20.3	2026-10-01
@pairbo/ui-kit	0.4.23	2026-10-01
@vitest/utils	5.0.2	2026-10-01
@wavoip/wavoip-webphone	1.9.1	2026-10-01
pushfeedback	0.1.85	2026-09-24

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

The stored pages and scripts reference no host outside kodansha.co.jp.

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://www.kodansha.co.jp/build/assets/app-DnuE2rTD.js	js	91.3 KB	2026-10-01	current
https://www.kodansha.co.jp/comic/new-releases	html	185.2 KB	2026-10-01	current
https://www.kodansha.co.jp/comic	html	316 KB	2026-10-01	current
https://www.kodansha.co.jp/company/about	html	164.4 KB	2026-10-01	current
https://www.kodansha.co.jp/comic/products/0000429871	html	199.9 KB	2026-10-01	current
https://www.kodansha.co.jp/	html	374.7 KB	2026-10-01	current
https://www.kodansha.co.jp/comic/products/0000431655	html	199.9 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 kodansha.co.jp

How does PageSourceSearch know what kodansha.co.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 kodansha.co.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 kodansha.co.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 kodansha.co.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.