https://psychologytoday.com
Scanned Apr 15, 2026 · 38.3s
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 6 user data leaks before consent on psychologytoday.com, including Google (Tracker Tracker), Advertising Tracker, GA4.
Security Headers
3/6 presentStrict-Transport-Security
max-age=31536000
Content-Security-Policy
Add a Content-Security-Policy header to prevent XSS and code injection attacks
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 (1)
No default consent call detected — consent mode may not be initialised correctly
Post-Rejection Audit
Reject Button
Found
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
728ms pre-consent
Google Tag Manager(GTM-NW5PKS)
Loaded 728ms after page load — before the consent banner was detected (banner appeared at 7852ms). 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
Consent Record Audit
Issues detectedConsent record stored after interaction
GDPR Art. 7(1)Found: cookieyes-consent (CookieYes)
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 detected
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
Critical4

GA4 (Google) loaded before consent: Sends pageview and event data to Google Analytics
Google (tracker) loaded before consent
advertising tracker at log.cookieyes.com 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)
Warnings3
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-NW5PKS)
Unknown third-party request to directory.cookieyes.com before consent
Info2
CookieYes2 findingscdn-cookieyes.com, cookieyes-consent
cdn-cookieyes.com, cookieyes-consent
CookieYes (CookieYes) loaded before consent: CookieYes cookie consent management
CookieYes cookie "cookieyes-consent" set before consent
Compliant45
Google Ads3 findings209bf26a7806f4f1a82f546dcdcea326.safeframe.googlesyndication.com, pagead2.googlesyndication.com, tpc.googlesyndication.com

209bf26a7806f4f1a82f546dcdcea326.safeframe.googlesyndication.com, pagead2.googlesyndication.com, tpc.googlesyndication.com

Google Ads (Google) loaded correctly after consent

Google Ads (Google) loaded correctly after consent

Google Ads (Google) loaded correctly after consent
Criteo2 findingsdis.criteo.com, cto_bundle

dis.criteo.com, cto_bundle

Criteo (Criteo) loaded correctly after consent

Criteo cookie "cto_bundle" set correctly after consent
Quantcast2 findingscms.quantserve.com, mc

cms.quantserve.com, mc

Quantcast (Quantcast) loaded correctly after consent

Quantcast cookie "mc" set correctly after consent
LiveRamp cookie "euconsent" set correctly after consent
Google Analytics2 findings_ga, _ga_5EMHF6S1M6

_ga, _ga_5EMHF6S1M6

Google Analytics cookie "_ga" set correctly after consent

Google Analytics cookie "_ga_5EMHF6S1M6" set correctly after consent
DoubleClick/Google Marketing2 findings__gads, IDE

__gads, IDE

DoubleClick/Google Marketing cookie "__gads" set correctly after consent

DoubleClick/Google Marketing cookie "IDE" set correctly after consent
Google AdSense2 findings__gpi, __eoi

__gpi, __eoi

Google AdSense cookie "__gpi" set correctly after consent

Google AdSense cookie "__eoi" set correctly after consent
Adform2 findingsUID, uid

UID, uid

Adform cookie "UID" set correctly after consent

Adform cookie "uid" set correctly after consent
ComScore2 findingsXID, pid
XID, pid
ComScore cookie "XID" set correctly after consent
ComScore cookie "pid" set correctly after consent
Google2 findingsDSID, receive-cookie-deprecation
DSID, receive-cookie-deprecation
Google cookie "DSID" set correctly after consent
Google cookie "receive-cookie-deprecation" 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
CreativeCDN cookie "g" set correctly after consent
PayPal cookie "ts" set correctly after consent
Adition cookie "UserID1" set correctly after consent
Yahoo2 findingsA3, IDSYNC
A3, IDSYNC
Yahoo cookie "A3" set correctly after consent
Yahoo cookie "IDSYNC" set correctly after consent

Adobe Advertising cookie "everest_g_v2" set correctly after consent
Snowplow cookie "sp" set correctly after consent
LinkedIn3 findingsbcookie, li_gc, lidc
bcookie, li_gc, lidc
LinkedIn cookie "bcookie" set correctly after consent
LinkedIn cookie "li_gc" set correctly after consent
LinkedIn cookie "lidc" set correctly after consent
Platform161 cookie "tuuid" set correctly after consent
Beeswax2 findingsbitoIsSecure, bito
bitoIsSecure, bito
Beeswax cookie "bitoIsSecure" set correctly after consent
Beeswax cookie "bito" set correctly after consent
Yieldmo cookie "yieldmo_id" set correctly after consent
bidswitch.net cookie "tuuid_lu" set correctly after consent
Media.net2 findingsdata-g, visitor-id
data-g, visitor-id
Media.net cookie "data-g" set correctly after consent
Media.net cookie "visitor-id" set correctly after consent
Sonobi2 findings__uis, HAPLB8G
__uis, HAPLB8G
Sonobi cookie "__uis" set correctly after consent
Sonobi cookie "HAPLB8G" set correctly after consent
csync.loopme.me cookie "viewer_token" set correctly after consent
Teads cookie "tt_viewer" set correctly after consent
Adkernel cookie "ADKUID" set correctly after consent
Federated Media Publishing cookie "ljt_reader" set correctly after consent
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan psychologytoday.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com