Site profile
kaitori-okoku.jp
Built with gtm, vue, axios, bxslider 4.2.17, es6-promise 4, mdn-polyfills 5.20.0, jquery.scrollup 2.4.1, calenstyle 2.0.8. 4 pages and 25 stored files, last crawled 2026-10-08.
rank 13,929,966 8 libraries 1 identifier 3 third-party hosts 1 crawl 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-10-08 | |
| vue | 2026-10-08 | |
| axios | 2026-10-08 | |
| bxslider | 4.2.17 | 2026-10-08 |
| es6-promise | 4 | 2026-10-08 |
| mdn-polyfills | 5.20.0 | 2026-10-08 |
| jquery.scrollup | 2.4.1 | 2026-10-08 |
| calenstyle | 2.0.8 | 2026-10-08 |
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-T7BCBT | view source |
Third-party hosts
Hosts outside kaitori-okoku.jp that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
| Host | Loaded as | Found in |
|---|---|---|
| cdn.jsdelivr.net | script | view source |
| seal.globalsign.com | script | view source |
| www.googletagmanager.com | iframe | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
4 pages, 25 files, 427 KB; 8 libraries, 1 identifier, 3 third-party hosts
8 libraries added
- gtm
- calenstyle 2.0.8
- bxslider 4.2.17
- jquery.scrollup 2.4.1
- mdn-polyfills 5.20.0
- es6-promise 4
- vue
- axios
1 identifier added
- GTM-T7BCBT Google Tag Manager container
3 third-party hosts added
25 files added
- https://kaitori-okoku.jp/ html
- https://kaitori-okoku.jp/news/news-1155/ html
- https://kaitori-okoku.jp/regist/ html
- https://kaitori-okoku.jp/kaitorihelp/ html
- https://kaitori-okoku.jp/wordpress/wp-content/th…/portal/js/jquery-1.11.1.min.js js
- https://kaitori-okoku.jp/wordpress/wp-content/themes/portal/js/ie.js js
- https://kaitori-okoku.jp/wordpress/wp-content/themes/portal/js/updnWatermark.js js
- https://kaitori-okoku.jp/wordpress/wp-content/th…/js/jquery.validate.min.js js
- https://kaitori-okoku.jp/wordpress/wp-content/themes/portal/js/messages_ja.js js
- https://kaitori-okoku.jp/wordpress/wp-content/th…/js/jquery.bxslider.min.js js
- https://kaitori-okoku.jp/wordpress/wp-content/themes/portal/js/gloss.1.0.js js
- https://kaitori-okoku.jp/wordpress/wp-content/th…/portal/js/jquery.easing.1.3.js js
- and 13 more
Questions about kaitori-okoku.jp
- How does PageSourceSearch know what kaitori-okoku.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 kaitori-okoku.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 kaitori-okoku.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 kaitori-okoku.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.