Referrer-Policy header
How much of the current address is handed to other sites when a visitor clicks a link. The loose values send the full URL, query string and all.
When a visitor follows a link or the page loads a third-party resource, the browser sends the Referer header with the address of the page they came from. That address can contain a lot: password-reset tokens, search queries, order numbers, internal paths. Referrer-Policy decides how much of it leaves your site.
How SiteScan grades it
- “Strong”: a value that does not send the full URL to other sites —
strict-origin-when-cross-origin,strict-origin,same-origin,originorno-referrer; - “Weak”:
unsafe-url,no-referrer-when-downgradeororigin-when-cross-origin— these still pass the full address, path and query string to other sites; - “Missing”: no header. Modern browsers then use
strict-origin-when-cross-originby default, but older ones and some embedded browsers do not.
Recommended value
Referrer-Policy: strict-origin-when-cross-origin — your own pages get the full address for analytics, other sites see only the domain, and nothing is sent from HTTPS to HTTP. If even the domain is sensitive, use no-referrer. Partner programmes still see where traffic came from, just not the exact page. See the other security headers in the group.
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 “Security headers”
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