https://mayoclinic.org
Scanned Apr 15, 2026 · 33.9s
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 26 user data leaks before consent on mayoclinic.org, including Akamai (Analytics Tracker), CHEQ (Advertising Tracker), Kameleoon (Advertising Tracker) and 2 more.
Security Headers
1/6 presentStrict-Transport-Security
Add HSTS header to enforce HTTPS connections and prevent downgrade attacks
Content-Security-Policy
Add a Content-Security-Policy header to prevent XSS and code injection attacks
X-Frame-Options
SAMEORIGIN
X-Content-Type-Options
Set X-Content-Type-Options to 'nosniff' to prevent MIME type sniffing
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
Not DetectedGoogle Consent Mode v2 was not found on this page. GCM v2 allows Google's tags to adjust their behavior based on user consent, and is required for compliant advertising measurement in the EU. Without it, your Google Ads and GA4 conversions may be impacted after consent is declined.
Post-Rejection Audit
Reject Button
Missing
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)Cookie settings link / floating button found
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
Critical10
Akamai (Analytics Tracker)2 findingss.go-mpulse.net, c.go-mpulse.net
s.go-mpulse.net, c.go-mpulse.net
Akamai (analytics) loaded before consent
Akamai (analytics) loaded before consent
CHEQ (Advertising Tracker)2 findingsnexus.ensighten.com, data.privacy.ensighten.com
nexus.ensighten.com, data.privacy.ensighten.com
CHEQ (advertising) loaded before consent
CHEQ (advertising) loaded before consent
Kameleoon (Advertising Tracker)2 findingsxih9lsprjt.kameleoon.io, na-data.kameleoon.io
xih9lsprjt.kameleoon.io, na-data.kameleoon.io
Kameleoon (advertising) loaded before consent
Kameleoon (advertising) loaded before consent
Medallia (analytics) loaded before consent
comScore (analytics) loaded before consent
No "reject all" option found — users cannot refuse non-essential cookies (ICO guidance requires this)
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)
Warnings18
Unknown was clicked but no consent storage was written — tags may continue firing as if consent was never given
LaunchDarkly2 findingsapp.launchdarkly.com, events.launchdarkly.com
app.launchdarkly.com, events.launchdarkly.com
LaunchDarkly (LaunchDarkly) loaded before consent: LaunchDarkly feature flag management
LaunchDarkly (LaunchDarkly) loaded before consent: LaunchDarkly event tracking endpoint
Possible server-side tag proxy at tagdelivery.mayoclinic.org — analytics data may be forwarded to third parties before consent. Browser scanning cannot verify downstream recipients; audit your GTM Server-side or CNAME configuration.
Unknown third-party request to transcend-cdn.com before consent
Unknown third-party request to clientstream.launchdarkly.com before consent
localStorage key "_boomr_clss" written before consent
localStorage key "dummy" written before consent
localStorage key "ak_a" written before consent
localStorage key "ld:65801b740c1ee60f44aadf37:eyJraW5kIjoidXNlciIsImtleSI6ImFub24tdXNlciJ9" written before consent
localStorage key "utilTest" written before consent
localStorage key "nextauth.message" written before consent
localStorage key "kameleoonData-xih9lsprjt" written before consent
localStorage key "kameleoonExperiment-378596" written before consent
localStorage key "MAYO_CLINIC_ENSIGHTEN_PRIVACY_TLD-www.mayoclinic.org" written before consent
localStorage key "ld:65801b740c1ee60f44aadf37:$diagnostics" written before consent
sessionStorage key "kameleoonTabId" written before consent
localStorage key "tealium_timing" written before consent
Info5
Kaltura (cdn) loaded before consent
Akamai cookie "AKA_A2" set before consent — Used for Akamai's Advanced Acceleration feature, intended to improve web performance
Tripadvisor cookie "RT" set before consent — This cookie is used to identify the visitor through an application. This allows the visitor to login to a website through their LinkedIn application for example.
Akamai bot manager — necessary for site protection
Cross-site request forgery token — security mechanism
Compliant2
Adobe Analytics (Adobe) loaded correctly after consent
localStorage availability probe (null) wrote "__storage_test__" to localStorage correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan mayoclinic.org →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com