Site profile
mito-hp.jp
Built with js-cookie 2, gtag, @cognigy/webchat 3.50.0, flexslider 2.7.2, @brainfish-ai/nudge-widget 0.1.3, jsxgraph 1.13.3, jquery.flipster 1.1.6, @vitest/utils 5.0.2, @grigorov-it/mazer 2.2.0. 5 pages and 29 stored files.
rank 9,248,810 9 libraries 2 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 |
|---|---|---|
| js-cookie | 2 | 2026-09-30 |
| gtag | 2026-09-30 | |
| @cognigy/webchat | 3.50.0 | 2026-09-30 |
| flexslider | 2.7.2 | 2026-09-30 |
| @brainfish-ai/nudge-widget | 0.1.3 | 2026-09-30 |
| jsxgraph | 1.13.3 | 2026-09-30 |
| jquery.flipster | 1.1.6 | 2026-09-30 |
| @vitest/utils | 5.0.2 | 2026-09-30 |
| @grigorov-it/mazer | 2.2.0 | 2026-09-30 |
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 Analytics 4 measurement id (Google) | G-W8D9PJ9FPP | view source |
| Google Analytics 4 measurement id (Google) | G-YGG9NM3MQE | view source |
Third-party hosts
The stored pages and scripts reference no host outside mito-hp.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 mito-hp.jp
- How does PageSourceSearch know what mito-hp.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 mito-hp.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 mito-hp.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 mito-hp.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.