Site profile
nibelungen-kurier.de
Built with @tabler/core 1.5.1, uigg 3.1.1, @grigorov-it/mazer 2.2.0, tinymce 8.9.2, hugerte 1.0.14, supafolio-sdk 1.4.1. 5 pages and 46 stored files, last crawled 2026-10-02.
rank 618,871 6 libraries 0 identifiers 3 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 |
|---|---|---|
| @tabler/core | 1.5.1 | 2026-10-02 |
| uigg | 3.1.1 | 2026-10-02 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-02 |
| tinymce | 8.9.2 | 2026-09-24 |
| hugerte | 1.0.14 | 2026-09-24 |
| supafolio-sdk | 1.4.1 | 2026-09-24 |
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 nibelungen-kurier.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 |
|---|---|---|
| www.serif.com | connect | view source |
| www.w3.org | connect | view source |
| www.w3schools.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, 26 files, 1.6 MB; 3 libraries, 0 identifiers, 3 third-party hosts
3 libraries added
- @grigorov-it/mazer 2.2.0
- @tabler/core 1.5.1
- uigg 3.1.1
3 third-party hosts added
26 files added
- https://nibelungen-kurier.de/ html
- https://nibelungen-kurier.de/suche html
- https://nibelungen-kurier.de/nachrichten html
- https://nibelungen-kurier.de/nachrichten/worms-und-ortsteile html
- https://nibelungen-kurier.de/nachrichten/aus-dem-nibelungenland html
- https://nibelungen-kurier.de/assets/js/framework.js?version=1790927287 js
- https://nibelungen-kurier.de/assets/js/script.js?version=1790927287 js
- https://nibelungen-kurier.de/assets/js/cjs_image_viewer.js?version=1790927287 js
- https://nibelungen-kurier.de/home/script-home.js?version=1790927287 js
- https://nibelungen-kurier.de/assets/js/framework.js?version=1790927291 js
- https://nibelungen-kurier.de/assets/js/script.js?version=1790927291 js
- https://nibelungen-kurier.de/assets/js/cjs_image_viewer.js?version=1790927291 js
- and 14 more
Questions about nibelungen-kurier.de
- How does PageSourceSearch know what nibelungen-kurier.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 nibelungen-kurier.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 nibelungen-kurier.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 nibelungen-kurier.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.