How does PageSourceSearch know what 6699.by 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 6699.by 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 6699.by?

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 6699.by?

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

6699.by

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

rank 13,842,662 3 libraries 11 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-08
yandex-metrica		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 site verification (Google)	-ep2u43WykwnPzEh2nehNCI_YXdQr4dGWbpaQ5rgL0M	view source
Google site verification (Google)	-vzM_QV6JpalfV1Lja5lETX92v8ZuFCN7NY5En95U0Y	view source
Google site verification (Google)	HyC-rqSBuGuoh2XhrKZHwAzOFRA5k-7Sncb55CnV8zg	view source
Google Tag Manager container (Google)	GTM-PSTSP98	view source
Pinterest site verification (Pinterest)	927ce54f8cbc804700b43cf2c6991b94	view source
Yandex Metrica counter (Yandex)	66701341	view source
Yandex site verification (Yandex)	00de2d81cdaada30	view source
Yandex site verification (Yandex)	3b6601f3561bcb9a	view source
Yandex site verification (Yandex)	5edbf96555c7df05	view source
Yandex site verification (Yandex)	91c762a12edfb01f	view source
Yandex site verification (Yandex)	f5c1dbf7e620c896	view source

Third-party hosts

Hosts outside 6699.by 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
cdn-f.vigbo.com	stylesheet	view source
cdn-s.vigbo.com	script stylesheet	view source
cdn-sh.vigbo.com	script stylesheet	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 5) }. 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://6699.by/contacts	html	78.6 KB	2026-10-08	2026-10-08
https://6699.by/about	html	64.3 KB	2026-10-08	2026-10-08
https://6699.by/blog	html	95.9 KB	2026-10-08	2026-10-08
https://6699.by/	html	137.6 KB	2026-10-08	2026-10-08
https://6699.by/shop/cart	html	47.7 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

5 pages, 5 files, 424 KB; 3 libraries, 11 identifiers, 4 third-party hosts
3 libraries added
- gtm
- yandex-metrica
- @vitest/utils 5.0.2
11 identifiers added
- GTM-PSTSP98 Google Tag Manager container
- 66701341 Yandex Metrica counter
- HyC-rqSBuGuoh2XhrKZHwAzOFRA5k-7Sncb55CnV8zg Google site verification
- -vzM_QV6JpalfV1Lja5lETX92v8ZuFCN7NY5En95U0Y Google site verification
- -ep2u43WykwnPzEh2nehNCI_YXdQr4dGWbpaQ5rgL0M Google site verification
- f5c1dbf7e620c896 Yandex site verification
- 5edbf96555c7df05 Yandex site verification
- 3b6601f3561bcb9a Yandex site verification
- 00de2d81cdaada30 Yandex site verification
- 91c762a12edfb01f Yandex site verification
- 927ce54f8cbc804700b43cf2c6991b94 Pinterest site verification
6 third-party hosts added
5 files added
- https://6699.by/ html
- https://6699.by/shop/cart html
- https://6699.by/blog html
- https://6699.by/about html
- https://6699.by/contacts html

Questions about 6699.by

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