Candidates
Every network address the browser collected to set up a WebRTC connection, with type, ownership and verdict. Any script on a website can read these addresses.
After the test, this lists every address your browser exposes, with its type and verdict.
How the test works
No plug-ins — just the browser's built-in WebRTC API, reproducing exactly how websites read your addresses.
The page creates a connection that carries no content and asks Cloudflare's and Google's STUN servers "who do you see me as?"
The browser reports available network addresses one by one: your LAN address, the public address seen by STUN, and relay addresses — waiting up to 10 seconds.
Every public address is compared with your web exit and its location is looked up. Any public address that differs from your web exit is exposure outside your proxy.
This test
- How it ended
- Shown after the test
- Duration
- Shown after the test
- STUN service
- Shown after the test
- Total candidates
- Shown after the test
- Connection failures
- Shown after the test
- Tested at
- Shown after the test
Web exit used for comparison
- Exit IP
- Shown after the test
- Country and city
- Shown after the test
- Network
- Shown after the test
How we judge
Only public, non-relay addresses actually read count as evidence. If it's the same as your web exit, WebRTC uses the same exit; if it differs, that's exposure.
hostYour device's address on the local network, such as 192.168.x.x. Modern browsers usually hide it behind a random name.mDNSThe browser replaces your real LAN address with a randomly generated .local name, so websites can't read your device's IP. This is normal protection.srflxYour public address as seen by a STUN server — the one WebRTC leaks most often expose.relayThe address used when traffic is relayed through a TURN server. It belongs to the relay server and doesn't expose your device's IP.How to prevent WebRTC leaks
If the test finds an unexpected public address, start with these three things. Option names vary by browser and proxy app.
WebRTC mostly uses UDP. Turn on TUN or enhanced mode in your proxy app and make sure your proxy node supports UDP, so this traffic goes through the proxy too.
In Chrome and Edge, install Google's official WebRTC Network Limiter extension; in Firefox, turn off media.peerconnection.enabled in about:config.
Disabling WebRTC may affect video meetings in the browser. After changing settings, come back and test again to confirm that the public address matches your web exit or is no longer exposed.
FAQ
Common questions about WebRTC leaks, how the test works and how to read the results.
What is a WebRTC leak?
WebRTC is the browser's built-in real-time communication technology, used for web video and voice. To connect directly, the browser collects your device's available network addresses, and scripts on the page can read them. If this traffic doesn't go through your proxy, websites can see your real public IP. That's a WebRTC leak.
How do WebRTC leaks relate to AI services?
Your web exit shows the proxy's address, but WebRTC may read a different one. When they don't match, some traffic is bypassing the proxy; some websites' fraud-detection scripts also read the WebRTC address and compare it with the visiting IP.
What does "The browser hid local addresses" mean?
Modern browsers such as Chrome, Safari and Firefox replace your real LAN address with a randomly generated .local name (mDNS), so websites can't read your internal IP. This is normal protection, not a leak.
Why wasn't a public address obtained?
The browser may have WebRTC turned off, the network may block UDP, the STUN servers may be unreachable, or your proxy app may handle this traffic. For privacy, that's usually good news: websites can't read an extra address.
If the public address matches my web exit, am I safe?
A match only means the WebRTC channel didn't expose an extra address. DNS lookups can also bypass your proxy, so we suggest running a DNS leak test too.
What does the test upload or record?
The test runs in your browser. When connecting to STUN servers, Cloudflare and Google see your public address; any public address read is sent to this site to look up its location, and isn't stored. See Privacy.
Address ownership: IP Geolocation by DB-IP (CC BY 4.0) · ASN data from IPtoASN · All data sourcesSTUN services: Cloudflare, Google