WebRTC leak test
A WebRTC leak happens when STUN candidates publish an address your VPN or proxy never sees. This page explains WebRTC leaks and links to the live WebRTC test so you can list those candidates in this browser.
Run this test when you use a VPN, extension-based proxy, or privacy browser and need to know whether WebRTC still publishes an unexpected address. The page lists STUN servers and any candidates the browser gathers.
Candidate addresses are collected in the browser. They are shown on screen and are not uploaded to NetScope unless you later generate a diagnostic report.
How to use this tool
- Connect to the network or VPN you normally use for browsing.
- Run the WebRTC test and expand SDP logs if you need the raw candidates.
- Compare any public addresses with the IP lookup result. An extra public address is the usual leak to investigate.
Open the WebRTC test
Frequently asked questions
Is every WebRTC address a privacy problem?
No. Host candidates on a LAN are common. The issue is an unexpected public or IPv6 address that bypasses the proxy you intended to use.
How do I stop WebRTC from exposing an address?
Use a VPN client that covers UDP, disable WebRTC in the browser, or use an extension that restricts WebRTC. Re-run the WebRTC test after each change instead of trusting a single setting.
Are “WebRTC leak” and “WebRTC leaks” the same check?
Yes. One leak or several extra candidates are the same class of problem: peer connections that left the path you intended. Run the WebRTC test and compare public candidates with the IP lookup.
Related tools