Site profile
takeda-adhs.de
Built with gtm, onetrust, loadjs 4.3.0, @vitest/utils 5.0.2, jqwidgets-scripts 27.0.1, @drupal/once 1.0.1. 5 pages and 16 stored files, last crawled 2026-10-07.
rank 13,403,278 6 libraries 1 identifier 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 |
|---|---|---|
| gtm | 2026-10-07 | |
| onetrust | 2026-10-07 | |
| loadjs | 4.3.0 | 2026-10-07 |
| @vitest/utils | 5.0.2 | 2026-10-07 |
| jqwidgets-scripts | 27.0.1 | 2026-10-07 |
| @drupal/once | 1.0.1 | 2026-10-07 |
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-K4XLLJH | view source |
Third-party hosts
Hosts outside takeda-adhs.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 |
|---|---|---|
| cdn.cookielaw.org | script | view source |
| takedaconnect.com | script stylesheet | view source |
| www.googletagmanager.com | iframe connect | view source |
| www.w3.org | 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, 1.1 MB; 6 libraries, 1 identifier, 4 third-party hosts
6 libraries added
- @vitest/utils 5.0.2
- gtm
- jqwidgets-scripts 27.0.1
- @drupal/once 1.0.1
- loadjs 4.3.0
- onetrust
1 identifier added
- GTM-K4XLLJH Google Tag Manager container
6 third-party hosts added
16 files added
- https://www.takeda-adhs.de/ html
- https://www.takeda-adhs.de/fachkreis html
- https://www.takeda-adhs.de/adhs-wissen html
- https://www.takeda-adhs.de/adhs-wissen/adhs-symptome html
- https://www.takeda-adhs.de/adhs-wissen/adhs-ursachen html
- https://www.takeda-adhs.de/sites/default/files/j…5kKpLF9w2CfG-xMN9QGeS7I-y9ystJg js
- https://www.takeda-adhs.de/modules/contrib/google_tag/js/gtag.js?tm2nx5 js
- https://www.takeda-adhs.de/modules/contrib/google_tag/js/gtm.js?tm2nx5 js
- https://www.takeda-adhs.de/core/assets/vendor/jquery/jquery.min.js?v=4.0.0 js
- https://www.takeda-adhs.de/sites/default/files/j…5kKpLF9w2CfG-xMN9QGeS7I-y9ystJg js
- https://www.takeda-adhs.de/sites/default/files/j…UAa2zcM5wNc6MF0R22Q54J8_AIWLcjj js
- https://www.takeda-adhs.de/sites/default/files/j…UAa2zcM5wNc6MF0R22Q54J8_AIWLcjj js
- and 4 more
Questions about takeda-adhs.de
- How does PageSourceSearch know what takeda-adhs.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 takeda-adhs.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 takeda-adhs.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 takeda-adhs.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.