How does PageSourceSearch know what gorodtokyo.ru 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 gorodtokyo.ru 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 gorodtokyo.ru?

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 gorodtokyo.ru?

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

gorodtokyo.ru

Built with gtm, gtag, @vitest/utils 5.0.2. 4 pages and 10 stored files, last crawled 2026-10-08.

rank 14,267,723 3 libraries 9 identifiers 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-08
gtag		2026-10-08
@vitest/utils	5.0.2	2026-10-08

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 Ads conversion id (Google)	AW-939802575	view source
Google site verification (Google)	lyqPmUHI2Y_9NFDNTerIuYJlpZEXkJeV270LpM5lpCY	view source
Google site verification (Google)	oV1naSOg9t70WDqEfLdRaLTcGglgFNb5uKaiBaIQ50I	view source
Google Tag Manager container (Google)	GTM-P3CP4KQ	view source
Yandex site verification (Yandex)	398b1b5e2db7c20a	view source
Yandex site verification (Yandex)	4cbb21bd6b677ebf	view source
Yandex site verification (Yandex)	74bb492a34bc24dc	view source
Yandex site verification (Yandex)	7e00b1635cb9120e	view source
Yandex site verification (Yandex)	c9ff8d90cba90230	view source

Third-party hosts

Hosts outside gorodtokyo.ru 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
static-cs47764.itmatrix.ru	script stylesheet	view source
suggestions.dadata.ru	connect	view source
www.googletagmanager.com	iframe	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://gorodtokyo.ru/js/select-address.js?20261008165306	js	9.3 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/js/custom.js?20261008165306	js	22.5 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/js/custom_gtm.js?20261008164532	js	6.4 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/js/select-address.js?20261008155623	js	9.3 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/js/custom.js?20261008155623	js	22.5 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/akcii-i-skidki/	html	77.8 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/js/custom_gtm.js?20261008155623	js	6.4 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/cgi-bin/dsp.pl?cl=register&event=edit_form	html	24.8 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/brand/	html	76 KB	2026-10-08	2026-10-08
https://gorodtokyo.ru/	html	474.1 KB	2026-10-08	2026-10-08

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

4 pages, 10 files, 729 KB; 3 libraries, 9 identifiers, 3 third-party hosts
3 libraries added
- gtag
- @vitest/utils 5.0.2
- gtm
9 identifiers added
- AW-939802575 Google Ads conversion id
- GTM-P3CP4KQ Google Tag Manager container
- oV1naSOg9t70WDqEfLdRaLTcGglgFNb5uKaiBaIQ50I Google site verification
- lyqPmUHI2Y_9NFDNTerIuYJlpZEXkJeV270LpM5lpCY Google site verification
- 74bb492a34bc24dc Yandex site verification
- 7e00b1635cb9120e Yandex site verification
- 4cbb21bd6b677ebf Yandex site verification
- c9ff8d90cba90230 Yandex site verification
- 398b1b5e2db7c20a Yandex site verification
4 third-party hosts added
10 files added

Questions about gorodtokyo.ru

How does PageSourceSearch know what gorodtokyo.ru 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 gorodtokyo.ru 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 gorodtokyo.ru?: 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 gorodtokyo.ru?: 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.