https://booking.com
Scanned Apr 15, 2026 · 43.2s
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 23 user data leaks before consent on booking.com, including Google Ads, Criteo (Advertising Tracker), RTBHouse (Advertising Tracker) and 4 more.
Security Headers
1/6 presentStrict-Transport-Security
max-age=63072000; includeSubDomains; preload
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
V2Consent Parameters
Issues (1)
No default consent call detected — consent mode may not be initialised correctly
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
2 vendors
Consent Mode
Not Detected
GTM Load
6008ms pre-consent
Google Tag Manager(GTM-5Q664QZ)
Loaded 6008ms after page load — before the consent banner was detected (banner appeared at 8294ms). 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.
✓ gtag('consent', 'update') call detected on rejection
Vendors firing after rejection (2)
| Vendor | Category | Timing | URL |
|---|---|---|---|
| Microsoft — Microsoft Ads | advertising | 20941ms | bat.bing.com |
| Google — Google Ads | advertising | 21471ms | pagead2.googlesyndication.com |
Consent Record Audit
PassConsent 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)Cookie settings link / floating button found
Tracker categories detected
Critical14
Criteo (Advertising Tracker)2 findingsID trackedgum.criteo.com, dynamic.criteo.com

gum.criteo.com, dynamic.criteo.com

Criteo (advertising) loaded before consent

Criteo (advertising) loaded before consent
Google Ads5 findingspagead2.googlesyndication.com, e0da242d4959748d12951ae298c24bc5.safeframe.googlesyndication.com, www.google.com, _gcl_au, _gcl_ls

pagead2.googlesyndication.com, e0da242d4959748d12951ae298c24bc5.safeframe.googlesyndication.com, www.google.com, _gcl_au, _gcl_ls

Google Ads (Google) loaded before consent: Google ad syndication and remarketing

Google Ads (Google) loaded before consent: Google ad syndication and remarketing

Google Ads (Google) loaded before consent: Google Consent Mode data collection for ad measurement

Google Ads cookie "_gcl_au" set before consent

Google Ads (Google) wrote "_gcl_ls" to localStorage before consent
RTBHouse (advertising) loaded before consent
The Trade Desk (tracker) loaded before consent

Microsoft Ads (Microsoft) loaded before consent: Microsoft Ads (Bing) UET conversion tracking

Adform cookie "uid" set before consent — Contains a unique ID to identify a user

Criteo cookie "cto_bundle" set before consent

Microsoft — Microsoft Ads fires after user rejected consent

Google — Google Ads fires after user rejected consent
Warnings11
Google Tag Manager2 findingsID trackedwww.googletagmanager.com

www.googletagmanager.com

Google Tag Manager loads before consent — this is expected and required for GCM v2 to initialise consent defaults before any tags fire

GTM loaded before consent banner — IP address transmitted to Google pre-consent (container: GTM-5Q664QZ)

Possible server-side tag proxy at gtp-mktg.booking.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 d8c14d4960ca.337f8b16.us-east-2.token.awswaf.com before consent
Unknown third-party request to cf.bstatic.com before consent
Unknown third-party request to t-cf.bstatic.com before consent
Unknown third-party request to q-xx.bstatic.com before consent
Unknown third-party request to r-xx.bstatic.com before consent
sessionStorage key "booking_product_session" written before consent
localStorage key "__rtbhouse.lid" written before consent
localStorage key "criteo_localstorage_check" 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

OneTrust CMP (OneTrust) loaded before consent: OneTrust geo-lookup — determines which consent banner to show based on user location
Naver (cdn) loaded before consent
Compliant16
Google Ads3 findingspagead2.googlesyndication.com, f60953dcd2937878e7ae5c157db65987.safeframe.googlesyndication.com, googleads.g.doubleclick.net

pagead2.googlesyndication.com, f60953dcd2937878e7ae5c157db65987.safeframe.googlesyndication.com, googleads.g.doubleclick.net

Google Ads (Google) loaded correctly after consent

Google Ads (Google) loaded correctly after consent

Google Ads (Google) loaded correctly after consent
Google Analytics5 findings_ga, FPID, FPAU, FPLC, _ga_A12345

_ga, FPID, FPAU, FPLC, _ga_A12345

Google Analytics cookie "_ga" set correctly after consent

Google Analytics cookie "FPID" set correctly after consent

Google Analytics cookie "FPAU" set correctly after consent

Google Analytics cookie "FPLC" set correctly after consent

Google Analytics cookie "_ga_A12345" set correctly after consent
Microsoft Ads2 findings_uetsid, _uetvid

_uetsid, _uetvid

Microsoft Ads cookie "_uetsid" set correctly after consent

Microsoft Ads cookie "_uetvid" set correctly after consent

Criteo cookie "cto_bundle" set correctly after consent

Bing / Microsoft cookie "MUID" set correctly after consent

DoubleClick/Google Marketing cookie "IDE" set 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

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 booking.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com