How to use Referrer-Policy Disclosure Simulator
- Enter the source-page and main destination HTTP(S) URLs. The model strips source credentials and fragments before calculating a referrer.
- Choose a Referrer-Policy. The default choice models strict-origin-when-cross-origin; it is not a policy read from a live page.
- Optionally add up to 50 extra destinations and keep Compare all eight policies enabled to contrast the main destination across policies.
- Run Model referrer. Compare no referrer, origin only or source path/query disclosure, then download the scenario report if needed. No URL is visited.
Example: Referrer-Policy Disclosure Simulator
Compare a cross-origin HTTPS destination, a same-origin page and an HTTP downgrade.
Options
- Referrer-Policy
- The eight policy values from the W3C Referrer Policy specification, plus the default a page gets when it sets none.
- Source page URL
- An absolute http or https URL, including the path and query you care about. Credentials and the fragment are removed before the value is worked out.
- Destination URL
- The page being linked to, navigated to or loaded. Only the scheme, host and port decide same-origin and downgrade.
- Extra destinations, one per line
- Optional, up to 50 URLs. Each one is added to the table with the same source and policy.
- Compare all eight policies for the main destination
- Adds a table and export that show the referrer each of the eight policies would send to the main destination. It does not change the selected policy above.
Supported inputs and limits
- Offline HTTP(S) URL scenarios for the eight supported policies only.
- Up to 50 extra destinations use the selected policy; the all-policy comparison covers the main destination.
- Source credentials and fragments are stripped.
- Real browser privacy overrides, document conditions and actual request headers are not tested.
- No page is loaded, network traced or certificate checked.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
The displayed value explains a disclosure choice
Different policies can send no referrer, an origin or a fuller source URL. Credentials and fragments are removed, while a policy that sends a fuller URL can disclose its path and query. The result models the entered URLs and policy; it does not inspect real request headers or prove a browser applied that policy.
Questions about Referrer-Policy Disclosure Simulator
Are credentials or fragments sent?
They are stripped from the modeled referrer. Paths and queries depend on the selected policy.
Does this show an actual request?
No. It calculates the declared scenario without loading the URLs.
What does origin contain?
The scheme, host and effective port, without the path, query or fragment.