MyIPScan
Browser privacy review

Check My Browser Privacy Signals

Browser privacy is not one switch. Review visible fingerprint traits, WebRTC candidates, IPv6 behavior, User-Agent context, and public route signals with clear limits.

Run Browser Fingerprint Test Run full report
Visible signals Safe receipt Not a certification

Where to start

Use the Browser Fingerprint Test for uniqueness-adjacent traits, WebRTC Leak Test for candidate behavior, IPv6 Leak Test for IPv6 visibility, and User-Agent Checker for browser identity clues.

How to improve signal quality

Change one setting at a time, retest in the same browser profile, and avoid interpreting a single result as proof of privacy or tracking behavior.

Safe sharing

Use Safe Copy or the Safe Privacy Receipt when you need to share a diagnostic summary without raw IP addresses, full User-Agent strings, raw resolver IPs, raw candidate strings, or fingerprint hashes.

Before / after privacy flow

Compare one browser or VPN change at a time

This page is focused on visible browser/session privacy signals. Start with the linked focused tool, then use Public Exposure Report for the combined route map. Results are visible browser/session signals, not a certification.

1. BaselineRun the focused check before changing VPN, DNS, browser, profile, or network settings.
2. Change one thingConnect or switch VPN, change Secure DNS, adjust WebRTC/fingerprint settings, or move networks.
3. RetestRun the same check again in the same browser/session when possible.
4. CompareReview changed and unchanged IP route, DNS, WebRTC, IPv6, fingerprint, and User-Agent signals.
5. Safe receiptUse Safe Copy or the Safe Privacy Receipt instead of sharing raw identifiers.

Status language

Use conservative result labels

These labels keep the result understandable without implying a VPN, browser, device, or account is safe.

Visible

A browser/session signal was visible and should be compared with what you expected.

Expected

The observed signal appears consistent with the stated route or browser behavior.

Review

The signal may need closer review before relying on this setup for the current session.

Limited

The check ran, but this page cannot cover every app, device route, server, or future connection.

Not detected

The tested signal was not observed in this browser/session.

Not checked

The signal has not run yet or the browser did not provide enough data.

Fix checklist

Where to review settings after a signal needs attention

Settings names change. Treat this as a route to verify, then rerun the focused check and the Public Exposure Report.

ChromeReview Secure DNS, WebRTC policy/extensions, profile state, and site permissions.
EdgeReview Chromium privacy settings, managed policies, Secure DNS, and VPN split tunneling.
FirefoxReview Enhanced Tracking Protection, DNS over HTTPS, and advanced WebRTC preferences when appropriate.
BraveReview Shields, fingerprinting protections, and WebRTC IP handling policy.
SafariReview website permissions, iCloud Private Relay context, and operating-system privacy settings.
iOSRetest after VPN profile, relay, mobile data, or Wi-Fi changes. Browser controls may be limited.
AndroidReview per-app VPN, Private DNS, browser permissions, and Wi-Fi versus mobile data behavior.
WindowsReview VPN adapter DNS, split tunneling, IPv6, browser Secure DNS, and firewall/proxy rules.
macOSReview VPN profile order, DNS settings, iCloud Private Relay context, and browser-specific privacy controls.
Public Exposure ReportDefault next step for a combined route map and Safe Privacy Receipt. Is My VPN Working?Before/after VPN workflow for visible browser/session signals. What Websites Can See About MePlain-language map of signals websites may read from this browser/session. Check My Browser PrivacyFocused path for fingerprint, WebRTC, IPv6, User-Agent, and browser settings.
Safe Receipt limits

Safe Copy removes raw IP addresses, exact city, full User-Agent, raw DNS resolver IPs, raw WebRTC candidates, and raw fingerprint values where relevant. It is a reduced summary, not a certification.

Review the Safe Privacy Receipt model before sharing diagnostics.

FAQ

Questions this page answers

What does this page check?

It helps review visible browser/session signals and points to focused MyIPScan tools for the current browser context.

What does this not prove?

It does not certify anonymity, VPN safety, every app route, every device route, every network path, or complete security.