Security & Privacy

Privacy Test

See what information your browser exposes to websites through HTTP headers and browser APIs.

This test runs locally in your browser where possible. WhatAnIP does not generate a browser fingerprint from these results.

Server-visible information

User Agent
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
EXPOSED
Client Hints
Unavailable
LIMITED
Do Not Track
Not provided
LIMITED
Referrer
Not sent
PROTECTED

Browser-exposed information

“Exposed” does not automatically mean unsafe. Many browser features require some information to function. This test shows what a website can observe; it does not assign a security score.

What does a browser privacy test show?

A browser privacy test shows information that websites can observe through ordinary HTTP requests and browser APIs. This can include user-agent data, client hints, referrer information, privacy preferences and selected browser capabilities.

The test does not claim to measure complete anonymity. Its purpose is to make visible some of the signals exposed during normal browsing so you can better understand how browser configuration affects privacy.

How to use the Privacy Test

  1. Open the page using the browser and network configuration you want to test.
  2. Review server-side information exposed through request headers.
  3. Review browser-side privacy signals such as WebRTC support and Global Privacy Control.

Understanding privacy test results

An exposed value means the website can observe that information during normal operation. A limited or protected result means the browser withheld, reduced or changed the signal in a way that may reveal less information.

Privacy behavior differs between browsers, extensions and network setups. A single protected signal does not make a browser anonymous, and an exposed value does not automatically indicate a security problem.

Common uses for a privacy test

  • Compare privacy settings between different browsers.
  • Check the effect of privacy extensions or hardened settings.
  • Review whether referrer or client-hint information is exposed.
  • Understand which browser APIs remain available to websites.
  • Compare browser behavior before and after configuration changes.

Related privacy tools