Site profile
dav-mannheim.de
Built with jquery 1.9.1, lazysizes 5.3.2, json-db-admin 0.0.1, jsxgraph 1.13.3, jquery.flipster 1.1.6, kutty 0.6.0, @grigorov-it/mazer 2.2.0. 5 pages and 21 stored files, last crawled 2026-10-02.
rank 1,321,652 7 libraries 1 identifier 1 third-party host 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.9.1 | 2026-10-02 |
| lazysizes | 5.3.2 | 2026-10-02 |
| json-db-admin | 0.0.1 | 2026-10-02 |
| jsxgraph | 1.13.3 | 2026-10-02 |
| jquery.flipster | 1.1.6 | 2026-10-02 |
| kutty | 0.6.0 | 2026-10-02 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-02 |
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 |
|---|---|---|
| Matomo site id (Matomo) | \#1 | view source |
Third-party hosts
Hosts outside dav-mannheim.de 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 |
|---|---|---|
| widgets.yolawo.de | script iframe | 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, 20 files, 550.4 KB; 7 libraries, 1 identifier, 1 third-party host
7 libraries added
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- lazysizes 5.3.2
- json-db-admin 0.0.1
- jquery 1.9.1
- kutty 0.6.0
1 identifier added
- \#1 Matomo site id
2 third-party hosts added
20 files added
- https://www.dav-mannheim.de/ html
- https://www.dav-mannheim.de/kletterz-3/ html
- https://www.dav-mannheim.de/aktivitaeten/termine/ html
- https://www.dav-mannheim.de/touren/tourenprogramm/ html
- https://www.dav-mannheim.de/touren/ html
- https://www.dav-mannheim.de/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js
- https://www.dav-mannheim.de/wp-includes/js/jquer…jquery-migrate.min.js?ver=3.4.1 js
- https://www.dav-mannheim.de/wp-content/plugins/w…4e04b337ef55ce18556e65ee4775bef js
- https://www.dav-mannheim.de/wp-content/plugins/a…?ao_version=3.1.16 js
- https://www.dav-mannheim.de/wp-includes/js/dist/…?ver=7496969728ca0f95732d js
- https://www.dav-mannheim.de/wp-includes/js/dist/…?ver=781d11515ad3d91786ec js
- https://www.dav-mannheim.de/wp-content/plugins/c…/swv/js/index.js?ver=6.1.6 js
- and 8 more
Questions about dav-mannheim.de
- How does PageSourceSearch know what dav-mannheim.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 dav-mannheim.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 dav-mannheim.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 dav-mannheim.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.