Geo-redirect detected
https://deutschetelekom.de redirected to https://www.telekom.de/start.
https://deutschetelekom.de
Scanned Apr 15, 2026 · 36.8s
Your website score is
Grade
BannerConsent Banner
Yes
Regulatory Compliance
Multi-regulation overview — click any regulation for details
Technical scan only. A passing score does not equal legal compliance. Consult qualified legal counsel for your jurisdiction.
Tag Leak detected 22 user data leaks before consent on deutschetelekom.de, including Tealium (Analytics Tracker), Advertising Tracker, Dynatrace and 1 more.
Security Headers
4/6 presentStrict-Transport-Security
max-age=31536000; includeSubDomains
Content-Security-Policy
frame-ancestors 'self' accounts.login.idm.telekom.com;
X-Frame-Options
DENY
X-Content-Type-Options
nosniff
Referrer-Policy
Set a Referrer-Policy header to control how much referrer information is shared
Permissions-Policy
Add a Permissions-Policy header to restrict browser features like camera, microphone, and geolocation
Google Consent Mode
V2Consent Parameters
Issues (4)
ad_storage defaults to "granted" — should default to "denied" for GDPR compliance
ad_user_data defaults to "granted" — should default to "denied" for GDPR compliance
ad_personalization defaults to "granted" — should default to "denied" for GDPR compliance
No GTM container detected — consent mode works best with Google Tag Manager
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
Not detected
Consent Mode V2: Not Detected
Google Consent Mode was not detected on this site.
Consent Record Audit
Issues detectedConsent record stored after interaction
GDPR Art. 7(1)No consent record written — cannot prove consent was given
No CMP consent cookie or localStorage entry was found after the consent interaction. GDPR requires controllers to demonstrate consent was given.
Consent withdrawal mechanism accessible
GDPR Art. 7(3)No way for users to withdraw consent found on page
No cookie settings link, footer link, or floating consent button was detected. GDPR requires users to withdraw consent as easily as they gave it.
Why this matters
Under GDPR Article 7, controllers must be able to demonstrate that consent was given (Art. 7(1)) and ensure users can withdraw consent at any time, as easily as giving it (Art. 7(3)). Sites with no consent record or no withdrawal mechanism cannot legally rely on consent as a lawful basis.
Tracker categories detected
Critical7
Tealium (Analytics Tracker)2 findingstags-eu.tiqcdn.com, visitor-service-eu-central-1.tealiumiq.com
tags-eu.tiqcdn.com, visitor-service-eu-central-1.tealiumiq.com
Tealium (analytics) loaded before consent
Tealium (analytics) loaded before consent
advertising tracker at pix.telekom.de loaded before consent
Dynatrace cookie "dtCookiep9vvb6ny" set before consent — This cookie is used by RUM API, Dynatrace Real User Monitoring (RUM) gives you the power to know your customers by providing performance analysis in real time.
Bing / Microsoft cookie "CC" set before consent — Contains a country code as determined from your IP address.
No recognizable consent cookie or storage entry detected after interaction — GDPR Article 7(1) requires controllers to demonstrate consent was given (server-side storage cannot be verified)
No recognizable consent withdrawal mechanism detected — GDPR Article 7(3) requires users can withdraw consent as easily as giving it (cookie settings link or floating button expected)
Warnings17
Unknown was clicked but no consent storage was written — tags may continue firing as if consent was never given
Webtrekk (Webtrekk) wrote "wt_test" to localStorage before consent
Unknown third-party request to www.telekom.de before consent
Unknown third-party request to ebs01.telekom.de before consent
Unknown third-party request to www2.telekom.de before consent
Unknown third-party request to ebs10.telekom.de before consent
Unknown third-party request to ebs02.telekom.de before consent
Unknown third-party request to accounts.login.idm.telekom.com before consent
Unknown third-party request to omega-webfrontend.dsa.telekom-dienste.de before consent
Unknown third-party request to omega-dsa.telekom.de before consent
localStorage key "196380495960676" written before consent
localStorage key "316202539684123" written before consent
localStorage key "tealium_timing" written before consent
localStorage key "__storejs__test__" written before consent
localStorage key "modernizr" written before consent
localStorage key "omega.ui.settings.v1" written before consent
localStorage key "omega.ui.chat.v1" written before consent
Compliant22
Meta Pixel3 findingsID trackedwww.facebook.com, connect.facebook.net, _fbp
www.facebook.com, connect.facebook.net, _fbp
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel (Meta) loaded correctly after consent
Meta Pixel cookie "_fbp" set correctly after consent
GA4 (Google) loaded correctly after consent
Microsoft Ads3 findingsbat.bing.com, _uetsid, _uetvid
bat.bing.com, _uetsid, _uetvid
Microsoft Ads (Microsoft) loaded correctly after consent
Microsoft Ads cookie "_uetsid" set correctly after consent
Microsoft Ads cookie "_uetvid" set correctly after consent
Google Ads4 findingsgoogleads.g.doubleclick.net, www.googleadservices.com, _gcl_au, _gcl_ls
googleads.g.doubleclick.net, www.googleadservices.com, _gcl_au, _gcl_ls
Google Ads (Google) loaded correctly after consent
Google Ads (Google) loaded correctly after consent
Google Ads cookie "_gcl_au" set correctly after consent
Google Ads (Google) wrote "_gcl_ls" to localStorage correctly after consent
The Tradedesk2 findingsTDID, TDCPM
TDID, TDCPM
The Tradedesk cookie "TDID" set correctly after consent
The Tradedesk cookie "TDCPM" set correctly after consent
Bing / Microsoft cookie "MUID" set correctly after consent
ComScore cookie "pid" set correctly after consent
Emetric3 findingspid_short, pid_signature, ep
pid_short, pid_signature, ep
Emetric cookie "pid_short" set correctly after consent
Emetric cookie "pid_signature" set correctly after consent
Emetric cookie "ep" set correctly after consent
DoubleClick/Google Marketing cookie "IDE" set correctly after consent
Adform3 findingsC, adformfrpid, uid
C, adformfrpid, uid
Adform cookie "C" set correctly after consent
Adform cookie "adformfrpid" set correctly after consent
Adform cookie "uid" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan deutschetelekom.de →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com