https://intel.com
Scanned Apr 15, 2026 · 35.1s
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 7 user data leaks before consent on intel.com, including Google Ads, Adform.
Security Headers
4/6 presentStrict-Transport-Security
max-age=31536000 ; includeSubDomains ; preload
Content-Security-Policy
frame-ancestors 'self' https://premiersupport.intel.com https://c0.avaamo.com *.intel.com; object-src 'self';
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
No GTM container detected — consent mode works best with Google Tag Manager
Post-Rejection Audit
Reject Button
Found
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)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
Google Ads (Google) loaded before consent: Google ad syndication and remarketing
Adform cookie "src_countrycode" set before consent — Unique value that records info about consecutive ads - includes: total impressions, daily impressions, total clicks, daily clicks, and last impression date
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)
Warnings5
Unknown third-party request to www.intel.nl before consent
localStorage key "__akfp_storage_test__" written before consent
sessionStorage key "waCheck" written before consent
localStorage key "_wap_user_consent" written before consent
localStorage key "_wap_user_consent_str" written before consent
Info8
Adobe (cdn) loaded before consent
OneTrust CMP (OneTrust) loaded before consent: OneTrust geo-lookup — determines which consent banner to show based on user location
OneTrust2 findingscdn.cookielaw.org, OptanonConsent
cdn.cookielaw.org, OptanonConsent
OneTrust (OneTrust) loaded before consent: OneTrust cookie consent management
OneTrust cookie "OptanonConsent" set before consent
Azure / Microsoft cookie "x-ms-cpim-geo" set before consent — Used as a hint to determine the resource tenants home geographic location.
Akamai bot management session — necessary for site protection
AWS Application Load Balancer — necessary for infrastructure
AWS Application Load Balancer — necessary for infrastructure
Compliant15
Microsoft Clarity5 findingsID trackedwww.clarity.ms, scripts.clarity.ms, i.clarity.ms, _clck, _clsk
www.clarity.ms, scripts.clarity.ms, i.clarity.ms, _clck, _clsk
Microsoft Clarity (Microsoft) loaded correctly after consent
Microsoft Clarity (Microsoft) loaded correctly after consent
Microsoft Clarity (Microsoft) loaded correctly after consent
Microsoft Clarity cookie "_clck" set correctly after consent
Microsoft Clarity cookie "_clsk" set correctly after consent
Google Analytics2 findingswww.googletagmanager.com, FPID
www.googletagmanager.com, FPID
GA4 (Google) loaded correctly after consent
Google Analytics cookie "FPID" set correctly after consent
Google Ads3 findingswww.google.com, _gcl_au, _gcl_ls
www.google.com, _gcl_au, _gcl_ls
Google Ads (Google) loaded correctly after consent
Google Ads cookie "_gcl_au" set correctly after consent
Google Ads (Google) wrote "_gcl_ls" to localStorage correctly after consent
OneTrust cookie "OptanonAlertBoxClosed" set correctly after consent
Adobe Analytics cookie "AMCV_AD2A1C8B53308E600A490D4D%40AdobeOrg" set correctly after consent
DoubleClick/Google Marketing cookie "IDE" set correctly after consent
Adobe Audience Manager2 findingsdemdex, dpm
demdex, dpm
Adobe Audience Manager cookie "demdex" set correctly after consent
Adobe Audience Manager cookie "dpm" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan intel.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com