https://harvard.edu
Scanned Apr 15, 2026 · 21.1s
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 24 user data leaks before consent on harvard.edu, including WordPress VIP (Analytics Tracker), Advertising Tracker, GA4 and 5 more.
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-5SGSF6G) but no consent mode initialisation found. Add gtag('consent', 'default', ...) before your GTM snippet.
Post-Rejection Audit
Reject Button
Missing
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
252ms pre-consent
Google Tag Manager(GTM-5SGSF6G)
Loaded 252ms after page load — before the consent banner was detected. 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)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
Critical21
Google Analytics6 findingsID trackedregion1.analytics.google.com, www.google-analytics.com, _gid, _gat_UA-2923555-1, _ga_KBLBYHG5EP, _ga
region1.analytics.google.com, www.google-analytics.com, _gid, _gat_UA-2923555-1, _ga_KBLBYHG5EP, _ga
GA4 (Google) loaded before consent: Sends pageview and event data to Google Analytics
GA4 (Google) loaded before consent: Sends pageview and event data to Google Analytics
Google Analytics cookie "_gid" set before consent
Google Analytics cookie "_gat_UA-2923555-1" set before consent
Google Analytics cookie "_ga_KBLBYHG5EP" set before consent
Google Analytics cookie "_ga" set before consent
Google (tracker) loaded before consent
Meta Pixel3 findingsID trackedwww.facebook.com, connect.facebook.net, _fbp
www.facebook.com, connect.facebook.net, _fbp
Meta Pixel (Meta) loaded before consent: Meta Pixel tracking endpoint
Meta Pixel (Meta) loaded before consent: Sends user data to Meta for ad targeting and conversion tracking
Meta Pixel cookie "_fbp" set before consent
WordPress VIP (Analytics Tracker)2 findingscdn.parsely.com, p1.parsely.com
cdn.parsely.com, p1.parsely.com
WordPress VIP (analytics) loaded before consent
WordPress VIP (analytics) loaded before consent
Advertising Tracker2 findingsstats.wp.com, pixel.wp.com
stats.wp.com, pixel.wp.com
advertising tracker at stats.wp.com loaded before consent
advertising tracker at pixel.wp.com loaded before consent
Google (Advertising Tracker)2 findingsep1.adtrafficquality.google, ep2.adtrafficquality.google
ep1.adtrafficquality.google, ep2.adtrafficquality.google
Google (advertising) loaded before consent
Google (advertising) loaded before consent
Google Ads (Google) loaded before consent: Google ad syndication and remarketing
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)
Warnings6
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-5SGSF6G)
Unknown third-party request to cse.google.com before consent
Unknown third-party request to www.google.com before consent
Unknown third-party request to clients1.google.com before consent
localStorage key "lastExternalReferrer" written before consent
Info3
Google (cdn) loaded before consent
Parse.ly2 findings_parsely_session, _parsely_visitor
_parsely_session, _parsely_visitor
Parse.ly cookie "_parsely_session" set before consent — JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
Parse.ly cookie "_parsely_visitor" set before consent — JSON document uniquely identifying a browser and counting its sessions
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan harvard.edu →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com