Site profile
sigma-service.ru
Built with yandex-metrica, @vitest/utils 5.0.2. 5 pages and 12 stored files, last crawled 2026-10-08.
rank 13,921,088 2 libraries 3 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 |
|---|---|---|
| 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) | AFft73KQ7erkj-fe4gt6KKfCORyDu-9G-WypdI913DE | view source |
| Yandex Metrica counter (Yandex) | 5258530 | view source |
| Yandex site verification (Yandex) | 3e28460e7db646e4 | view source |
Third-party hosts
Hosts outside sigma-service.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 |
|---|---|---|
| api-maps.yandex.ru | script | view source |
| holaone.ru | script | view source |
| www.w3.org | 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, 12 files, 1.6 MB; 2 libraries, 3 identifiers, 3 third-party hosts
2 libraries added
- yandex-metrica
- @vitest/utils 5.0.2
3 identifiers added
- 5258530 Yandex Metrica counter
- AFft73KQ7erkj-fe4gt6KKfCORyDu-9G-WypdI913DE Google site verification
- 3e28460e7db646e4 Yandex site verification
3 third-party hosts added
12 files added
- https://sigma-service.ru/ html
- https://sigma-service.ru/about/news/ html
- https://sigma-service.ru/about/ html
- https://sigma-service.ru/about/contacts/ html
- https://sigma-service.ru/stock/novye/ html
- https://sigma-service.ru/site/templates/scripts/main.js?v=2 js
- https://sigma-service.ru/site/templates/scripts/additional.js?v=20261007 js
- https://sigma-service.ru/site/templates/scripts/events.js?v=5 js
- https://sigma-service.ru/site/templates/scripts/cars.js?v=2011 js
- https://sigma-service.ru/site/templates/scripts/map.js?v=20260821c js
- https://sigma-service.ru/site/templates/scripts/cvw.js?v=2 js
- https://sigma-service.ru/site/templates/scripts/stock-active-filters.js?v=9 js
Questions about sigma-service.ru
- How does PageSourceSearch know what sigma-service.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 sigma-service.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 sigma-service.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 sigma-service.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.