Chrome browser self-test
Chrome Browser Fingerprint Test: Check Visible Browser Signals
Use this page to review visible browser fingerprint signals from your current Chrome session. Behavior can vary by Chrome version, extensions, OS, graphics stack, privacy settings and site context. This does not certify a browser, device, VPN, setting or connection.
Run it in Chrome. It reads what this Chrome profile shows to every website, so a second profile or an extension can change the result.
Fingerprint Surface Estimate
Current Result
Not generated
Run the test to see whether visible browser modules create a low, medium, or high recognizable surface.
- Signals collected
- Not tested
- Surface level
- Run the test first
- Storage behavior
- Generated locally. Baseline is optional local browser storage.
- Supporting checks
- Canvas, WebGL, audio, fonts, Client Hints, storage, and privacy signals are shown as modules.
- Meaning
- Recognizable surface, not a universal identifier.
What this means for you
Run the check to see what this means
This block turns the result into plain language: what the finding does and does not show, and what to do next.
Nothing has been checked yet.
Separate modules
Fingerprint Surface Estimate
What Chrome does by default
- Hides your local IP from WebRTC: Protective Yes (mDNS name) source
- Public IP visible to WebRTC: Exposed Yes, via STUN source
- DNS over HTTPS by default: Partial Automatic, falls back to plain DNS source
- Fingerprinting protection: Exposed No; the Incognito script blocking was never launched source
- Blocks third-party cookies: Exposed No; yes in Incognito source
- Sends Global Privacy Control: Exposed No source
Current-session checks
What this Chrome self-test checks
This checks browser-visible fingerprint surfaces in the current Chrome session. Use the existing MyIPScan tools to review the visible signals instead of drawing conclusions from one page.
What this cannot prove
- This applies to the current browser session or current setup only.
- This does not prove anonymity.
- This does not prove every security condition.
- This does not certify a browser, device, VPN, setting or connection.
- Behavior can vary by browser, OS, extension, network and settings.
- This does not inspect every app, device route, extension, OS service, router path or network path.
Scenario-specific caveats
- Fingerprint surfaces can change after browser updates, extension changes or OS graphics changes.
- A local fingerprint demo is not a population uniqueness claim and does not identify a person by itself.
- This page does not inspect every Chrome profile, extension, site request or device configuration.
How to compare before and after
- Run the same check before changing a VPN, browser, OS, extension or network setting.
- Make one change at a time when possible.
- Rerun in the same browser and network context.
- Compare visible signals and use Safe Copy if useful.
Safe Copy limits
Safe Copy exports use safe summary categories and remove raw IP, exact city, full user-agent, raw fingerprint data, raw resolver IPs and WebRTC candidates. It is not a certificate, device audit, browser audit or proof of anonymity.
FAQ
Chrome self-test FAQ
What does this Chrome page check in my current setup?
It routes you into focused MyIPScan tools for visible browser/session signals related to Browser Fingerprint Test, plus supporting privacy diagnostic checks.
What does this page not prove about Chrome?
It does not prove anonymity, every security condition, or every app, browser, device, route, extension, OS service, setting or connection. It is not a certification of Chrome or your setup.
Why can results vary by browser, OS, extension, network or settings?
Browser version, OS version, extensions, VPN clients, router settings, carrier networks and privacy settings can change visible signals.
How should I compare before and after changing a setting or VPN?
Run the same check before the change, make one change, then rerun in the same browser and network context when possible.
What should I do if a signal needs review?
Open the focused DNS, WebRTC, IPv6, VPN or fingerprint tool, read the methodology, then review the relevant browser, OS, VPN or network settings.