Site profile
keb-freiburg.info
Built with webpack, @sentry-internal/replay 10.57.0, @vitest/utils 5.0.2, @betterbugs/web-sdk 0.0.47, holidoit 1.0.163, @anyline/anyline-js 56.1.3. 5 pages and 12 stored files, last crawled 2026-10-10.
6 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 |
|---|---|---|
| webpack | 2026-10-10 | |
| @sentry-internal/replay | 10.57.0 | 2026-10-10 |
| @vitest/utils | 5.0.2 | 2026-10-10 |
| @betterbugs/web-sdk | 0.0.47 | 2026-10-10 |
| holidoit | 1.0.163 | 2026-10-10 |
| @anyline/anyline-js | 56.1.3 | 2026-10-10 |
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) | piwik-sesam.w-commerce.de#373 | view source |
Third-party hosts
Hosts outside keb-freiburg.info 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 |
|---|---|---|
| static.kath-musterhausen.de | script stylesheet | 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, 12 files, 781.8 KB; 6 libraries, 1 identifier, 1 third-party host
6 libraries added
- @vitest/utils 5.0.2
- @anyline/anyline-js 56.1.3
- webpack
- holidoit 1.0.163
- @betterbugs/web-sdk 0.0.47
- @sentry-internal/replay 10.57.0
1 identifier added
- piwik-sesam.w-commerce.de#373 Matomo site id
2 third-party hosts added
12 files added
- https://keb-freiburg.info/ html
- https://keb-freiburg.info/login/ html
- https://keb-freiburg.info/ueber-uns/ html
- https://keb-freiburg.info/ueber-uns/vorstand-2/ html
- https://keb-freiburg.info/ueber-uns/satzung/ html
- https://keb-freiburg.info/public/js/3416.45ff8545dbd3c8a8c36f.js js
- https://keb-freiburg.info/public/js/2138.5df2b6b39933c9a326cc.js js
- https://keb-freiburg.info/public/frontend/js/main.ts.7689a467a57eb3df8d32.js js
- https://keb-freiburg.info/public/frontend/js/mod…ntry.ts.c72010afbeb351eb8a1b.js js
- https://keb-freiburg.info/public/frontend/js/inc…ntry.ts.a9dff8e8a6757cb3571f.js js
- https://keb-freiburg.info/public/js/2329.1b944919a49849ac24a9.js js
- https://keb-freiburg.info/public/js/4481.7b9d8e703e8968231587.js js
Questions about keb-freiburg.info
- How does PageSourceSearch know what keb-freiburg.info 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 keb-freiburg.info 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 keb-freiburg.info?
- 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 keb-freiburg.info?
- 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.