Site profile
drei-fluesse-theater.de
Built with jquery 1.9.1, bootstrap-tabcollapse 0.2.6, jquery.scrollup 2.4.1, bootstrap-typeahead 2.3.2, x-editable-bs5 1.5.8, easy-responsive-tabs 0.0.2, jquery-migrate 1.1.1, owlcarousel 1.3.3. 5 pages and 13 stored files, last crawled 2026-10-03.
rank 1,612,980 8 libraries 0 identifiers 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 |
|---|---|---|
| jquery | 1.9.1 | 2026-10-03 |
| bootstrap-tabcollapse | 0.2.6 | 2026-10-03 |
| jquery.scrollup | 2.4.1 | 2026-10-03 |
| bootstrap-typeahead | 2.3.2 | 2026-10-03 |
| x-editable-bs5 | 1.5.8 | 2026-10-03 |
| easy-responsive-tabs | 0.0.2 | 2026-10-03 |
| jquery-migrate | 1.1.1 | 2026-09-25 |
| owlcarousel | 1.3.3 | 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 drei-fluesse-theater.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 |
|---|---|---|
| shop.ticketpay.de | 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, 287.2 KB; 6 libraries, 0 identifiers, 1 third-party host
6 libraries added
- easy-responsive-tabs 0.0.2
- x-editable-bs5 1.5.8
- jquery 1.9.1
- bootstrap-tabcollapse 0.2.6
- jquery.scrollup 2.4.1
- bootstrap-typeahead 2.3.2
1 third-party host added
13 files added
- https://drei-fluesse-theater.de/ html
- https://drei-fluesse-theater.de/index.php html
- https://drei-fluesse-theater.de/spielplan.php html
- https://drei-fluesse-theater.de/theater.php html
- https://drei-fluesse-theater.de/presse.php html
- https://drei-fluesse-theater.de/themes/theater/js/jquery.js js
- https://drei-fluesse-theater.de/themes/theater/js/jquery-migrate-1.1.1.js js
- https://drei-fluesse-theater.de/themes/theater/js/jquery.easing.1.3.js js
- https://drei-fluesse-theater.de/themes/theater/js/superfish.js js
- https://drei-fluesse-theater.de/themes/theater/js/jquery.mobilemenu.js js
- https://drei-fluesse-theater.de/themes/theater/j…jquery.mobile.customized.min.js js
- https://drei-fluesse-theater.de/themes/theater/js/camera.js js
- and 1 more
Questions about drei-fluesse-theater.de
- How does PageSourceSearch know what drei-fluesse-theater.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 drei-fluesse-theater.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 drei-fluesse-theater.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 drei-fluesse-theater.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.