Site profile
koda-optim.ru
Built with jquery 1.0.4, jssocials 1.5.0, yandex-metrica, accounting 0.4.1, @vitest/utils 5.0.2, easy-responsive-tabs 0.0.2. 5 pages and 22 stored files, last crawled 2026-10-06.
rank 12,050,958 6 libraries 0 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 |
|---|---|---|
| jquery | 1.0.4 | 2026-10-06 |
| jssocials | 1.5.0 | 2026-10-06 |
| yandex-metrica | 2026-10-06 | |
| accounting | 0.4.1 | 2026-10-06 |
| @vitest/utils | 5.0.2 | 2026-10-06 |
| easy-responsive-tabs | 0.0.2 | 2026-10-06 |
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 koda-optim.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 |
|---|---|---|
| mc.yandex.ru | script | view source |
| orphus.ru | connect | view source |
| static.flowplayer.org | connect | view source |
| www.adobe.com | 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, 22 files, 506.6 KB; 7 libraries, 0 identifiers, 4 third-party hosts
7 libraries added
- @vitest/utils 5.0.2
- jssocials 1.5.0
- accounting 0.4.1
- easy-responsive-tabs 0.0.2
- jquery 1.3
- jquery 1.0.4
- yandex-metrica
4 third-party hosts added
22 files added
- http://www.koda-optim.ru/ html
- http://www.koda-optim.ru/products/gas-detection html
- http://www.koda-optim.ru/news html
- http://www.koda-optim.ru/about html
- http://www.koda-optim.ru/contacts html
- http://www.koda-optim.ru/sites/koda/design/files/jquery-1.6.min.js js
- http://www.koda-optim.ru/sites/koda/design/files…/jquery.fancybox-1.3.4.pack.js js
- http://www.koda-optim.ru/sites/koda/design/files/flowplayer-3.2.6.min.js js
- http://www.koda-optim.ru/sites/koda/design/files/search.js js
- http://www.koda-optim.ru/system/modules/mailform/templates/mailform.js?145 js
- http://www.koda-optim.ru/sites/koda/design/files/scripts.js?781 js
- http://www.koda-optim.ru/sites/koda/design/files/orphus/orphus.js js
- and 10 more
Questions about koda-optim.ru
- How does PageSourceSearch know what koda-optim.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 koda-optim.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 koda-optim.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 koda-optim.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.