What the test does
WebRTC is the browser technology behind video calls and peer-to-peer features. To set up a direct connection it collects ICE candidates, which are possible network addresses for your device, and it asks a STUN server for the public address as the internet sees it. This test starts that process in your browser using a Google STUN server and lists the candidates it receives. It then compares the public address with the IP used by your ordinary HTTP connection.
How to read the result
- Same IP in both rows: no leak. WebRTC and normal traffic leave from the same place.
- Different public IPs: a leak. A site that runs the same script can see your real address even though pages load through the proxy.
- Only a .local name or nothing: modern browsers often hide local addresses behind mDNS names, and some block candidates when no permission is granted. That is a good outcome.
- IPv6 address shown: compare it with the IPv6 you expect; some proxies carry only IPv4.
Why it matters for proxy users
A proxy that covers HTTP and HTTPS does not necessarily cover the UDP traffic WebRTC uses to reach a STUN server. If a page can read the address WebRTC discovers, the country you set with a token such as -country-us is undone by a single script. This matters most when you use a proxy to see the web as a visitor from another market, for example in ad verification or localized QA. A mismatch also makes your session inconsistent: the IP says one country, WebRTC says another.
How to fix a leak
- Use a browser profile or antidetect browser that applies the proxy to WebRTC as well, or set its WebRTC mode to replace or hide the real address.
- Disable or restrict WebRTC in the browser's settings or with a trusted extension when you do not need calls.
- Route traffic at the system or network level, for example with the Nefo Windows app, so no application bypasses the proxy.
- For automation, launch your headless browser with its WebRTC policy set to avoid exposing public addresses, or disable the feature.
- Retest after each change and check the connection with the IP lookup.
Need a different IP or location?
If the result shows an address or country you do not want, route traffic through residential proxies in 227 countries, from $4.50 for 5 GB that never expires, or check pricing.
Frequently asked questions
A leak is when WebRTC exposes your real public IP while a proxy or VPN hides it for normal web requests. Any page running a small script can read the address WebRTC discovers.
It gathers ICE candidates through a Google STUN server in your browser and compares the public IP they reveal with the IP your HTTP connection presents.
Browsers often hide local addresses behind mDNS .local names. Seeing no public address that differs from your connection IP is a good result.
Apply the proxy to WebRTC in your browser profile, restrict or disable WebRTC, or route traffic at the system level. Then run the test again.
No, it is a legitimate technology for calls and sharing. The concern is only that it can disclose your real IP independently of a proxy.