Site profile
wir-pflegen-thueringen.de
Built with uikit 3.25.25, hapi-video 1.2.2, stackedboost-shopify-assets 0.2.0. 5 pages and 16 stored files, last crawled 2026-10-08.
rank 14,532,419 3 libraries 0 identifiers 7 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 |
|---|---|---|
| uikit | 3.25.25 | 2026-10-08 |
| hapi-video | 1.2.2 | 2026-10-08 |
| stackedboost-shopify-assets | 0.2.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 wir-pflegen-thueringen.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.eu.usercentrics.eu | script | view source |
| fonts.googleapis.com | stylesheet | view source |
| player.vimeo.com | connect | view source |
| privacy-proxy.usercentrics.eu | script | view source |
| sdp.eu.usercentrics.eu | script | view source |
| secure.fundraisingbox.com | script | view source |
| vimeo.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, 593 KB; 3 libraries, 0 identifiers, 7 third-party hosts
3 libraries added
- stackedboost-shopify-assets 0.2.0
- uikit 3.25.25
- hapi-video 1.2.2
7 third-party hosts added
16 files added
- https://wir-pflegen-thueringen.de/ html
- https://wir-pflegen-thueringen.de/login html
- https://wir-pflegen-thueringen.de/pflegende-ange…n-pflege-ploetzlich-noetig-wird html
- https://wir-pflegen-thueringen.de/pflegende-angehoerige/erste-schritte html
- https://wir-pflegen-thueringen.de/interessenvertretung/pflegende-eltern html
- https://wir-pflegen-thueringen.de/media/system/js/core.min.js?a3d8f8 js
- https://wir-pflegen-thueringen.de/media/system/j…oomla-hidden-mail.min.js?80d9c7 js
- https://wir-pflegen-thueringen.de/media/system/js/messages.min.js?9a4811 js
- https://wir-pflegen-thueringen.de/templates/yoot…/dist/js/uikit.min.js?5.0.46 js
- https://wir-pflegen-thueringen.de/templates/yoot…/uikit-icons-fuse.min.js?5.0.46 js
- https://wir-pflegen-thueringen.de/templates/yoot…/assets/site/js/theme.js?5.0.46 js
- https://wir-pflegen-thueringen.de/plugins/system…/js/accessibility.min.js?1.15 js
- and 4 more
Questions about wir-pflegen-thueringen.de
- How does PageSourceSearch know what wir-pflegen-thueringen.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 wir-pflegen-thueringen.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 wir-pflegen-thueringen.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 wir-pflegen-thueringen.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.