Geo-redirect detected
https://mango.com redirected to https://shop.mango.com/gb/en.
https://mango.com
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 5 user data leaks before consent on mango.com.
Security Headers
3/6 presentStrict-Transport-Security
max-age=31536000 ; includeSubDomains
Content-Security-Policy
Add a Content-Security-Policy header to prevent XSS and code injection attacks
X-Frame-Options
SAMEORIGIN
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
analytics_storage defaults to "granted" — should default to "denied" for GDPR compliance
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
3 vendors
Consent Mode
Basic
GTM Load
After consent
Google Tag Manager(GTM-W5MKJLK)
Loaded after consent banner detected — no pre-consent IP transmission detected.
Consent Mode V2: Basic
Basic Consent Mode — anonymised pings still fire after rejection. Permitted by Google but legally contested under PECR.
Vendors firing after rejection (3)
| Vendor | Category | Timing | URL |
|---|---|---|---|
| Google — Google Tag Manager | Basic CM ping | 17129ms | www.googletagmanager.com |
| Google — GA4 | Basic CM ping | 17136ms | www.googletagmanager.com |
| Google — GA4 | Basic CM ping | 22808ms | region1.google-analytics.com |
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
Critical2
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)
Warnings7
Unknown was clicked but no consent storage was written — tags may continue firing as if consent was never given
Google — Google Tag Manager ping fires after rejection (Basic Consent Mode — anonymised, legal grey zone)
Google — GA4 ping fires after rejection (Basic Consent Mode — anonymised, legal grey zone)
localStorage key "dummy" written before consent
localStorage key "__akfp_storage_test__" written before consent
sessionStorage key "previous_url" written before consent
localStorage key "customerToken" written before consent
Info3
Twitch cookie "auth-token" set before consent — This cookie is used for authentication & authorization
Akamai bot management session — necessary for site protection
Akamai bot manager — necessary for site protection
Compliant16
Google Tag Manager (Google) loaded correctly after consent
Google Ads3 findingswww.googleadservices.com, googleads.g.doubleclick.net, _gcl_ls
www.googleadservices.com, googleads.g.doubleclick.net, _gcl_ls
Google Ads (Google) loaded correctly after consent
Google Ads (Google) loaded correctly after consent
Google Ads (Google) wrote "_gcl_ls" to localStorage correctly after consent
Google2 findingsGCLB, FPGSID
GCLB, FPGSID
Google cookie "GCLB" set correctly after consent
Google cookie "FPGSID" set correctly after consent
Dynatrace4 findingsrxVisitor, rxvt, dtPC, dtCookie
rxVisitor, rxvt, dtPC, dtCookie
Dynatrace cookie "rxVisitor" set correctly after consent
Dynatrace cookie "rxvt" set correctly after consent
Dynatrace cookie "dtPC" set correctly after consent
Dynatrace cookie "dtCookie" set correctly after consent
Google Analytics3 findings_ga, _ga_NC306DXESG, FPAU
_ga, _ga_NC306DXESG, FPAU
Google Analytics cookie "_ga" set correctly after consent
Google Analytics cookie "_ga_NC306DXESG" set correctly after consent
Google Analytics cookie "FPAU" set correctly after consent
Meta Pixel cookie "_fbp" set correctly after consent
DoubleClick/Google Marketing2 findingstest_cookie, IDE
test_cookie, IDE
DoubleClick/Google Marketing cookie "test_cookie" set correctly after consent
DoubleClick/Google Marketing cookie "IDE" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan mango.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com