Site profile
cuva.ru
No known library was recognised in its stored source. 6 pages and 6 stored files, last crawled 2026-10-02.
rank 1,129,779 0 libraries 5 identifiers 4 third-party hosts 1 crawl open the site
Technologies and libraries
No library file or bundled library code was recognised in the stored source. The site may use code of its own, load its libraries from a host the crawler does not fetch, or be too new in the index.
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 |
|---|---|---|
| Facebook domain verification (Meta) | bdrje31rpgcxkh02kko16q10wqyxi7 | view source |
| Google site verification (Google) | Jq5kX76niavSUo9agpKcu9ZUXN5lFylFeLUbBLc2b6I | view source |
| Pinterest site verification (Pinterest) | 99323ecd55cf0e91806fc9f7a0db8a6a | view source |
| Yandex site verification (Yandex) | 299bba661c4c8d04 | view source |
| Yandex site verification (Yandex) | 886c28451861119f | view source |
Third-party hosts
Hosts outside cuva.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 |
|---|---|---|
| code.jivosite.com | script | view source |
| neo.tildacdn.com | script | view source |
| points.boxberry.ru | script | view source |
| static.tildacdn.com | script stylesheet | view source |
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://cuva.ru/delivery-and-payment | html | 699.9 KB | 2026-10-02 | current |
| https://cuva.ru/contacts | html | 701.6 KB | 2026-10-02 | current |
| https://cuva.ru/about | html | 654.9 KB | 2026-10-02 | 2026-10-02 |
| https://cuva.ru/blog-new | html | 643.9 KB | 2026-10-02 | current |
| https://cuva.ru/ | html | 1.4 MB | 2026-10-02 | 2026-10-02 |
| https://cuva.ru/otzyvy | html | 760.9 KB | 2026-09-25 | current |
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, 5 files, 4 MB; 0 libraries, 5 identifiers, 4 third-party hosts
5 identifiers added
- Jq5kX76niavSUo9agpKcu9ZUXN5lFylFeLUbBLc2b6I Google site verification
- 299bba661c4c8d04 Yandex site verification
- 886c28451861119f Yandex site verification
- bdrje31rpgcxkh02kko16q10wqyxi7 Facebook domain verification
- 99323ecd55cf0e91806fc9f7a0db8a6a Pinterest site verification
5 third-party hosts added
5 files added
Questions about cuva.ru
- How does PageSourceSearch know what cuva.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 cuva.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 cuva.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 cuva.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.