Site profile
jftc.go.jp
Built with @accessible360/accessible-slick 1.0.1, fomantic-ui 2.9.4, scroll-hint 1.2.9, slick-slider 1.8.2, @vitest/utils 5.0.2, parse 8.6.2, stackedboost-shopify-assets 0.2.0, gameanalytics 5.0.0, jquery 3.6.3, mv-boost 0.0.8, pushfeedback 0.1.85. 5 pages and 23 stored files.
rank 13,369 11 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 |
|---|---|---|
| @accessible360/accessible-slick | 1.0.1 | 2026-10-01 |
| fomantic-ui | 2.9.4 | 2026-10-01 |
| scroll-hint | 1.2.9 | 2026-10-01 |
| slick-slider | 1.8.2 | 2026-10-01 |
| @vitest/utils | 5.0.2 | 2026-10-01 |
| parse | 8.6.2 | 2026-10-01 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-01 |
| gameanalytics | 5.0.0 | 2026-10-01 |
| jquery | 3.6.3 | 2026-09-24 |
| mv-boost | 0.0.8 | 2026-09-24 |
| 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 jftc.go.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 jftc.go.jp
- How does PageSourceSearch know what jftc.go.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 jftc.go.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 jftc.go.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 jftc.go.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.