https://binance.com
Scanned Apr 15, 2026 · 42.0s
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 24 user data leaks before consent on binance.com, including Binance (Analytics Tracker).
Security Headers
0/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
Add X-Frame-Options header to prevent clickjacking attacks
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.
GTM container detected (GTM-M86QHGF) but no consent mode initialisation found. Add gtag('consent', 'default', ...) before your GTM snippet.
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
8585ms pre-consent
Google Tag Manager(GTM-M86QHGF)
Loaded 8585ms after page load — before the consent banner was detected (banner appeared at 9481ms). Per a 2022 German court ruling, GTM itself transmits the user's IP to Google pre-consent.
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)Found: OptanonConsent (OneTrust)
Record contains timestamp
Art. 7(1)Timestamp field detected
Record contains consent state
Art. 7(1)Accept/reject state detected
Record contains consent categories
Art. 7(1)Consent categories (analytics, marketing, etc.) not found in record
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
Critical3
Binance (Analytics Tracker)2 findingsbin.bnbstatic.com, public.bnbstatic.com
bin.bnbstatic.com, public.bnbstatic.com
Binance (analytics) loaded before consent
Binance (analytics) loaded before consent
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)
Warnings22
Google Tag Manager2 findingsID trackedwww.googletagmanager.com
www.googletagmanager.com
Google Tag Manager (Google) loaded before consent: Loads the GTM container which may trigger other tags
GTM loaded before consent banner — IP address transmitted to Google pre-consent (container: GTM-M86QHGF)
Unknown third-party request to fe4385362baa.02ef5c95.us-east-2.token.awswaf.com before consent
Unknown third-party request to api.saasexch.co before consent
Unknown third-party request to fe4385362baa.ead381d8.eu-west-1.token.awswaf.com before consent
Unknown third-party request to accounts.google.com before consent
Unknown third-party request to google.com before consent
Unknown third-party request to api.saasexch.com before consent
localStorage key "__BNC_FP_INFO__" written before consent
localStorage key "maskedBalance" written before consent
localStorage key "isHideSmallBalance" written before consent
localStorage key "favorites" written before consent
localStorage key "lngGuideKey" written before consent
localStorage key "deviceId" written before consent
sessionStorage key "__sak" written before consent
localStorage key "ss_incoming_params" written before consent
localStorage key "ss_webReferrer" written before consent
localStorage key "binance_cookie_manager_unknown_cookies" written before consent
localStorage key "_fc_aks" written before consent
localStorage key "__local_store_support__" written before consent
sessionStorage key "__session_storage_support__" written before consent
localStorage key "sawebjssdkpageleave-306279194" written before consent
Info4
OneTrust2 findingscdn.cookielaw.org, OptanonConsent
cdn.cookielaw.org, OptanonConsent
OneTrust (OneTrust) loaded before consent: OneTrust cookie consent management
OneTrust cookie "OptanonConsent" set before consent
Sentry (Sentry) loaded before consent: Sentry error reporting endpoint
OneTrust CMP (OneTrust) loaded before consent: OneTrust geo-lookup — determines which consent banner to show based on user location
Compliant6
Google Analytics5 findingswww.google-analytics.com, _gid, _gat_UA-162512367-1, _ga_3WP50LGEEC, _ga
www.google-analytics.com, _gid, _gat_UA-162512367-1, _ga_3WP50LGEEC, _ga
GA4 (Google) loaded correctly after consent
Google Analytics cookie "_gid" set correctly after consent
Google Analytics cookie "_gat_UA-162512367-1" set correctly after consent
Google Analytics cookie "_ga_3WP50LGEEC" set correctly after consent
Google Analytics cookie "_ga" set correctly after consent
OneTrust cookie "OptanonAlertBoxClosed" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan binance.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com