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

Site profile

merchury.com

Built with gtm, gtag. 5 pages and 6 stored files, last crawled 2026-10-07.

rank 12,331,640 2 libraries 4 identifiers 4 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-07
gtag		2026-10-07

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 Analytics 4 measurement id (Google)	G-9Z0VMZDLND	view source
Google Tag Manager container (Google)	GTM-KJVVH5RR	view source
Yandex site verification (Yandex)	21f4d45ef7f1240c	view source
Yandex site verification (Yandex)	532a3ea7d3302c06	view source

Third-party hosts

Hosts outside merchury.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
fonts.googleapis.com	stylesheet	view source
neo.tildacdn.com	script	view source
static.tildacdn.biz	script stylesheet	view source
www.googletagmanager.com	script iframe	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 6) }. 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://merchury.com/ceny	html	388.3 KB	2026-10-07	2026-10-07
https://www.googletagmanager.com/gtag/js?id=G-9Z0VMZDLND	js library	not fetched	2026-10-07	2026-10-07
https://merchury.com/katalog	html	439.3 KB	2026-10-07	2026-10-07
https://merchury.com/nashi-proekty	html	625.3 KB	2026-10-07	2026-10-07
https://merchury.com/onas	html	503.6 KB	2026-10-07	2026-10-07
https://merchury.com/	html	955.9 KB	2026-10-07	2026-10-07

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-07 first crawl

5 pages, 6 files, 2.8 MB; 2 libraries, 4 identifiers, 4 third-party hosts
2 libraries added
- gtag
- gtm
4 identifiers added
- G-9Z0VMZDLND Google Analytics 4 measurement id
- GTM-KJVVH5RR Google Tag Manager container
- 532a3ea7d3302c06 Yandex site verification
- 21f4d45ef7f1240c Yandex site verification
6 third-party hosts added
6 files added
- https://merchury.com/ html
- https://merchury.com/onas html
- https://merchury.com/nashi-proekty html
- https://merchury.com/katalog html
- https://merchury.com/ceny html
- https://www.googletagmanager.com/gtag/js?id=G-9Z0VMZDLND js

Questions about merchury.com

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