Cookie consent banner
Whether the pages carry a consent layer before the tracking scripts run. For an EU audience that is what the GDPR and the ePrivacy Directive ask for.
Under the GDPR and the ePrivacy Directive, a site may not store or read non-essential identifiers on a visitor's device — analytics, advertising, session recording — until the visitor has agreed. A consent layer is the banner or dialog that asks, together with the mechanism that keeps the tags switched off until the answer is yes.
What the row shows
SiteScan looks for the known consent platforms (Cookiebot, OneTrust, Usercentrics, Iubenda, CookieYes, Didomi, Complianz, Borlabs, Klaro and others) and for a hand-made banner recognisable by ids and classes such as cookie-banner or consent-banner. A layer found on any crawled page counts for the whole site.
- Green — a layer is there, named by vendor or shown as a custom banner.
- Red — trackers load and no layer was found, on a site addressed to Europe: an EU or UK domain, or a generic one whose pages are in a European language.
- Amber — the same gap on a site outside that audience, reported as a low-severity note.
- Grey — no trackers, so nothing needs consent.
A banner alone is not enough: the tags must wait for it. Load them with type="text/plain" and a category attribute your platform understands, or through its tag-manager integration. More in cookie consent.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Privacy & consent”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data