Site profile
werkbund-werkstatt.de
Built with @popperjs/core 2.11.8, friendly-challenge 0.9.20, @vitest/utils 5.0.2, @lanyundev/blog-static 1.4.18. 5 pages and 15 stored files, last crawled 2026-10-07.
rank 13,062,792 4 libraries 0 identifiers 5 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 |
|---|---|---|
| @popperjs/core | 2.11.8 | 2026-10-07 |
| friendly-challenge | 0.9.20 | 2026-10-07 |
| @vitest/utils | 5.0.2 | 2026-10-07 |
| @lanyundev/blog-static | 1.4.18 | 2026-10-07 |
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 werkbund-werkstatt.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.friendlycaptcha.com | connect | view source |
| cloud.ccm19.de | script | view source |
| friendlycaptcha.com | connect | view source |
| www.w3.org | connect | view source |
| www.youtube-nocookie.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, 15 files, 4.2 MB; 4 libraries, 0 identifiers, 5 third-party hosts
4 libraries added
- @vitest/utils 5.0.2
- @popperjs/core 2.11.8
- friendly-challenge 0.9.20
- @lanyundev/blog-static 1.4.18
5 third-party hosts added
15 files added
- https://werkbund-werkstatt.de/ html
- https://werkbund-werkstatt.de/online-infotag html
- https://werkbund-werkstatt.de/infotage/infotage-neue-termine html
- https://werkbund-werkstatt.de/programm/werkstatt-jahr html
- https://werkbund-werkstatt.de/werkstaetten/werkstattjahr/seminare-workshops html
- https://werkbund-werkstatt.de/typo3temp/assets/c…555027433f626bc6e.js?1774542407 js
- https://werkbund-werkstatt.de/typo3temp/assets/c…31f5aed8688e09fdc.js?1787222557 js
- https://werkbund-werkstatt.de/typo3temp/assets/c…7a14b46bd682225da.js?1786980032 js
- https://werkbund-werkstatt.de/typo3conf/ext/t3sb…/t3sbHelper.js?1741859954 js
- https://werkbund-werkstatt.de/typo3conf/ext/t3sb…-dropdown-ml-hack.js?1741859954 js
- https://werkbund-werkstatt.de/typo3temp/assets/j…46e20adbc2e0a1094.js?1690360734 js
- https://werkbund-werkstatt.de/typo3temp/assets/t…tstrap_4c313585cd.js?1747141914 js
- and 3 more
Questions about werkbund-werkstatt.de
- How does PageSourceSearch know what werkbund-werkstatt.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 werkbund-werkstatt.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 werkbund-werkstatt.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 werkbund-werkstatt.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.