Site profile
summer-breeze.de
Built with gtm, photoswipe 5.4.4, @oiz/stzh-components 4.16.0, @vitest/utils 5.0.2, @dettalant/laymic 2.2.2, udesly-ad-banner 0.0.4. 5 pages and 11 stored files, last crawled 2026-10-02.
rank 520,515 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 |
|---|---|---|
| gtm | 2026-10-02 | |
| photoswipe | 5.4.4 | 2026-10-02 |
| @oiz/stzh-components | 4.16.0 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @dettalant/laymic | 2.2.2 | 2026-10-02 |
| udesly-ad-banner | 0.0.4 | 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 |
|---|---|---|
| Google Tag Manager container (Google) | GTM-NKN6G3HD | view source |
Third-party hosts
Hosts outside summer-breeze.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 |
|---|---|---|
| app.mailjet.com | script | 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, 11 files, 650.1 KB; 5 libraries, 1 identifier, 1 third-party host
5 libraries added
- @vitest/utils 5.0.2
- gtm
- photoswipe 5.4.4
- @oiz/stzh-components 4.16.0
- @dettalant/laymic 2.2.2
1 identifier added
- GTM-NKN6G3HD Google Tag Manager container
1 third-party host added
11 files added
- https://www.summer-breeze.de/en/ html
- https://www.summer-breeze.de/en/news/ html
- https://www.summer-breeze.de/en/app/ html
- https://www.summer-breeze.de/de/ html
- https://www.summer-breeze.de/en/newsletter/ html
- https://www.summer-breeze.de/wp-content/cache/bo…nfig-de.json.js?ver=3.0.0.12-37 js
- https://www.summer-breeze.de/wp-content/plugins/…ioritize.min.js?ver=3.0.0.12-37 js
- https://www.summer-breeze.de/wp-content/themes/s…?ver=202608011535 js
- https://www.summer-breeze.de/wp-includes/js/wp-embed.min.js?ver=6.8 js
- https://www.summer-breeze.de/wp-content/themes/s…/dist/index.js?ver=202608011535 js
- https://www.summer-breeze.de/wp-content/plugins/…labs-cookie.min.js?ver=3.0.0.12 js
Questions about summer-breeze.de
- How does PageSourceSearch know what summer-breeze.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 summer-breeze.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 summer-breeze.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 summer-breeze.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.