Referrer policy checker

What the referrer policy checker does

This tool requests a website and checks whether the response includes a Referrer-Policy header. It displays the policy value when present, showing how the site controls the referrer information sent with outgoing requests.

The Referrer-Policy header determines how much information about the current page is included when a user follows a link or loads a resource from another site. Browsers send a Referer header by default, which can reveal the full URL the user came from.

Why referrer policy matters

Referrer data can leak sensitive information. A URL might contain a search term, a user identifier, or an internal path that should not be shared with third parties. Limiting referrer information reduces that exposure while still allowing sites to receive useful context when appropriate.

Referrer policy also affects analytics and affiliate tracking. Some sites depend on referrer data to attribute traffic, so the policy should balance privacy with legitimate measurement needs. The right setting depends on what the site does and what it links to.

How to interpret the result

If a policy is present, review its value. Common policies include no-referrer, which sends nothing; same-origin, which sends full referrer only within the same origin; strict-origin, which sends only the origin and only over HTTPS; and strict-origin-when-cross-origin, a common default that sends the full URL for same-origin requests and only the origin for cross-origin requests over HTTPS.

If no header is reported, the browser uses its default policy. Modern browsers often default to a reasonably privacy-conscious behavior, but relying on defaults means the site has less explicit control. Setting a policy makes the intent clear and consistent across browsers.

Common referrer policy issues

• No explicit policy. Behavior depends on browser defaults.
• Overly permissive policy. Full URLs sent to third parties unnecessarily.
• Breaking attribution. A strict policy that removes referrer data needed by partners.
• Inconsistent policies. Different values across pages or resources.

Practical workflow

Check the header on key pages and on pages that link to third parties. Choose a policy that matches your privacy and measurement needs, and apply it consistently. After changes, verify that analytics and partner integrations still receive the data they require, and re-check the header to confirm it is sent.

Limitations

The checker reports the header on the response it receives. It does not trace how referrer data flows across third-party requests, and individual links can override the policy with their own referrerpolicy attribute.