How does PageSourceSearch know what store-domingo.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 store-domingo.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 store-domingo.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 store-domingo.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.

Site profile

store-domingo.jp

Built with jquery 1.7.1, gtm, gtag, jquery-ui 1.8.16, facebook-pixel, luckysheet 2.1.13, universalviewer 4.4.4, @vitest/utils 5.0.2, bootstrap-datetime-picker 2.4.4, @searchtap/search-client 1.3.0, mixpanel-common 1.129.0. 5 pages and 10 stored files, last crawled 2026-10-06.

rank 12,039,434 11 libraries 6 identifiers 8 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
jquery	1.7.1	2026-10-06
gtm		2026-10-06
gtag		2026-10-06
jquery-ui	1.8.16	2026-10-06
facebook-pixel		2026-10-06
luckysheet	2.1.13	2026-10-06
universalviewer	4.4.4	2026-10-06
@vitest/utils	5.0.2	2026-10-06
bootstrap-datetime-picker	2.4.4	2026-10-06
@searchtap/search-client	1.3.0	2026-10-06
mixpanel-common	1.129.0	2026-10-06

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
Facebook domain verification (Meta)	55jw5llw9v1925f2g5kwcqlo3b33f5	view source
Meta pixel id (Meta)	2994801050561908	view source
Google Analytics 4 measurement id (Google)	G-EYRNRKEEMD	view source
Google site verification (Google)	Y24z6AkxgmBgyOa1GqoUXiUkEFHU3OQtLoJN4IEUkk0	view source
Google Tag Manager container (Google)	GTM-NZRBC54	view source
Sentry DSN host (Sentry)	o423276.ingest.sentry.io	view source

Third-party hosts

Hosts outside store-domingo.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
cdnjs.cloudflare.com	script	view source
instagram.aratana-gateway.jp	connect	view source
pinterest.com	connect	view source
timeline.line.me	connect	view source
twitter.com	connect	view source
www.facebook.com	connect	view source
www.googletagmanager.com	script	view source
www.visumo.jp	script	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 10) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

File	Kind	Size	Collected	Versions
https://cdnjs.cloudflare.com/v3/polyfill.min.js?…e.includes,IntersectionObserver	js library	not fetched	2026-10-06	2026-10-06
https://store-domingo.jp/client_info/DOMINGO/vie…?timestamp=1787186565100	js	249.5 KB	2026-10-06	2026-10-06
https://www.googletagmanager.com/gtag/js?id=G-EYRNRKEEMD	js library	not fetched	2026-10-06	2026-10-06
https://store-domingo.jp/client_info/DOMINGO/vie…?timestamp=1787186565100	js	9.9 KB	2026-10-06	2026-10-06
https://store-domingo.jp/client_info/DOMINGO/vie…?timestamp=1787186565100	js	156.7 KB	2026-10-06	2026-10-06
https://store-domingo.jp/ext/stores.html	html	48.4 KB	2026-10-06	2026-10-06
https://store-domingo.jp/item/107462197.html	html	133.5 KB	2026-10-06	2026-10-06
https://store-domingo.jp/item_detail_search.html	html	47.9 KB	2026-10-06	2026-10-06
https://store-domingo.jp/	html	140.7 KB	2026-10-06	2026-10-06
https://store-domingo.jp/login.html	html	46.8 KB	2026-10-06	2026-10-06

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.

2026-10-06 first crawl

5 pages, 10 files, 833.4 KB; 11 libraries, 6 identifiers, 8 third-party hosts
11 libraries added
- gtag
- gtm
- facebook-pixel
- @vitest/utils 5.0.2
- mixpanel-common 1.129.0
- bootstrap-datetime-picker 2.4.4
- jquery 1.7.1
- jquery-ui 1.8.16
- luckysheet 2.1.13
- @searchtap/search-client 1.3.0
- universalviewer 4.4.4
6 identifiers added
- G-EYRNRKEEMD Google Analytics 4 measurement id
- GTM-NZRBC54 Google Tag Manager container
- 2994801050561908 Meta pixel id
- Y24z6AkxgmBgyOa1GqoUXiUkEFHU3OQtLoJN4IEUkk0 Google site verification
- 55jw5llw9v1925f2g5kwcqlo3b33f5 Facebook domain verification
- o423276.ingest.sentry.io Sentry DSN host
8 third-party hosts added
10 files added

Questions about store-domingo.jp

How does PageSourceSearch know what store-domingo.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 store-domingo.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 store-domingo.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 store-domingo.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.