Site profile
mainichi.jp
Built with gtm, vue 2.4.0, @wix/design-system 1.328.0, lazyload 2.0.0-rc.2, webc-miam 10.8.0, bromcom-ui 2.12.3, jssocials 1.5.0, cdn4script 2.2.4, fomantic-ui 2.9.4, @freshworks/crayons 2.13.4, malihu-custom-scrollbar-plugin 3.1.5, recaptcha and more. 5 pages and 26 stored files.
rank 5,706 19 libraries 1 identifier 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 |
|---|---|---|
| gtm | 2026-09-24 | |
| vue | 2.4.0 | 2026-09-24 |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| lazyload | 2.0.0-rc.2 | 2026-09-24 |
| webc-miam | 10.8.0 | 2026-09-24 |
| bromcom-ui | 2.12.3 | 2026-09-24 |
| jssocials | 1.5.0 | 2026-09-24 |
| cdn4script | 2.2.4 | 2026-09-24 |
| fomantic-ui | 2.9.4 | 2026-09-24 |
| @freshworks/crayons | 2.13.4 | 2026-09-24 |
| malihu-custom-scrollbar-plugin | 3.1.5 | 2026-09-24 |
| recaptcha | 2026-09-24 | |
| @cognigy/webchat | 3.50.0 | 2026-09-24 |
| babel-polyfill | 7.8.7 | 2026-09-24 |
| anfuns-assets | 1.0.10 | 2026-09-24 |
| mdbootstrap | 4.20.0 | 2026-09-24 |
| jquery-colorbox | 1.6.4 | 2026-09-24 |
| json-db-admin | 0.0.1 | 2026-09-24 |
| universalviewer | 4.4.4 | 2026-09-24 |
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 |
|---|---|---|
| Google Tag Manager container (Google) | GTM-5M48NC | view source |
Third-party hosts
The stored pages and scripts reference no host outside mainichi.jp.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about mainichi.jp
- How does PageSourceSearch know what mainichi.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 mainichi.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 mainichi.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 mainichi.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.