Site profile
supereight-app.jp
Built with gtm, volantis-static 0.0.1761982841160, @vitest/utils 5.0.2, jquery.scrollup 2.4.1, @lanyundev/blog-static 1.4.18. 2 pages and 10 stored files, last crawled 2026-10-04.
rank 10,628,886 5 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-04 | |
| volantis-static | 0.0.1761982841160 | 2026-10-04 |
| @vitest/utils | 5.0.2 | 2026-10-04 |
| jquery.scrollup | 2.4.1 | 2026-10-04 |
| @lanyundev/blog-static | 1.4.18 | 2026-10-04 |
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-TFLVDRB | view source |
Third-party hosts
Hosts outside supereight-app.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-apac.onetrust.com | script | view source |
| www.googletagmanager.com | iframe | 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
2 pages, 10 files, 210.9 KB; 5 libraries, 1 identifier, 3 third-party hosts
5 libraries added
- @vitest/utils 5.0.2
- gtm
- volantis-static 0.0.1761982841160
- jquery.scrollup 2.4.1
- @lanyundev/blog-static 1.4.18
1 identifier added
- GTM-TFLVDRB Google Tag Manager container
3 third-party hosts added
10 files added
- https://supereight-app.jp/ html
- https://supereight-app.jp/s/se/products/items/list?ima=2242 html
- https://supereight-app.jp/files/94/_assets/se/js/se_jquery_17_20250415172955.js js
- https://supereight-app.jp/files/94/_assets/se/js…ery_easing_18_20250415173023.js js
- https://supereight-app.jp/files/94/_assets/se/js…e_lazyload_21_20250415173211.js js
- https://supereight-app.jp/files/94/_assets/se/js/se_modal_19_20250415173052.js js
- https://supereight-app.jp/files/94/_assets/se/js/se_random_20_20250415173132.js js
- https://supereight-app.jp/files/94/_assets/se/js/se_base_14_20250415172736.js js
- https://supereight-app.jp/files/94/_assets/se/js/se_script_15_20250417145854.js js
- https://supereight-app.jp/files/94/_assets/se/js…ms_js_util_12_20250220030001.js js
Questions about supereight-app.jp
- How does PageSourceSearch know what supereight-app.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 supereight-app.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 supereight-app.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 supereight-app.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.