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.

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.

Enter a valid value or use one of the quick examples above.
Live analysis is enabled where server-side checks are available. A few tools still fall back to readiness mode when they need external network services or third-party APIs.

What the Referrer-Policy header controls

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.

How to use the checker

  1. Type or paste the full address into the URL field, including https://. You can also click one of the example chips (example.com, github.com or developer.mozilla.org) to fill it in.
  2. Click Check Referrer Policy. Our server requests the page and collects the HTTP response headers.
  3. Read the result panel. The status badge next to your URL shows the policy value in green, or Missing in amber if the header was not sent. Below it you will see three figures: Policy, Header Count (how many response headers the server returned in total) and Server (the value of the Server header, or N/A).
  4. If the result says Missing, check the exact final URL a visitor lands on (see the redirect note below) before concluding the site has no policy.

Worked example: what each policy actually sends

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.

PolicySame-origin link (shop.example.com/help)Cross-origin HTTPS (pay.partner.com)HTTPS to HTTP (old.partner.com)
no-referrernothingnothingnothing
no-referrer-when-downgradefull URLfull URL, including the emailnothing
originhttps://shop.example.com/https://shop.example.com/https://shop.example.com/
origin-when-cross-originfull URLhttps://shop.example.com/https://shop.example.com/
same-originfull URLnothingnothing
strict-originhttps://shop.example.com/https://shop.example.com/nothing
strict-origin-when-cross-originfull URLhttps://shop.example.com/nothing
unsafe-urlfull URLfull URL, including the emailfull 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.

Real results from three sites

When we ran the three example chips through the checker in October 2026, they returned three different situations:

  • https://github.com returned 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.
  • https://developer.mozilla.org showed Missing, but only because that address answers with a redirect to /en-US/. Checking https://developer.mozilla.org/en-US/ directly returned strict-origin-when-cross-origin.
  • https://example.com sent no Referrer-Policy header at all, so visitors' browsers fall back to their built-in default.

How to read the result

  • 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.
  • Missing is not automatically a vulnerability, because modern browsers default to 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.
  • A value the tool shows but you do not recognise (for example a typo such as strict-origin-cross-origin) is ignored by browsers. Only the eight values in the table above are valid.

Limits of this checker

  • It reads HTTP headers only. A policy can also be set in the page HTML with <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.
  • It does not follow redirects. It reports the headers of the first response. If you enter 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.
  • It checks one URL at a time. Servers can send different headers on different paths, so test your checkout, login and account pages separately from the home page.
  • The request comes from our server, not from your browser. Sites behind firewalls, logins or bot protection may return an error page, or different headers from what real visitors receive. Pages on your local network or intranet cannot be reached.
  • It reports the header but does not simulate what a particular browser sends. Browsers may trim referrers further for privacy reasons, but they never send more than the policy allows.

Checker vs. browser DevTools vs. command line

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.

Setting the header on common servers

  • Apache (.htaccess or vhost, with mod_headers): Header always set Referrer-Policy "strict-origin-when-cross-origin"
  • Nginx (server block): add_header Referrer-Policy "strict-origin-when-cross-origin" always;
  • Cloudflare: add a Response Header Transform Rule that sets Referrer-Policy.
  • HTML fallback, when you cannot change headers: <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.

Frequently Asked Questions

Current versions of the major browsers default to strict-origin-when-cross-origin: full URL for same-origin requests, only the origin (for example https://example.com/) for cross-origin HTTPS requests, and no referrer when going from HTTPS to HTTP.

strict-origin-when-cross-origin suits most sites. Use no-referrer or same-origin on pages whose URLs contain tokens, emails or account data. Avoid unsafe-url, which sends full URLs everywhere, including over plain HTTP.

The tool reads HTTP headers from the first response only. A policy set with a meta referrer tag or a referrerpolicy attribute is not detected, and if the URL redirects you see the redirect's headers. Enter the final URL, or check the meta tag in DevTools.

It is a fallback list. Browsers apply the last value in the list that they support, so a header like origin-when-cross-origin, strict-origin-when-cross-origin gives modern browsers the stricter last policy.

No. Referer (spelled with one r, a historic typo in the HTTP spec) is the request header the browser sends to the destination. Referrer-Policy is the response header your site sends to control what goes into Referer.