Browser security
Compatibility & evidence
Browser privacy

Referrer Policy

Limits referrer information sent with navigations and subresource requests.

Support in current browsers

Checked against the current browser versions recorded in MDN browser data 8.1.5.

BrowserMinimumOutcomeReason
Chrome155WorksEvery required mapped BCD feature is available without a recorded qualification.
Edge154WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari27WorksEvery required mapped BCD feature is available without a recorded qualification.
Chrome for Android155WorksEvery required mapped BCD feature is available without a recorded qualification.
Firefox for Android157WorksEvery required mapped BCD feature is available without a recorded qualification.
Safari on iOS27WorksEvery required mapped BCD feature is available without a recorded qualification.
Android WebView155WorksEvery required mapped BCD feature is available without a recorded qualification.
Samsung Internet30.0WorksEvery required mapped BCD feature is available without a recorded qualification.
The release trace

How support changed

Each segment groups recorded releases with the same result. Gaps between recorded versions are not filled in. This is support at each release, rather than the planner’s check of every release above a minimum.

Chrome

http.headers.Referrer-Policy
  1. 1 – 5555 recorded releases
    Not supported
  2. 56 – 15599 recorded releases
    Works

Edge

http.headers.Referrer-Policy
  1. 12 – 187 recorded releases
    Not supported
  2. 79 – 15475 recorded releases
    Works

Firefox

http.headers.Referrer-Policy
  1. 1 – 4952 recorded releases
    Not supported
  2. 50 – 157108 recorded releases
    Works

Safari

http.headers.Referrer-Policy
  1. 1 – 1118 recorded releases
    Not supported
  2. 11.1 – 2743 recorded releases
    Works

Chrome for Android

http.headers.Referrer-Policy
  1. 18 – 5532 recorded releases
    Not supported
  2. 56 – 15599 recorded releases
    Works

Firefox for Android

http.headers.Referrer-Policy
  1. 4 – 4943 recorded releases
    Not supported
  2. 50 – 15798 recorded releases
    Works

Safari on iOS

http.headers.Referrer-Policy
  1. 1 – 11.316 recorded releases
    Not supported
  2. 12 – 2742 recorded releases
    Works

Android WebView

http.headers.Referrer-Policy
  1. 1 – 5527 recorded releases
    Not supported
  2. 56 – 15599 recorded releases
    Works

Samsung Internet

http.headers.Referrer-Policy
  1. 1.0 – 7.016 recorded releases
    Not supported
  2. 7.2 – 30.036 recorded releases
    Works

BCD 8.1.5 · catalogue 2.3.0. Source corrections can change this trace without a new browser release.

What this feature can and cannot do

Helps protect against

  • URL data disclosure
  • Cross-origin navigation metadata leakage

Does not guarantee

  • Data placed in destination URLs
  • Other browser telemetry
  • Server logs for the requested resource

What you need before using it

  • A policy compatible with application routing and integrations

Fallback to keep in place

Keep sensitive values out of URLs and avoid relying on referrer data for authorisation.