Site profile
the-key.jp
Built with gtm, vue 2.4.0, @findify/bundle 7.1.108, core-js-bundle 3.50.0, fomantic-ui 2.9.4, kore-web-sdk 11.28.1, anfuns-assets 1.0.10, jsonld 9.0.0, json-db-admin 0.0.1, universalviewer 4.4.4, supafolio-sdk 1.4.1, volantis-static 0.0.1761982841160 and more. 5 pages and 17 stored files, last crawled 2026-10-04.
rank 10,582,857 21 libraries 0 identifiers 15 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-04 | |
| vue | 2.4.0 | 2026-10-04 |
| @findify/bundle | 7.1.108 | 2026-10-04 |
| core-js-bundle | 3.50.0 | 2026-10-04 |
| fomantic-ui | 2.9.4 | 2026-10-04 |
| kore-web-sdk | 11.28.1 | 2026-10-04 |
| anfuns-assets | 1.0.10 | 2026-10-04 |
| jsonld | 9.0.0 | 2026-10-04 |
| json-db-admin | 0.0.1 | 2026-10-04 |
| universalviewer | 4.4.4 | 2026-10-04 |
| supafolio-sdk | 1.4.1 | 2026-10-04 |
| volantis-static | 0.0.1761982841160 | 2026-10-04 |
| @recogito/annotorious | 2.7.14 | 2026-10-04 |
| @flittpayments/checkout | 1.17.2 | 2026-10-04 |
| greensock | 1.20.2 | 2026-10-04 |
| hyperformula | 3.4.0 | 2026-10-04 |
| chobitsu | 1.8.6 | 2026-10-04 |
| @unbabel/ui | 5.19.0 | 2026-10-04 |
| @chatui/core | 3.8.0 | 2026-10-04 |
| bkl-request-demo | 1.0.8 | 2026-10-04 |
| genesys-cloud-webrtc-sdk | 14.2.4 | 2026-10-04 |
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
Hosts outside the-key.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 |
|---|---|---|
| asp.hotel-story.ne.jp | connect | view source |
| axios-http.com | connect | view source |
| d-reserve.jp | connect | view source |
| github.com | connect | view source |
| members.kanayaresorts.com | connect | view source |
| player.vimeo.com | connect | view source |
| recruit.kanayaresorts.com | connect | view source |
| trip-ai.jp | script connect | view source |
| webfont.fontplus.jp | script | view source |
| www.facebook.com | connect | view source |
| www.googletagmanager.com | connect | view source |
| www.instagram.com | connect | view source |
| www.kanayaresorts.com | connect | view source |
| www.nasusafari.com | connect | view source |
| www.w3.org | connect | 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
5 pages, 17 files, 1.7 MB; 21 libraries, 0 identifiers, 15 third-party hosts
21 libraries added
- bkl-request-demo 1.0.8
- @unbabel/ui 5.19.0
- json-db-admin 0.0.1
- hyperformula 3.4.0
- @recogito/annotorious 2.7.14
- genesys-cloud-webrtc-sdk 14.2.4
- core-js-bundle 3.50.0
- @flittpayments/checkout 1.17.2
- jsonld 9.0.0
- supafolio-sdk 1.4.1
- chobitsu 1.8.6
- vue 2.4.0
- and 9 more
16 third-party hosts added
17 files added
- https://highland-nasu.the-key.jp/ html
- https://highland-nasu.the-key.jp/news/ html
- https://highland-nasu.the-key.jp/news/article/?id=1441 html
- https://highland-nasu.the-key.jp/kitchen/ html
- https://highland-nasu.the-key.jp/rooms/ html
- https://highland-nasu.the-key.jp/js/fontasync.js js
- https://highland-nasu.the-key.jp/js/chat.js js
- https://highland-nasu.the-key.jp/_nuxt/2b0fd76.js js
- https://highland-nasu.the-key.jp/_nuxt/bbf7fd2.js js
- https://highland-nasu.the-key.jp/_nuxt/bec15e0.js js
- https://highland-nasu.the-key.jp/_nuxt/7d1186f.js js
- https://highland-nasu.the-key.jp/_nuxt/c7cf059.js js
- and 5 more
Questions about the-key.jp
- How does PageSourceSearch know what the-key.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 the-key.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 the-key.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 the-key.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.