1001Ferramentas
🔗Security

Referrer-Policy Builder

Builds the Referrer-Policy header from a standard value (strict-origin, no-referrer, etc.).



  

Controlling what your browser tells the next site

You want to leak less information to the sites people reach by clicking links on yours, but writing the header itself is where you stall: the spec defines eight values, and the gap between strict-origin and strict-origin-when-cross-origin is not obvious from the names. This page handles the mechanical part. Type the value, get back a line you can paste into Nginx, Cloudflare or an Express middleware.

Under the hood it is a list check and nothing more. Whatever you type is compared against the eight tokens from the spec: no-referrer, no-referrer-when-downgrade, origin, origin-when-cross-origin, same-origin, strict-origin, strict-origin-when-cross-origin and unsafe-url. A match produces the Referrer-Policy line; anything else produces a warning instead. Worth knowing: the field label only lists six of those, but origin-when-cross-origin and unsafe-url are accepted too.

One thing catches people out. The spec allows a comma separated fallback list, and this validator rejects that, because it compares against a single token. If you need a fallback, write the line by hand. Also think about where the value lands, since the scope differs: an HTTP header covers the whole site, the name=referrer meta tag covers that one document, and the referrerpolicy attribute covers a single link or iframe. Everything runs in your browser; the tool builds a string and never probes your site.

Frequently asked questions

Which value should I pick when in doubt?
strict-origin-when-cross-origin, which is already the browser default. It sends the full URL within your own origin and only the origin when the destination is another site.
Why did I get a warning instead of a header?
What you typed is not one of the eight spec values. Check the spelling, and note that a comma separated list also triggers the warning, since the check expects a single token.
Does it check whether my site already sends the header?
No. It only assembles the line. To see what is live, open DevTools, go to the Network tab and read the response headers of the page itself.

Related Tools