Site profile
classic-solution.ru
Built with jquery 1.12.1, yandex-metrica, @doctorassistant/daai-component 2.5.2, @vitest/utils 5.0.2. 5 pages and 59 stored files, last crawled 2026-10-09.
4 libraries 0 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 |
|---|---|---|
| jquery | 1.12.1 | 2026-10-09 |
| yandex-metrica | 2026-10-09 | |
| @doctorassistant/daai-component | 2.5.2 | 2026-10-09 |
| @vitest/utils | 5.0.2 | 2026-10-09 |
Tracking, tag and verification IDs
No analytics property, tag manager container, pixel or site-verification token was found in the stored source.
Third-party hosts
Hosts outside classic-solution.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.jquery.com | script | view source |
| mc.yandex.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, 59 files, 1.4 MB; 4 libraries, 0 identifiers, 3 third-party hosts
4 libraries added
- @vitest/utils 5.0.2
- @doctorassistant/daai-component 2.5.2
- yandex-metrica
- jquery 1.12.1
3 third-party hosts added
59 files added
- https://www.classic-solution.ru/ html
- https://www.classic-solution.ru/products/screens/ html
- https://www.classic-solution.ru/products/iboards/interactive_displays/ html
- https://www.classic-solution.ru/products/mounts/ html
- https://www.classic-solution.ru/products/cams/ html
- https://www.classic-solution.ru/bitrix/js/main/core/core.min.js?1732535659225181 js
- https://www.classic-solution.ru/bitrix/cache/js/…rnel_main_v1.js?178827368210092 js
- https://www.classic-solution.ru/bitrix/js/ui/dex…3.bundle.min.js?169702667488274 js
- https://www.classic-solution.ru/bitrix/js/main/c…/core_ls.min.js?16833180687365 js
- https://www.classic-solution.ru/bitrix/js/main/c…me_cache.min.js?170619028311210 js
- https://www.classic-solution.ru/bitrix/cache/js/…d06b34fc23c_v1.js?1788273682860 js
- https://www.classic-solution.ru/bitrix/templates/24565new/maxheight.js js
- and 47 more
Questions about classic-solution.ru
- How does PageSourceSearch know what classic-solution.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 classic-solution.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 classic-solution.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 classic-solution.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.