Site profile
hokkaido-digital-museum.jp
Built with swiper, bootstrap, jquery, gtag, popper.js, @findify/bundle 7.1.108, bowser 2.14.1, bromcom-ui 2.12.3, object-fit-images, oidc-client 1.11.5, anfuns-assets 1.0.10, es6-promise and more. 5 pages and 15 stored files, last crawled 2026-10-02.
rank 730,074 41 libraries 1 identifier 9 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 |
|---|---|---|
| swiper | 2026-10-02 | |
| bootstrap | 2026-10-02 | |
| jquery | 2026-10-02 | |
| gtag | 2026-10-02 | |
| popper.js | 2026-10-02 | |
| @findify/bundle | 7.1.108 | 2026-10-02 |
| bowser | 2.14.1 | 2026-10-02 |
| bromcom-ui | 2.12.3 | 2026-10-02 |
| object-fit-images | 2026-10-02 | |
| oidc-client | 1.11.5 | 2026-10-02 |
| anfuns-assets | 1.0.10 | 2026-10-02 |
| es6-promise | 2026-10-02 | |
| dom7 | 2026-10-02 | |
| ssr-window | 2026-10-02 | |
| json-db-admin | 0.0.1 | 2026-10-02 |
| universalviewer | 4.4.4 | 2026-10-02 |
| vue-moment | 4.1.0 | 2026-10-02 |
| @googlemaps/js-api-loader | 2026-10-02 | |
| volantis-static | 0.0.1761982841160 | 2026-10-02 |
| venom-player | 0.2.92 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @genpact/genome.mfe.solidify-app | 3.15.1 | 2026-10-02 |
| wsemi | 1.9.3 | 2026-10-02 |
| idle-js | 1.2.0 | 2026-10-02 |
| cbplayer2 | 0.12.0 | 2026-10-02 |
| startbootstrap-sb-admin-2 | 4.1.4 | 2026-10-02 |
| @saasquatch/mint-components | 2.5.1 | 2026-10-02 |
| @widgetti/solara-vuetify-app | 10.1.1 | 2026-10-02 |
| v-img | 0.2.0 | 2026-10-02 |
| @unbabel/ui | 5.19.0 | 2026-10-02 |
| comindware.core.ui | 2.1.149 | 2026-10-02 |
| alpheios-components | 3.4.3-incr-3.4.x.20220428394 | 2026-10-02 |
| js-heo | 1.0.13 | 2026-10-02 |
| @sum.cumo/vue-awesome-swiper | 3.1.6 | 2026-10-02 |
| bkl-request-demo | 1.0.8 | 2026-10-02 |
| cdn4script | 2.2.4 | 2026-09-24 |
| vviinn-widgets | 2.224.3 | 2026-09-24 |
| viewerjs | 1.14.0 | 2026-09-24 |
| supafolio-sdk | 1.4.1 | 2026-09-24 |
| dzxstatic | 3.4.20211231 | 2026-09-24 |
| @3t-transform/threeteeui | 1.12.1 | 2026-09-24 |
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-M5JGZJPSY5 | view source |
Third-party hosts
Hosts outside hokkaido-digital-museum.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 |
|---|---|---|
| bit.ly | connect | view source |
| creativecommons.org | connect | view source |
| fonts.googleapis.com | stylesheet | view source |
| jpsearch.go.jp | connect | view source |
| maps.googleapis.com | connect | view source |
| rightsstatements.org | connect | view source |
| www.googletagmanager.com | script connect | view source |
| www.w3.org | connect | view source |
| www.youtube.com | 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, 15 files, 1.7 MB; 35 libraries, 1 identifier, 9 third-party hosts
35 libraries added
- gtag
- @vitest/utils 5.0.2
- bootstrap
- jquery
- object-fit-images
- popper.js
- @googlemaps/js-api-loader
- dom7
- es6-promise
- ssr-window
- swiper
- oidc-client 1.11.5
- and 23 more
1 identifier added
- G-M5JGZJPSY5 Google Analytics 4 measurement id
10 third-party hosts added
15 files added
- https://hokkaido-digital-museum.jp/ html
- https://hokkaido-digital-museum.jp/artifacts-search/ html
- https://hokkaido-digital-museum.jp/about/ html
- https://hokkaido-digital-museum.jp/contact/ html
- https://hokkaido-digital-museum.jp/museum-list/ html
- https://hokkaido-digital-museum.jp/wp-includes/j…?ver=f0f188028580e8dc1255 js
- https://hokkaido-digital-museum.jp/wp-includes/j…?ver=1dfe7db3940c23ea9216 js
- https://hokkaido-digital-museum.jp/wp-content/pl…/swv/js/index.js?ver=6.1.7 js
- https://hokkaido-digital-museum.jp/wp-content/pl…/includes/js/index.js?ver=6.1.7 js
- https://hokkaido-digital-museum.jp/wp-content/themes/hdm-ja/js/common.bundle.js js
- https://hokkaido-digital-museum.jp/wp-content/themes/hdm-ja/js/front.bundle.js js
- https://hokkaido-digital-museum.jp/wp-content/pl…/dist/top-facility.js?ver=7.1.2 js
- and 3 more
Questions about hokkaido-digital-museum.jp
- How does PageSourceSearch know what hokkaido-digital-museum.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 hokkaido-digital-museum.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 hokkaido-digital-museum.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 hokkaido-digital-museum.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.