Site profile
dvv-pokal.de
Built with jquery 4.0.0, leaflet-tag-filter-button 0.0.5, jqwidgets-scripts 27.0.1, hexo-theme-redefine 2.9.0. 4 pages and 17 stored files, last crawled 2026-10-02.
rank 1,376,594 4 libraries 0 identifiers 7 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 |
|---|---|---|
| jquery | 4.0.0 | 2026-10-02 |
| leaflet-tag-filter-button | 0.0.5 | 2026-10-02 |
| jqwidgets-scripts | 27.0.1 | 2026-10-02 |
| hexo-theme-redefine | 2.9.0 | 2026-10-02 |
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 dvv-pokal.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 |
|---|---|---|
| mycrocast-webplayer.s3.eu-central-1.amazonaws.com | script | view source |
| tools.pinpoll.com | script | view source |
| twitter.com | connect | view source |
| widget.accessgo.de | script | view source |
| www.facebook.com | connect | view source |
| www.pinterest.com | connect | view source |
| www.w3.org | 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
4 pages, 17 files, 615.4 KB; 4 libraries, 0 identifiers, 7 third-party hosts
4 libraries added
- jquery 4.0.0
- jqwidgets-scripts 27.0.1
- hexo-theme-redefine 2.9.0
- leaflet-tag-filter-button 0.0.5
7 third-party hosts added
17 files added
- https://www.dvv-pokal.de/ html
- https://www.dvv-pokal.de/cms/home/pokalfinale/infos/shop.xhtml html
- https://www.dvv-pokal.de/rss/articleFeed.xhtml?c…,185869,185929,185868,766577093 html
- https://www.dvv-pokal.de/cms/home.xhtml html
- https://www.dvv-pokal.de/jakarta.faces.resource/…&v=15.0.12&e=15.0.12 js
- https://www.dvv-pokal.de/jakarta.faces.resource/…&v=15.0.12&e=15.0.12 js
- https://www.dvv-pokal.de/jakarta.faces.resource/…&v=15.0.12&e=15.0.12 js
- https://www.dvv-pokal.de/jakarta.faces.resource/…&v=15.0.12&e=15.0.12 js
- https://www.dvv-pokal.de/js/sams.js js
- https://www.dvv-pokal.de/cms/files/layout/js/layout.js?115 js
- https://www.dvv-pokal.de/jakarta.faces.resource/…f7d1f32880df3dadb0855ebff7214de js
- https://www.dvv-pokal.de/jakarta.faces.resource/…f7d1f32880df3dadb0855ebff7214de js
- and 5 more
Questions about dvv-pokal.de
- How does PageSourceSearch know what dvv-pokal.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 dvv-pokal.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 dvv-pokal.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 dvv-pokal.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.