https://chase.com
Scanned Apr 15, 2026 · 24.6s
Your website score is
Grade
BannerConsent Banner
No
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 17 user data leaks before consent on chase.com, including Akamai (Analytics Tracker), Adobe Analytics.
Security Headers
4/6 presentStrict-Transport-Security
max-age=31536000
Content-Security-Policy
frame-ancestors 'none'
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
ch-ua-full-version-list=("https://*.chase.com"),ch-ua-platform-version=("https://*.chase.com"),ch-ua-arch=("https://*.chase.com"),ch-ua-model=("https://*.chase.com"),ch-ua-bitness=("https://*.chase.com"),ch-ua-wow64=("https://*.chase.com")
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)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
Akamai (Analytics Tracker)2 findingss2.go-mpulse.net, c.go-mpulse.net
s2.go-mpulse.net, c.go-mpulse.net
Akamai (analytics) loaded before consent
Akamai (analytics) loaded before consent
Adobe Analytics cookie "AMCV_EA673DFC5A2F19060A495C9C@AdobeOrg" set before consent
No consent banner detected — all cookies and tags fire without user 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)
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)
Warnings13
Possible server-side tag proxy at analytics.chase.com — 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 static.chasecdn.com before consent
Unknown third-party request to trial-eum-clientnsv4-s.akamaihd.net before consent
Unknown third-party request to trial-eum-clienttons-s.akamaihd.net before consent
Unknown third-party request to 2etgclk7mvfnq2o74elq-ppsl8a-65ddc12fa-clientnsv4-s.akamaihd.net before consent
Unknown third-party request to 209-38-97-45_s-96-16-53-145_ts-1776279831-clienttons-s.akamaihd.net before consent
localStorage key "__SPLITSOFTWARE__" written before consent
localStorage key "_boomr_clss" written before consent
sessionStorage key "pages-visited" written before consent
localStorage key "_boomr_akamaiXhrRetry" written before consent
localStorage key "__dip_bs_flag" written before consent
localStorage key "FTzyeq12rr" written before consent
localStorage key "l_FTzyeq12rr" written before consent
Info2
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.
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan chase.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com