Site profile
burghotel-strausberg.de
Built with slick-lightbox 0.2.12, stackedboost-shopify-assets 0.2.0, bootstrap-tabcollapse 0.2.6, skrollr-stylesheets 1.0.0. 5 pages and 13 stored files, last crawled 2026-10-08.
rank 13,450,365 4 libraries 0 identifiers 4 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 |
|---|---|---|
| slick-lightbox | 0.2.12 | 2026-10-08 |
| stackedboost-shopify-assets | 0.2.0 | 2026-10-08 |
| bootstrap-tabcollapse | 0.2.6 | 2026-10-08 |
| skrollr-stylesheets | 1.0.0 | 2026-10-08 |
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 burghotel-strausberg.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 |
|---|---|---|
| hotelclass.info | iframe | view source |
| wsrb.de | script stylesheet | view source |
| www.gastro.site | script | view source |
| www.openstreetmap.org | iframe | 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, 13 files, 420.5 KB; 4 libraries, 0 identifiers, 4 third-party hosts
4 libraries added
- stackedboost-shopify-assets 0.2.0
- skrollr-stylesheets 1.0.0
- bootstrap-tabcollapse 0.2.6
- slick-lightbox 0.2.12
5 third-party hosts added
13 files added
- https://burghotel-strausberg.de/ html
- https://burghotel-strausberg.de/hotel-arrangement.htm html
- https://burghotel-strausberg.de/veranstaltung-uebersicht.htm html
- https://burghotel-strausberg.de/restaurant-menu.htm html
- https://burghotel-strausberg.de/nachhaltigkeit.htm html
- https://burghotel-strausberg.de/intern/js/mcheck.js js
- https://burghotel-strausberg.de/intern/js/jquery-1.7.2.min.js js
- https://burghotel-strausberg.de/intern/js/jquery-migrate-1.2.1.min.js js
- https://burghotel-strausberg.de/intern/js/slick.min.js js
- https://burghotel-strausberg.de/intern/js/scripts.js js
- https://burghotel-strausberg.de/intern/js/introx.js js
- https://burghotel-strausberg.de/intern/js/jquery.bxslider.min.js js
- and 1 more
Questions about burghotel-strausberg.de
- How does PageSourceSearch know what burghotel-strausberg.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 burghotel-strausberg.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 burghotel-strausberg.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 burghotel-strausberg.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.