MyIPScan

Chrome browser self-test pilot

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.

Open the Browser Fingerprint Test Read methodology

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.

Browser Fingerprint Test Review browser characteristics that a VPN usually does not change. Canvas Fingerprint Test Check local canvas rendering behavior. WebGL Fingerprint Test Review WebGL renderer and capability signals. Client Hints Checker Check browser User-Agent Client Hints signals. VPN Leak Test Review IP, DNS, WebRTC, IPv6 and browser/session signals together. DNS Leak Test Review limited resolver-signal behavior for this browser session. WebRTC Leak Test Check browser WebRTC candidate behavior. IPv6 Leak Test Review whether IPv6 appears in visible signals. Methodology Review the limits before interpreting results.

What this cannot prove

  • This applies to the current browser session or current setup only.
  • This does not prove anonymity.
  • This does not prove complete security.
  • 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

  1. Run the same check before changing a VPN, browser, OS, extension or network setting.
  2. Make one change at a time when possible.
  3. Rerun in the same browser and network context.
  4. Compare visible signals and save a Privacy Receipt if useful.

Privacy Receipt limits

Privacy Receipt 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, complete security, 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.