Enter a URL to see the Referrer-Policy header its server sends, or whether it is missing, so you know how much of your page address browsers share with other sites.
Referrer Policy Checker
Enter a URL to see the Referrer-Policy header its server sends, or whether it is missing, so you know how much of your page address browsers share with other sites.
Every time a visitor clicks a link on your site, or their browser loads an image, script or font from another server, the browser may send a Referer header telling the destination which page the request came from. If your URLs contain order numbers, search terms, password-reset tokens or email addresses in the query string, that header can hand those details to analytics vendors, ad networks, payment providers and any other third party your page links to.
The Referrer-Policy response header tells the browser how much of that address to share. It is defined in the W3C Referrer Policy specification, and MDN's Referrer-Policy reference documents browser support. This checker fetches a URL from our server, reads the response headers it gets back, and reports whether a Referrer-Policy header is present and what it says.
https://. You can also click one of the example chips (example.com, github.com or developer.mozilla.org) to fill it in.Server header, or N/A).Suppose a customer is on this order page and the page links out to two partners and an old HTTP site:
https://shop.example.com/orders/12345?email=jane%40example.com
The table shows the Referer value the browser sends under each of the eight valid policies. Fragments (anything after #) are never sent under any policy.
| Policy | Same-origin link (shop.example.com/help) | Cross-origin HTTPS (pay.partner.com) | HTTPS to HTTP (old.partner.com) |
|---|---|---|---|
no-referrer | nothing | nothing | nothing |
no-referrer-when-downgrade | full URL | full URL, including the email | nothing |
origin | https://shop.example.com/ | https://shop.example.com/ | https://shop.example.com/ |
origin-when-cross-origin | full URL | https://shop.example.com/ | https://shop.example.com/ |
same-origin | full URL | nothing | nothing |
strict-origin | https://shop.example.com/ | https://shop.example.com/ | nothing |
strict-origin-when-cross-origin | full URL | https://shop.example.com/ | nothing |
unsafe-url | full URL | full URL, including the email | full URL, sent in clear text |
"Full URL" here means https://shop.example.com/orders/12345?email=jane%40example.com. Only two policies, no-referrer-when-downgrade and unsafe-url, leak the customer's email address to the payment partner. Those are the values to look out for in the checker's result.
When we ran the three example chips through the checker in October 2026, they returned three different situations:
origin-when-cross-origin, strict-origin-when-cross-origin. This is a fallback list: the browser uses the last value in the list that it understands, so modern browsers apply strict-origin-when-cross-origin and older ones fall back to the first value./en-US/. Checking https://developer.mozilla.org/en-US/ directly returned strict-origin-when-cross-origin.strict-origin-when-cross-origin is a sensible choice for most sites. Your own analytics still see full paths for internal navigation, other sites only learn your domain, and nothing goes to HTTP pages. It is also the default that current versions of the major browsers use when a page sets no policy, according to MDN.no-referrer, same-origin and strict-origin are stricter. Use them on pages that handle accounts, health, finance or tokens in URLs. The trade-off is that partners and affiliate networks see less or no referral data from you.unsafe-url or no-referrer-when-downgrade deserve a second look. The first sends full URLs everywhere, even over unencrypted HTTP. The second was the old browser default and still sends full URLs to every HTTPS site.strict-origin-when-cross-origin. Setting the header explicitly is still recommended, since it makes your intent clear, covers older browsers and is flagged by most security header audits.strict-origin-cross-origin) is ignored by browsers. Only the eight values in the table above are valid.<meta name="referrer" content="...">, or per element with the referrerpolicy attribute on links, images and scripts, or rel="noreferrer" on a link. The tool does not parse the page body, so a site that relies on a meta tag will show as Missing here.http://, a bare domain or an address without a trailing language path, you may be looking at a redirect response. Enter the final URL a visitor actually ends up on.You can see the same header yourself: open DevTools in Chrome or Firefox, go to the Network tab, reload the page, click the document request and look under Response Headers. On the command line, curl -sI https://yoursite.com/ | grep -i referrer-policy does the same job. DevTools is the best option for pages behind a login, because it uses your session. curl is handy for scripts. This checker is quicker when you are on a phone, auditing a site you do not control, or sending a result to a colleague who does not use the command line.
For a wider audit, run the same URL through the Security Headers Scanner, which checks Referrer-Policy alongside HSTS, CSP, X-Frame-Options, X-Content-Type-Options and Permissions-Policy. The HTTP Headers Checker lists every response header. If you are tightening HTTPS at the same time, the HSTS Header Checker shows your Strict-Transport-Security settings.
Header always set Referrer-Policy "strict-origin-when-cross-origin"add_header Referrer-Policy "strict-origin-when-cross-origin" always;Referrer-Policy.<meta name="referrer" content="strict-origin-when-cross-origin"> in the page head. This checker will not detect it, so confirm it in DevTools.After deploying, clear any CDN cache and run the check again on the exact URL to confirm that the new value is being served.