Browser Leak Test
Every site you visit can read the stuff below without asking. This page runs the same checks trackers use and shows you what they'd see.
Everything is computed in your browser. Nothing is stored or sent anywhere by this page (the CSP wouldn't let it). One exception: the WebRTC test contacts a public STUN server (stun.l.google.com) to discover your public IP, which is how the leak is detected.
How to read it
The exposure score is a rough count of how many identifying signals your browser hands over. It is not a measure of how unique you are. A normal browser landing around C or D is expected; Tor Browser and Mullvad Browser score high because they make everyone look the same.
The fingerprint ID is a hash of the stable signals. Reload in a fresh session: if the ID changes, your browser is randomising signals. If it stays the same, trackers can recognise you without cookies.
What to do about it
WebRTC leak
Firefox: set media.peerconnection.ice.default_address_only to true, or
media.peerconnection.enabled to false. Chromium: use an extension that
limits WebRTC IP handling. On a VPN, a mismatch here means your real IP is exposed.
Fingerprints
Tor Browser or Mullvad Browser make everyone look alike. Firefox's
privacy.resistFingerprinting and Brave's shields randomise or flatten
signals, at the cost of some site breakage.
Time zone and language
A VPN in another country with your home time zone and language is a giveaway. Match them, or use a browser that reports UTC and en-US.