Referrer-Policy Explainer with Sample Scenarios

Shows exactly what Referer a browser sends under each Referrer-Policy value, for same-origin, cross-origin and downgrade navigations.

Use the tool

Why this tool exists

The Referer header tells the next site where a visitor came from. With a full URL it can leak paths and query strings such as tokens or search terms.

Pick a policy and enter a page URL and the tool shows what is sent in three cases, then compares all eight policy values side by side. It follows the W3C Referrer Policy rules for navigation links. Fragments and credentials are never sent. The default in current browsers is strict-origin-when-cross-origin.

How to use it

  1. Enter the page URL you care about.
  2. Choose a policy.
  3. Read what each case sends.
  4. Set the header or meta tag that fits.

Frequently asked questions

Which policy is a good default?

strict-origin-when-cross-origin is the browser default and a sensible one. Use no-referrer or same-origin for sensitive pages.

Does it cover images and scripts?

It models navigation links. Sub-resource requests follow similar rules with small differences.

Why is a downgrade special?

Sending a full URL from HTTPS to HTTP could expose it on the network.