Site profile
secure-navi.jp
Built with gtm, @n8n/chat 1.39.2, @marimo-team/frontend 0.25.0, vue-router 5.3.1, element-plus 2.14.6, @gumlet/insights-js-core 4.0.3, @scalar/api-reference 1.71.0, @coveo/headless 3.57.0, @devframes/hub-ui 1.0.0, @gouvfr/dsfr-chart 2.1.1, @data-fair/app-charts 1.4.4, ramp-pcar 4.22.1 and more. 1 page and 15 stored files, last crawled 2026-10-02.
rank 692,783 14 libraries 1 identifier 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-02 | |
| @n8n/chat | 1.39.2 | 2026-10-02 |
| @marimo-team/frontend | 0.25.0 | 2026-10-02 |
| vue-router | 5.3.1 | 2026-10-02 |
| element-plus | 2.14.6 | 2026-10-02 |
| @gumlet/insights-js-core | 4.0.3 | 2026-10-02 |
| @scalar/api-reference | 1.71.0 | 2026-10-02 |
| @coveo/headless | 3.57.0 | 2026-10-02 |
| @devframes/hub-ui | 1.0.0 | 2026-10-02 |
| @gouvfr/dsfr-chart | 2.1.1 | 2026-10-02 |
| @data-fair/app-charts | 1.4.4 | 2026-10-02 |
| ramp-pcar | 4.22.1 | 2026-10-02 |
| @waline/client | 3.15.2 | 2026-09-24 |
| twikoo | 2.0.9 | 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 site verification (Google) | yuUIzql8kZQZ37JrzYTEOgmiACSLXzLqAdLsNR1Ks0Q | view source |
Third-party hosts
Hosts outside secure-navi.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 |
|---|---|---|
| analytics.studiodesignapp.com | connect | view source |
| cdn.channel.io | connect | view source |
| connect.facebook.net | connect | view source |
| fonts.googleapis.com | connect | view source |
| fonts.gstatic.com | connect | view source |
| js.hs-scripts.com | connect | view source |
| nuxt.com | connect | view source |
| storage.googleapis.com | connect | view source |
| studio.design | connect | view source |
| vuejs.org | connect | view source |
| widget.intercom.io | connect | view source |
| www.google-analytics.com | connect | view source |
| www.google.com | connect | view source |
| www.googletagmanager.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
1 page, 11 files, 574.6 KB; 12 libraries, 1 identifier, 15 third-party hosts
12 libraries added
- vue-router 5.3.1
- @gumlet/insights-js-core 4.0.3
- @scalar/api-reference 1.71.0
- @devframes/hub-ui 1.0.0
- @gouvfr/dsfr-chart 2.1.1
- @n8n/chat 1.39.2
- ramp-pcar 4.22.1
- @marimo-team/frontend 0.25.0
- @data-fair/app-charts 1.4.4
- element-plus 2.14.6
- @coveo/headless 3.57.0
- gtm
1 identifier added
- yuUIzql8kZQZ37JrzYTEOgmiACSLXzLqAdLsNR1Ks0Q Google site verification
15 third-party hosts added
11 files added
- https://secure-navi.jp/ html
- https://secure-navi.jp/_nuxt/B_fSWFJa.js js
- https://secure-navi.jp/_nuxt/CbXtAM7H.js js
- https://secure-navi.jp/_nuxt/Cqksm9lV.js js
- https://secure-navi.jp/_nuxt/BguDustX.js js
- https://secure-navi.jp/_nuxt/HclGiUj8.js js
- https://secure-navi.jp/_nuxt/J-ytfnqK.js js
- https://secure-navi.jp/_nuxt/-X72B8JK.js js
- https://secure-navi.jp/_nuxt/DXaWbY8T.js js
- https://www.googletagmanager.com/gtm.js?id=GTM-T4VW9DP7 js
- https://www.googletagmanager.com/gtm.js?id= js
Questions about secure-navi.jp
- How does PageSourceSearch know what secure-navi.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 secure-navi.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 secure-navi.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 secure-navi.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.