Site profile
grade-up.at
Built with @vitest/utils 5.0.2. 5 pages and 17 stored files, last crawled 2026-10-08.
rank 14,105,280 1 library 3 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 |
|---|---|---|
| @vitest/utils | 5.0.2 | 2026-10-08 |
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) | dcarahmcqrcn1moyslhi2fecwvveyc | view source |
| Google site verification (Google) | _AY6CBiFSv2KX_EPoHH8TSEoAMBXPqBIeQUMW93cJBE | view source |
| TikTok pixel id (TikTok) | D47TPN3C77U2U4VHNK4G | view source |
Third-party hosts
Hosts outside grade-up.at 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 |
|---|---|---|
| onecdn.io | script stylesheet | view source |
| www.cloudflare.com | connect | view source |
| www.digistore24-scripts.com | script | view source |
| www.facebook.com | connect | view source |
| www.tiktok.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, 17 files, 4.3 MB; 1 library, 3 identifiers, 5 third-party hosts
1 library added
- @vitest/utils 5.0.2
3 identifiers added
- _AY6CBiFSv2KX_EPoHH8TSEoAMBXPqBIeQUMW93cJBE Google site verification
- dcarahmcqrcn1moyslhi2fecwvveyc Facebook domain verification
- D47TPN3C77U2U4VHNK4G TikTok pixel id
6 third-party hosts added
17 files added
- https://grade-up.at/ html
- https://grade-up.at/gradeup-englisch html
- https://grade-up.at/grade-up-deutsch html
- https://grade-up.at/grade-up-rechnungswesen html
- https://grade-up.at/grade-up-mathe html
- https://grade-up.at/one-runtime/react.mjs js
- https://grade-up.at/one-runtime/react-dom.mjs js
- https://grade-up.at/one-runtime/react-dom-client.mjs js
- https://grade-up.at/one-runtime/react-jsx-runtime.mjs js
- https://grade-up.at/one-runtime/mobx.mjs js
- https://grade-up.at/one-runtime/mobx-react.mjs js
- https://grade-up.at/one-runtime/framer-motion.mjs js
- and 5 more
Questions about grade-up.at
- How does PageSourceSearch know what grade-up.at 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 grade-up.at 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 grade-up.at?
- 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 grade-up.at?
- 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.