Site profile
bij-kusuri.jp
Built with gtm, gather-vue 8.20.3, typesense 3.0.6, kore-web-sdk 11.28.1, @cdek-it/widget 4.0.0, bootstrap-italia 2.18.3, @machi-pla/japan_concierge_2024 0.1.5, cil-dropin-components 1.2.10, @myparcel-dev/delivery-options 7.5.3, @eid-easy/eideasy-widget 3.17.5, tify 0.36.2, @solace-health/solace-entry-widget 2.0.5. 5 pages and 16 stored files, last crawled 2026-10-08.
rank 13,471,451 12 libraries 1 identifier 5 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 | |
| gather-vue | 8.20.3 | 2026-10-08 |
| typesense | 3.0.6 | 2026-10-08 |
| kore-web-sdk | 11.28.1 | 2026-10-08 |
| @cdek-it/widget | 4.0.0 | 2026-10-08 |
| bootstrap-italia | 2.18.3 | 2026-10-08 |
| @machi-pla/japan_concierge_2024 | 0.1.5 | 2026-10-08 |
| cil-dropin-components | 1.2.10 | 2026-10-08 |
| @myparcel-dev/delivery-options | 7.5.3 | 2026-10-08 |
| @eid-easy/eideasy-widget | 3.17.5 | 2026-10-08 |
| tify | 0.36.2 | 2026-10-08 |
| @solace-health/solace-entry-widget | 2.0.5 | 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-NFV8BF9 | view source |
Third-party hosts
Hosts outside bij-kusuri.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 |
|---|---|---|
| script.bi-instatag.com | script | view source |
| social-plugins.line.me | connect | view source |
| vuejs.org | connect | view source |
| www.googletagmanager.com | iframe 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, 16 files, 957.3 KB; 12 libraries, 1 identifier, 5 third-party hosts
12 libraries added
- gtm
- kore-web-sdk 11.28.1
- bootstrap-italia 2.18.3
- cil-dropin-components 1.2.10
- @eid-easy/eideasy-widget 3.17.5
- typesense 3.0.6
- @machi-pla/japan_concierge_2024 0.1.5
- @cdek-it/widget 4.0.0
- @solace-health/solace-entry-widget 2.0.5
- gather-vue 8.20.3
- @myparcel-dev/delivery-options 7.5.3
- tify 0.36.2
1 identifier added
- GTM-NFV8BF9 Google Tag Manager container
6 third-party hosts added
16 files added
- https://bij-kusuri.jp/ html
- https://bij-kusuri.jp/date_search/ html
- https://bij-kusuri.jp/products/ html
- https://bij-kusuri.jp/products/field/ html
- https://bij-kusuri.jp/request/ html
- https://bij-kusuri.jp/common/scripts/main.js?260423150344 js
- https://bij-kusuri.jp/common/scripts/line_search.js js
- https://bij-kusuri.jp/request/_nuxt/DEtUrglv.js js
- https://bij-kusuri.jp/request/_nuxt/DAvU1qw7.js js
- https://bij-kusuri.jp/request/_nuxt/CJdSIAXl.js js
- https://bij-kusuri.jp/request/_nuxt/D3EMJuY7.js js
- https://bij-kusuri.jp/request/_nuxt/CT9Zm6q3.js js
- and 4 more
Questions about bij-kusuri.jp
- How does PageSourceSearch know what bij-kusuri.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 bij-kusuri.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 bij-kusuri.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 bij-kusuri.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.