Site profile
brandenburg-33.de
Built with chart.js 4.5.1, dompurify, leaflet 1.9.4, regenerator-runtime, @tarekraafat/autocomplete.js 10.2.10, @babel/runtime, iframe-resizer, hogan.js, leaflet.locatecontrol 0.90.1, leaflet.markercluster 1.5.3, vimeo-player, invariant and more. 5 pages and 18 stored files, last crawled 2026-10-02.
rank 1,392,911 33 libraries 0 identifiers 20 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 |
|---|---|---|
| chart.js | 4.5.1 | 2026-10-02 |
| dompurify | 2026-10-02 | |
| leaflet | 1.9.4 | 2026-10-02 |
| regenerator-runtime | 2026-10-02 | |
| @tarekraafat/autocomplete.js | 10.2.10 | 2026-10-02 |
| @babel/runtime | 2026-10-02 | |
| iframe-resizer | 2026-10-02 | |
| hogan.js | 2026-10-02 | |
| leaflet.locatecontrol | 0.90.1 | 2026-10-02 |
| leaflet.markercluster | 1.5.3 | 2026-10-02 |
| vimeo-player | 2026-10-02 | |
| invariant | 2026-10-02 | |
| css-loader | 2026-10-02 | |
| @justifi/webcomponents | 6.14.3 | 2026-10-02 |
| esri-leaflet | 3.0.19 | 2026-10-02 |
| hashcode | 2026-10-02 | |
| query-string-for-all | 2026-10-02 | |
| leaflet-gesture-handling | 1.2.2 | 2026-10-02 |
| baguettebox.js | 1.13.0 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| tdesign-vue | 1.16.1 | 2026-10-02 |
| @gstat/leaflet-gesture-handling | 1.2.8 | 2026-10-02 |
| tdesign-vue-next | 1.20.8 | 2026-10-02 |
| @memori.ai/memori-webcomponent | 8.3.3 | 2026-10-02 |
| @crystaldesign/diva-web-planner-react | 26.11.0 | 2026-10-02 |
| wonder-image | 2.1.2-alpha.4 | 2026-10-02 |
| comindware.core.ui | 2.1.149 | 2026-10-02 |
| develart-olzalogistic-pickup-points-widget | 1.8.19 | 2026-10-02 |
| @bmlt-enabled/croutonjs | 4.3.3 | 2026-10-02 |
| jupyter-leaflet | 0.20.0 | 2026-10-02 |
| @aarhus-university/au-designsystem-delphinus | 1.16.2 | 2026-09-25 |
| @pdftron/pdfjs-express-viewer | 8.7.5 | 2026-09-25 |
| h8k-components | 2.2.0 | 2026-09-25 |
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 brandenburg-33.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 |
|---|---|---|
| api.tomtom.com | connect | view source |
| api.whatsapp.com | connect | view source |
| classic-maps.openrouteservice.org | connect | view source |
| dev.virtualearth.net | connect | view source |
| leafletjs.com | connect | view source |
| legal.here.com | connect | view source |
| maps.hereapi.com | connect | view source |
| player.vimeo.com | connect | view source |
| static.arcgis.com | connect | view source |
| twitter.com | connect | view source |
| www.bing.com | connect | view source |
| www.esri.com | connect | view source |
| www.facebook.com | connect | view source |
| www.garmin.com | connect | view source |
| www.google.com | connect | view source |
| www.linkedin.com | connect | view source |
| www.mapsmarker.com | connect | view source |
| www.w3.org | connect | view source |
| www.youtube-nocookie.com | connect | view source |
| www.youtube.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, 16 files, 1.5 MB; 30 libraries, 0 identifiers, 20 third-party hosts
30 libraries added
- @vitest/utils 5.0.2
- comindware.core.ui 2.1.149
- regenerator-runtime
- @babel/runtime
- css-loader
- dompurify
- hashcode
- hogan.js
- iframe-resizer
- invariant
- query-string-for-all
- @crystaldesign/diva-web-planner-react 26.11.0
- and 18 more
20 third-party hosts added
16 files added
- https://brandenburg-33.de/ html
- https://brandenburg-33.de/karte/ html
- https://brandenburg-33.de/audiowalks/ html
- https://brandenburg-33.de/badbelzig/ html
- https://brandenburg-33.de/brandenburg/ html
- https://brandenburg-33.de/wp-content/plugins/sma…/dist/n2.min.js?ver=1c12b24c js
- https://brandenburg-33.de/wp-content/plugins/sma…er-frontend.min.js?ver=1c12b24c js
- https://brandenburg-33.de/wp-content/plugins/sma…/ss-simple.min.js?ver=1c12b24c js
- https://brandenburg-33.de/wp-content/plugins/sma…/w-bullet.min.js?ver=1c12b24c js
- https://brandenburg-33.de/wp-content/plugins/pod…/web-player/embed.js?ver=5.9.2 js
- https://brandenburg-33.de/wp-content/plugins/pod…/js/cache.js?ver=5.9.2 js
- https://brandenburg-33.de/wp-content/plugins/gal…/baguetteBox.min.js?ver=1.12.0 js
- and 4 more
Questions about brandenburg-33.de
- How does PageSourceSearch know what brandenburg-33.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 brandenburg-33.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 brandenburg-33.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 brandenburg-33.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.