Site profile
energo-p.ru
Built with mustache 4.2.0, imask 7.6.1, jquery.mmenu 7.3.3, @vitest/utils 5.0.2, @peculiar/fortify-webcomponents 4.2.0, layui-layer 1.0.9. 5 pages and 26 stored files, last crawled 2026-10-07.
rank 13,098,045 6 libraries 0 identifiers 5 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 |
|---|---|---|
| mustache | 4.2.0 | 2026-10-07 |
| imask | 7.6.1 | 2026-10-07 |
| jquery.mmenu | 7.3.3 | 2026-10-07 |
| @vitest/utils | 5.0.2 | 2026-10-07 |
| @peculiar/fortify-webcomponents | 4.2.0 | 2026-10-07 |
| layui-layer | 1.0.9 | 2026-10-07 |
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 energo-p.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 |
|---|---|---|
| analytics.bitrix.info | connect | view source |
| i.ytimg.com | connect | view source |
| player.vimeo.com | connect | view source |
| www.w3.org | connect | view source |
| www.youtube-nocookie.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, 26 files, 1.4 MB; 6 libraries, 0 identifiers, 5 third-party hosts
6 libraries added
- @vitest/utils 5.0.2
- @peculiar/fortify-webcomponents 4.2.0
- layui-layer 1.0.9
- jquery.mmenu 7.3.3
- imask 7.6.1
- mustache 4.2.0
5 third-party hosts added
26 files added
- https://energo-p.ru/ html
- https://energo-p.ru/cart/ html
- https://energo-p.ru/about/ html
- https://energo-p.ru/contacts/ html
- https://energo-p.ru/saveenergy/ html
- https://energo-p.ru/bitrix/js/main/core/core.min.js?1732703447225422 js
- https://energo-p.ru/bitrix/js/pull/protobuf/protobuf.min.js?173270348776433 js
- https://energo-p.ru/bitrix/js/pull/protobuf/model.min.js?173270348714190 js
- https://energo-p.ru/bitrix/js/main/core/core_promise.min.js?17327034472490 js
- https://energo-p.ru/bitrix/js/rest/client/rest.client.min.js?17327034909240 js
- https://energo-p.ru/bitrix/js/pull/client/pull.client.min.js?173270348749664 js
- https://energo-p.ru/bitrix/js/main/popup/dist/ma…p.bundle.min.js?173270344765924 js
- and 14 more
Questions about energo-p.ru
- How does PageSourceSearch know what energo-p.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 energo-p.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 energo-p.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 energo-p.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.