MyIPScan

Chrome browser self-test pilot

Chrome WebRTC Leak Test: Check Your Current Browser Session

Use this page to review visible WebRTC candidate signals from your current Chrome browser session. Behavior can vary by Chrome version, extensions, VPN, OS, network and settings. This does not certify a browser, device, VPN, setting or connection.

Open the WebRTC Leak Test Read methodology

Current-session checks

What this Chrome self-test checks

This checks browser-visible WebRTC candidate behavior in the current Chrome session. Use the existing MyIPScan tools to review the visible signals instead of drawing conclusions from one page.

WebRTC Leak Test Check browser WebRTC candidate behavior. 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. Browser Fingerprint Test Review browser characteristics that a VPN usually does not change. 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

  • Chrome version, site permissions, extensions and enterprise policies can change WebRTC behavior.
  • VPN client, OS network routing and local network state can change visible candidates.
  • This page does not inspect every Chrome profile, device, extension or connection.

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 WebRTC Leak 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.