Site profile
daimaru-matsuzakaya.com
Built with gtm, mdbootstrap 4.20.0, @vitest/utils 5.0.2, calenstyle 2.0.8, swiper 3.4.1, wordcloud 1.2.3, udesly-ad-banner 0.0.4. 5 pages and 14 stored files, last crawled 2026-10-02.
rank 525,571 7 libraries 1 identifier 1 third-party host 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 | |
| mdbootstrap | 4.20.0 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| calenstyle | 2.0.8 | 2026-10-02 |
| swiper | 3.4.1 | 2026-09-24 |
| wordcloud | 1.2.3 | 2026-09-24 |
| udesly-ad-banner | 0.0.4 | 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 Tag Manager container (Google) | GTM-MWSWDHM | view source |
Third-party hosts
Hosts outside daimaru-matsuzakaya.com 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 |
|---|---|---|
| www.googletagmanager.com | iframe 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, 14 files, 377.2 KB; 4 libraries, 1 identifier, 1 third-party host
4 libraries added
- gtm
- @vitest/utils 5.0.2
- calenstyle 2.0.8
- mdbootstrap 4.20.0
1 identifier added
- GTM-MWSWDHM Google Tag Manager container
2 third-party hosts added
14 files added
- https://daimaru-matsuzakaya.com/ html
- https://daimaru-matsuzakaya.com/strategies/store.html html
- https://daimaru-matsuzakaya.com/news-topics/f_2026/ html
- https://daimaru-matsuzakaya.com/about-site/ html
- https://daimaru-matsuzakaya.com/index.html html
- https://daimaru-matsuzakaya.com/_include_js/google_analytics.js js
- https://daimaru-matsuzakaya.com/_include_js/jquery.min.js js
- https://daimaru-matsuzakaya.com/_include_js/masonry.pkgd.min.js js
- https://daimaru-matsuzakaya.com/_include_js/imagesloaded.pkgd.min.js js
- https://daimaru-matsuzakaya.com/_include_js/swiper.min.js js
- https://daimaru-matsuzakaya.com/_include_js/common.js js
- https://daimaru-matsuzakaya.com/index/_index.js js
- and 2 more
Questions about daimaru-matsuzakaya.com
- How does PageSourceSearch know what daimaru-matsuzakaya.com 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 daimaru-matsuzakaya.com 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 daimaru-matsuzakaya.com?
- 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 daimaru-matsuzakaya.com?
- 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.