WebRTC test
A WebRTC test asks the browser to gather ICE candidates. Those candidates can include a LAN address and a public address even when ordinary HTTPS is going through a VPN or extension proxy.
Use this WebRTC test after connecting a VPN, enabling a proxy extension, or changing WebRTC policy in the browser. Compare any public candidate with the IP lookup result.
Candidates are collected in this browser and shown on screen. They are not uploaded to NetScope unless you generate a report.
How to use this tool
- Connect the VPN or proxy you normally browse with.
- Start the WebRTC test and wait for STUN results.
- Treat an extra public or unexpected IPv6 address as the leak to investigate.
Run the WebRTC test
Frequently asked questions
Is a WebRTC test the same as a WebRTC leak check?
Yes for this tool. The WebRTC test lists candidates; a leak is when a public address appears that your VPN or proxy was supposed to hide. Read the WebRTC leak guide for the why.
Why do I see a 192.168.x.x address?
That is a typical LAN host candidate. It is common and not the same problem as a second public IP that bypasses the tunnel.
Related tools