Site profile
geo.de
Built with jquery 3.3.1, gtm, @wix/design-system 1.328.0, @scandit/web-datacapture-core 8.6.0, @amplitude/amplitude-js-gtm 3.25.0, @docsearch/js 5.1.1. 1 page and 6 stored files.
rank 8,824 6 libraries 1 identifier 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 |
|---|---|---|
| jquery | 3.3.1 | 2026-09-24 |
| gtm | 2026-09-24 | |
| @wix/design-system | 1.328.0 | 2026-09-24 |
| @scandit/web-datacapture-core | 8.6.0 | 2026-09-24 |
| @amplitude/amplitude-js-gtm | 3.25.0 | 2026-09-24 |
| @docsearch/js | 5.1.1 | 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 |
|---|---|---|
| Google Tag Manager container (Google) | GTM-K47MJWS9 | view source |
Third-party hosts
The stored pages and scripts reference no host outside geo.de.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
| File | Kind | Size | Collected | Versions |
|---|---|---|---|---|
| https://code.jquery.com/jquery-3.3.1.min.js | js library | not fetched | 2026-09-24 | current |
| https://www.geo.de/jBlXrN1h/Svoe11v/7QqFy7l/xn/f…e36-65ca-6278-08b1-e95cfc441734 | js | 507.6 KB | 2026-09-24 | current |
| https://www.googletagmanager.com/gtm.js?id= | js library | not fetched | 2026-09-24 | current |
| https://www.geo.de/harasbycarob.js | js | 184.2 KB | 2026-09-24 | current |
| https://www.geo.de/public/main-PJIUGP6N.js | js | 512.3 KB | 2026-09-24 | current |
| https://www.geo.de/ | html | 350.7 KB | 2026-09-24 | current |
Timeline
No crawl has recorded a snapshot of this site yet; snapshots are written by every crawl from now on.
Questions about geo.de
- How does PageSourceSearch know what geo.de 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 geo.de 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 geo.de?
- 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 geo.de?
- 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.