Site profile
pius.co.jp
Built with gtm, gtag, core-js-bundle 3.50.0, facebook-pixel, recaptcha, jsxgraph 1.13.3, baguettebox.js 1.13.0, vue3-sfc-loader 0.9.5, jquery.flipster 1.1.6, ovenplayer 0.10.54, @vitest/utils 5.0.2, stackedboost-shopify-assets 0.2.0 and more. 5 pages and 21 stored files, last crawled 2026-10-09.
13 libraries 5 identifiers 6 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-09 | |
| gtag | 2026-10-09 | |
| core-js-bundle | 3.50.0 | 2026-10-09 |
| facebook-pixel | 2026-10-09 | |
| recaptcha | 2026-10-09 | |
| jsxgraph | 1.13.3 | 2026-10-09 |
| baguettebox.js | 1.13.0 | 2026-10-09 |
| vue3-sfc-loader | 0.9.5 | 2026-10-09 |
| jquery.flipster | 1.1.6 | 2026-10-09 |
| ovenplayer | 0.10.54 | 2026-10-09 |
| @vitest/utils | 5.0.2 | 2026-10-09 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-09 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-09 |
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 |
|---|---|---|
| Meta pixel id (Meta) | 2028060374400606 | view source |
| Google Analytics 4 measurement id (Google) | G-SVJYR1BT2N | view source |
| Google site verification (Google) | 6fDO4vgZo8ydJDYslk2d81wGJmMRlApXBh11JA04W84 | view source |
| Google Tag Manager container (Google) | GTM-M2NBL9 | view source |
| reCAPTCHA site key (Google) | 6Lf3SQItAAAAAB_T8e4UbHxx830U8dhILBuzs2ot | view source |
Third-party hosts
Hosts outside pius.co.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 |
|---|---|---|
| ajaxzip3.github.io | script | view source |
| github.com | connect | view source |
| www.google.co.jp | connect | view source |
| www.google.com | script | view source |
| www.googletagmanager.com | script iframe | 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, 21 files, 4.8 MB; 13 libraries, 5 identifiers, 6 third-party hosts
13 libraries added
- gtm
- @vitest/utils 5.0.2
- stackedboost-shopify-assets 0.2.0
- gtag
- facebook-pixel
- recaptcha
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- baguettebox.js 1.13.0
- core-js-bundle 3.50.0
- vue3-sfc-loader 0.9.5
- and 1 more
5 identifiers added
- GTM-M2NBL9 Google Tag Manager container
- G-SVJYR1BT2N Google Analytics 4 measurement id
- 2028060374400606 Meta pixel id
- 6Lf3SQItAAAAAB_T8e4UbHxx830U8dhILBuzs2ot reCAPTCHA site key
- 6fDO4vgZo8ydJDYslk2d81wGJmMRlApXBh11JA04W84 Google site verification
7 third-party hosts added
21 files added
- https://pius.co.jp/ html
- https://pius.co.jp/beauty-m html
- https://pius.co.jp/beauty-m/juvey935 html
- https://pius.co.jp/beauty-m/pd_proslim511 html
- https://pius.co.jp/beauty-m/pd_magimpact html
- https://pius.co.jp/wp-includes/js/jquery/jquery.…?ver=3.7.1&fver=20241226020932 js
- https://pius.co.jp/wp-includes/js/jquery/jquery-…?ver=3.4.1&fver=20241226020932 js
- https://pius.co.jp/wp-content/plugins/interactiv…=1.16.19&fver=20260311111444 js
- https://pius.co.jp/wp-includes/js/dist/hooks.min…&fver=20260710110100 js
- https://pius.co.jp/wp-includes/js/dist/i18n.min.…&fver=20260710110100 js
- https://pius.co.jp/wp-content/plugins/contact-fo…?ver=6.1.7&fver=20260817110259 js
- https://pius.co.jp/wp-content/plugins/contact-fo…?ver=6.1.7&fver=20260817110259 js
- and 9 more
Questions about pius.co.jp
- How does PageSourceSearch know what pius.co.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 pius.co.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 pius.co.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 pius.co.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.