Site profile
tpu.ru
Built with bromcom-ui 2.12.3, @tarekraafat/autocomplete.js 10.2.10, cdn4script 2.2.4, c2pa 0.30.17, css-vars-ponyfill 2.4.9, vconsole 3.15.1, immortal-db 1.1.0, @partslogic/ui 2.0.7, yandex-metrica, vue2-datepicker 3.11.1, formiojs 4.21.7, face-age 2.4.6 and more. 5 pages and 20 stored files.
rank 26,888 38 libraries 2 identifiers 0 third-party hosts 0 crawls 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 |
|---|---|---|
| bromcom-ui | 2.12.3 | 2026-10-01 |
| @tarekraafat/autocomplete.js | 10.2.10 | 2026-10-01 |
| cdn4script | 2.2.4 | 2026-10-01 |
| c2pa | 0.30.17 | 2026-10-01 |
| css-vars-ponyfill | 2.4.9 | 2026-10-01 |
| vconsole | 3.15.1 | 2026-10-01 |
| immortal-db | 1.1.0 | 2026-10-01 |
| @partslogic/ui | 2.0.7 | 2026-10-01 |
| yandex-metrica | 2026-10-01 | |
| vue2-datepicker | 3.11.1 | 2026-10-01 |
| formiojs | 4.21.7 | 2026-10-01 |
| face-age | 2.4.6 | 2026-10-01 |
| json-db-admin | 0.0.1 | 2026-10-01 |
| supafolio-sdk | 1.4.1 | 2026-10-01 |
| docsify-themeable | 0.9.0 | 2026-10-01 |
| @opentok/client | 2.35.2 | 2026-10-01 |
| @toast-ui/calendar | 2.1.3 | 2026-10-01 |
| @vitest/utils | 5.0.2 | 2026-10-01 |
| @memori.ai/memori-webcomponent | 8.3.3 | 2026-10-01 |
| @accusoft/pdf-viewer | 3.11.158639 | 2026-10-01 |
| @widgetti/solara-vuetify-app | 10.1.1 | 2026-10-01 |
| chobitsu | 1.8.6 | 2026-10-01 |
| @fsl-app/erm-app | 1.1.3 | 2026-10-01 |
| @figmania/svg-animate | 1.3.0 | 2026-10-01 |
| sheryjs | 1.0.0-beta.0.1.8 | 2026-10-01 |
| peachy-booking-flow | 1.11.6 | 2026-10-01 |
| @story-telling-reporter/react-embed-code-generator | 2.2.20 | 2026-10-01 |
| scatter-js | 2.5.2 | 2026-10-01 |
| @unbabel/ui | 5.19.0 | 2026-10-01 |
| @vismaux/vud | 1.8.4 | 2026-10-01 |
| alpheios-components | 3.4.3-incr-3.4.x.20220428394 | 2026-10-01 |
| js-heo | 1.0.13 | 2026-10-01 |
| @genpact/genome.mfe.v6-app | 1.0.328 | 2026-10-01 |
| @voxeet/voxeet-web-sdk | 3.11.1 | 2026-10-01 |
| smooothy | 0.0.35 | 2026-10-01 |
| amazon-ivs-web-broadcast | 1.40.0 | 2026-10-01 |
| bkl-request-demo | 1.0.8 | 2026-10-01 |
| pushfeedback | 0.1.85 | 2026-09-24 |
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 |
|---|---|---|
| Yandex Metrica counter (Yandex) | 24683258 | view source |
| Yandex Metrica counter (Yandex) | 84773887 | view source |
Third-party hosts
The stored pages and scripts reference no host outside tpu.ru.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about tpu.ru
- How does PageSourceSearch know what tpu.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 tpu.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 tpu.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 tpu.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.