Referrer-Policy header check

Short answer

Referrer-Policy controls how much of your page address is sent to other sites when visitors click a link or load a third-party resource. The recommended value is strict-origin-when-cross-origin. SiteShield warns when the header is missing and fails unsafe-url, which leaks full URLs including any tokens or IDs in them.

Browser protectionWorth 2 of 100 pointsBy Mumshad JawadUpdated

What is Referrer-Policy?

When a browser leaves your page or loads an image or script from another domain, it sends a Referer header. Referrer-Policy decides what goes in it: nothing (no-referrer), just your domain (origin, strict-origin), or the full URL with path and query string (unsafe-url).

strict-origin-when-cross-origin sends the full URL within your own site (useful for your analytics), only the origin to other sites, and nothing when going from HTTPS to HTTP.

Why it matters

Controls how much of your page URLs (which can contain tokens or customer IDs) leak to other sites when visitors click links.

URLs often contain more than they should: password-reset tokens, order numbers, customer IDs, search terms, email addresses in tracking links. With a leaky policy, every external link, embedded video or analytics tag on those pages receives that information. Sharing less is a straightforward data-minimisation measure.

SiteShield maps this check to:

UAE PDPL: data minimisation

See how these standards fit together in the UAE website security checklist.

How SiteShield grades it

This check, "Referrer-Policy", can cost up to 2 points: a fail loses all 2, a warning loses 1. Every scan starts at 100.

ResultWhenPoints lost
WarningNo Referrer-Policy header. Modern browsers default to strict-origin-when-cross-origin, but the setting should be explicit.1
FailReferrer-Policy is unsafe-url.2
PassAny other explicit policy.0

How to check it yourself

curl -sI https://example.com | grep -i referrer-policy

Or run a free SiteShield scan, which checks this and 16 other settings in one go.

How to fix it

The quick version: Send Referrer-Policy: strict-origin-when-cross-origin

Cloudflare

Rules → Transform Rules → Modify Response Header: set static header Referrer-Policy to strict-origin-when-cross-origin.

Nginx

add_header Referrer-Policy "strict-origin-when-cross-origin" always;

Apache

Header always set Referrer-Policy "strict-origin-when-cross-origin"

WordPress

SiteShield reads the HTTP header, not a <meta name="referrer"> tag, so set it at the server/CDN or with:

add_action('send_headers', function () {
    header('Referrer-Policy: strict-origin-when-cross-origin');
});

FAQ

Will Referrer-Policy break my analytics?

Not with strict-origin-when-cross-origin. Your own analytics still see full internal paths, and other sites still see which domain sent the visitor, just not the exact page.

Is no-referrer safer?

It shares nothing at all, which is the most private option, but some partners and payment providers check the referring domain. strict-origin-when-cross-origin is the usual balance.

Test your Referrer-Policy now

Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.

Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.

Related checks

See all 17 security checks →