Browser uniqueness estimate

Browser Fingerprint Test: Check Session Uniqueness Signals

See whether this browser session looks broad, moderate, or more distinctive based on visible fingerprint signals websites can read.

This check estimates session specificity from the signals displayed on this page. It does not use a population dataset, does not identify a person, and does not prove another site is tracking you.

Uniqueness estimate

Current Result

Not assessed

Run the test to estimate how distinctive this browser session looks from visible signals. Not generated

Specificity not assessed yet

Run the test to see whether the visible browser signals look broad, moderate, or more specific for this session.

Signals collected: Not tested
Session specificity: Run the test first
Storage behavior: No database storage. Generated locally in browser.
Supporting checks: Canvas, WebGL, audio, client hints, privacy signals, and fonts are available as optional evidence below.
Meaning: Session specificity estimate, not a universal identifier.

Verdict first Safe Copy Supporting checks

Exposure estimate and receipt limits

Fingerprint surface labels describe visible browser characteristics in this session. Receipt exports use safe categories and remove raw fingerprint values or hashes before export. Read the methodology.

See what Safe Copy includes before sharing or saving a result.

Want the full picture? Run the Privacy Exposure Report.

Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.

Run report

Quick answer

A browser fingerprint test estimates how distinctive this session looks

The useful signal is not one hash by itself. It is the mix of canvas, WebGL, audio, font, Client Hints, storage, language, timezone, and privacy preference values that may make one browser session easier to recognize across visits.

Run Fingerprint Test Chrome fingerprint guide Canvas signal Safe Copy

What this can reveal

Browser fingerprinting combines many small signals, such as language, timezone, screen size, platform, hardware hints, cookies, storage behavior, and rendering traits. One signal is rarely enough on its own, but the combination can make a browser session easier to recognize.

This page estimates whether the visible combination looks broad, moderate, or more distinctive. A more distinctive result means the session has more browser-visible context that may help recognition when combined with IP address, account state, cookies, or site-side analytics.

What this does not do

It does not store the demonstration fingerprint in a MyIPScan database.
It does not send the fingerprint to a backend API.
It treats canvas, WebGL, audio, client hints, privacy signal, and font checks as supporting evidence, not separate verdicts.
It does not prove that another website will see the same value.

Reduction steps

Practical ways to reduce fingerprinting risk

No setting removes all fingerprinting risk, but these steps can reduce unusual or highly specific browser signals.

Keep your browser updated so privacy features and security fixes are current.
Use built-in anti-fingerprinting features where your browser provides them.
Avoid stacking many rare extensions because extension combinations can become distinctive.
Limit third-party scripts with a reputable content blocker when appropriate.
Use separate browser profiles for activities that should not share the same browser state.

Browser recommendations

Cautious browser guidance

Firefox

Firefox offers advanced privacy settings, including anti-fingerprinting options for users who understand the compatibility tradeoffs.

Brave

Brave includes fingerprinting protections that can reduce some tracking surfaces, though site behavior and settings still matter.

Safari

Safari includes privacy protections and tracking prevention, but browser and device signals can still vary by platform.

Tor Browser

Tor Browser is designed to reduce uniqueness by making users look more similar, but it has usability and performance tradeoffs.

Methodology

How this demo works

The overview script reads standard browser APIs for user agent, language, timezone, screen size, platform, hardware concurrency, optional device memory, Do Not Track, Global Privacy Control, cookies, and local storage availability. It computes a local SHA-256 session fingerprint estimate when browser crypto is available, with a deterministic local fallback otherwise.

The supporting checks are browser-only pages for canvas rendering, WebGL capability values, offline audio rendering, Client Hints, privacy preference signals, and a small font measurement set. The check does not call a backend, does not store the value, and removes the temporary local-storage test key immediately. Read the MyIPScan methodology for broader limitations.

Supporting fingerprint checks Open these only when you need to inspect one signal behind the main uniqueness estimate.

These browser-only checks help explain the main fingerprint surface. They are not separate identity verdicts and should be read together with the overview result.

Canvas signalRender and hash a local canvas signal. WebGL signalInspect GPU and WebGL capability signals. Audio signalRun a silent offline audio rendering check. Client HintsSee browser Client Hints and fallback values. GPC / DNT signalsReview browser privacy preference signals. Font signalRun a small local font measurement check.

Related guides

Learn the signals

Can Someone Track Me by My IP Address?Understand IP tracking and its limits. What Is a VPN?See what VPNs hide and what browser signals remain. How to Hide Your IP AddressCompare practical privacy tools and tradeoffs. Proxy vs VPN vs TorLearn how routing tools differ. Chrome Browser Fingerprint GuideFollow a browser-specific path after changing extensions, profiles, or privacy settings. Guides HomeOpen the MyIPScan blog for newer privacy guides.

Before / after privacy flow

Compare one browser or VPN change at a time

This page is focused on visible fingerprint traits, canvas, WebGL, audio, fonts, Client Hints, and privacy preference signals. Run the browser fingerprint estimate first, then use Public Exposure Report to combine it with IP, DNS, WebRTC, and IPv6. 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.

Check my browser/privacy

What this checks

Visible browser traits such as canvas, WebGL, audio, fonts, Client Hints, language, timezone, storage behavior, user-agent, and privacy preference signals.

Limits

What this cannot check

It cannot identify a person, inspect every tracking method, prove a site can or cannot recognize you, or certify that a browser profile is private.

Read results

How to interpret results

A good lower-risk result has fewer unusual or stable browser-visible traits in this local check. It still does not prove that websites cannot recognize this browser.

Warnings

What a warning means

A warning means the session has traits that may be more distinctive or stable and should be reviewed alongside IP, DNS, WebRTC, and IPv6 signals.

Fix path

What to do next

Compare normal and private profiles, review extensions, privacy settings, browser updates, and whether a hardened browser changes the same signal groups.

Retest

When to retest

Retest after changing browsers, profiles, privacy settings, extensions, language/timezone settings, or fingerprint-resistance features.