WebRTC leak test
Runs in your browser · freeCheck whether WebRTC exposes your real public IP or your local network address, even behind a proxy or VPN.
| WebRTC support | … |
| Public IP seen by WebRTC | … |
| Device and local addresses | … |
| What to do | … |
The test asks a public STUN server for your address, as any video call does. Nothing is sent to NexLogin.
Why WebRTC leaks your IP
To set up a direct call, WebRTC collects every address your device can be reached on, called ICE candidates, and hands them to the page. Many proxies only carry ordinary web requests, so the request WebRTC sends to a STUN server can leave through your real connection and reveal your real public IP.
Sites use this to check whether the IP you browse from matches the IP your browser can reach. A mismatch suggests a proxy, and the real IP can link separate accounts to one person.
How to stop it
- Route all browser traffic, including UDP, through the proxy, or disable non-proxied UDP.
- Make sure the public IP WebRTC reports is the proxy's IP, not your own.
- Keep local addresses hidden behind mDNS names.
For a full picture of what your browser reveals, run the browser fingerprint test.
WebRTC leak FAQ
What is a WebRTC leak?
WebRTC lets browsers make video and voice calls directly. To connect, the browser gathers your IP addresses and can share them with any page that asks, including your local network address and, if a proxy or VPN does not cover WebRTC traffic, your real public IP.
How do I read the result?
Compare the public IP shown here with the IP your proxy or VPN should give you. If they differ, WebRTC is going around your proxy. A private address such as 192.168.x.x or 10.x.x.x means your local network address is exposed.
What does 'Hidden (mDNS)' mean?
Modern Chrome replaces your local address with a random .local name for pages without camera or microphone permission. That is good: your local IP is not exposed.
How do I fix a WebRTC leak?
Use a browser that routes WebRTC through the same proxy as the rest of its traffic, or turns WebRTC off when you do not need it. NexLogin does this per browser profile.
WebRTC that follows your proxy
Each NexLogin profile routes WebRTC through its own proxy, so your real IP stays out of every session.