Site profile
gracom.jp
Built with gtm, bxslider 4.2.17, jquery-ui 1.14.2, lightbox2 2.12.0, tooltipster 4.2.8, selectric 1.13.0, dzxstatic 3.4.20211231, slicknav 1.0.8, @textadventures/quest-viva-wasmplayer 6.0.0-rc.3, jquery-passive 3.6.0, @chakra-ui/utils 2.2.2. 5 pages and 13 stored files.
rank 1,594,230 11 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-25 | |
| bxslider | 4.2.17 | 2026-09-25 |
| jquery-ui | 1.14.2 | 2026-09-25 |
| lightbox2 | 2.12.0 | 2026-09-25 |
| tooltipster | 4.2.8 | 2026-09-25 |
| selectric | 1.13.0 | 2026-09-25 |
| dzxstatic | 3.4.20211231 | 2026-09-25 |
| slicknav | 1.0.8 | 2026-09-25 |
| @textadventures/quest-viva-wasmplayer | 6.0.0-rc.3 | 2026-09-25 |
| jquery-passive | 3.6.0 | 2026-09-25 |
| @chakra-ui/utils | 2.2.2 | 2026-09-25 |
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-W659V67 | view source |
Third-party hosts
The stored pages and scripts reference no host outside gracom.jp.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://gracom.jp/theme/gs/js/form-submit.js | js | 334 B | 2026-09-25 | current |
| https://gracom.jp/mail/js/mail_token.js | js | 285 B | 2026-09-25 | current |
| https://gracom.jp/theme/admin-third/js/admin/vendors/i18n/ui.datepicker-ja.js | js | 857 B | 2026-09-25 | current |
| https://gracom.jp/theme/admin-third/js/admin/vendors/jquery-ui-1.11.4.min.js | js | 234.8 KB | 2026-09-25 | current |
| https://gracom.jp/theme/gs/js/jquery.bxslider.js | js | 66 KB | 2026-09-25 | current |
| https://gracom.jp/theme/gs/js/style.js | js | 377 B | 2026-09-25 | current |
| https://gracom.jp/theme/gs/js/jquery-3.6.0.js | js | 281.8 KB | 2026-09-25 | current |
| https://gracom.jp/theme/gs/js/jquery.slicknav.js | js | 20.5 KB | 2026-09-25 | current |
| https://gracom.jp/gracom_new | html | 7.9 KB | 2026-09-25 | current |
| https://gracom.jp/contact/ | html | 18 KB | 2026-09-25 | current |
| https://gracom.jp/about | html | 11.2 KB | 2026-09-25 | current |
| https://gracom.jp/news/ | html | 12.5 KB | 2026-09-25 | current |
| https://gracom.jp/ | html | 18.3 KB | 2026-09-25 | current |
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about gracom.jp
- How does PageSourceSearch know what gracom.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 gracom.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 gracom.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 gracom.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.