Site profile
bistum-osnabrueck.de
Built with magnific-popup 1.2.0, jsxgraph 1.13.3, jquery.flipster 1.1.6, @vitest/utils 5.0.2, @daily-co/daily-js 0.92.2, @appnest/masonry-layout 2.2.3, lazysizes-umd 3.0.1, @grigorov-it/mazer 2.2.0, @unhead/vue 3.4.1, @pdftron/webviewer 12.1.0. 5 pages and 31 stored files, last crawled 2026-10-02.
rank 586,861 10 libraries 1 identifier 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 |
|---|---|---|
| magnific-popup | 1.2.0 | 2026-10-02 |
| jsxgraph | 1.13.3 | 2026-10-02 |
| jquery.flipster | 1.1.6 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @daily-co/daily-js | 0.92.2 | 2026-10-02 |
| @appnest/masonry-layout | 2.2.3 | 2026-10-02 |
| lazysizes-umd | 3.0.1 | 2026-10-02 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-02 |
| @unhead/vue | 3.4.1 | 2026-09-24 |
| @pdftron/webviewer | 12.1.0 | 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 |
|---|---|---|
| Matomo site id (Matomo) | bistum-osnabrueck.de#1 | view source |
Third-party hosts
Hosts outside bistum-osnabrueck.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 |
|---|---|---|
| browser.sentry-cdn.com | connect | view source |
| cdn1.readspeaker.com | script | view source |
| twitter.com | connect | view source |
| www.example.com | connect | 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
5 pages, 30 files, 968 KB; 8 libraries, 1 identifier, 7 third-party hosts
8 libraries added
- @vitest/utils 5.0.2
- @daily-co/daily-js 0.92.2
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- magnific-popup 1.2.0
- lazysizes-umd 3.0.1
- @appnest/masonry-layout 2.2.3
1 identifier added
- bistum-osnabrueck.de#1 Matomo site id
7 third-party hosts added
30 files added
- https://bistum-osnabrueck.de/ html
- https://bistum-osnabrueck.de/newsletter/ html
- https://bistum-osnabrueck.de/live-gottesdienste/ html
- https://bistum-osnabrueck.de/arbeitsplatz-kirche/ html
- https://bistum-osnabrueck.de/kontaktuebersicht/ html
- https://bistum-osnabrueck.de/wp-content/plugins/…entry-browser.min.js?ver=8.12.0 js
- https://bistum-osnabrueck.de/wp-content/plugins/…/wp-sentry-init.js?ver=8.12.0 js
- https://bistum-osnabrueck.de/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js
- https://bistum-osnabrueck.de/wp-content/plugins/…recaptcha-gdpr-pow.js?ver=6.1.0 js
- https://bistum-osnabrueck.de/wp-content/plugins/…/mailin-front.js?ver=1782800846 js
- https://bistum-osnabrueck.de/wp-includes/js/dist…?ver=f0f188028580e8dc1255 js
- https://bistum-osnabrueck.de/wp-includes/js/dist…?ver=1dfe7db3940c23ea9216 js
- and 18 more
Questions about bistum-osnabrueck.de
- How does PageSourceSearch know what bistum-osnabrueck.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 bistum-osnabrueck.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 bistum-osnabrueck.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 bistum-osnabrueck.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.