WebRTC Leak Test
A VPN is meant to hide your real IP address. But a browser feature called WebRTC can sometimes reveal it anyway. This test checks whether yours does.
Pressing the button makes your browser contact a public STUN server run by Google, which necessarily includes your IP address. Nothing is sent before you press it. See our Privacy Policy.
| Address websites see | – |
|---|---|
| Addresses WebRTC revealed | – |
Technical details
| Type | Address | Protocol |
|---|
How to use this test
- Connect to your VPN, if you use one.
- Run the test above in the browser you normally use.
- If it says Leak detected, your real address is visible. Follow the fixes below.
If you don't use a VPN, the test will simply show your normal address, which is expected. Not sure what your address is? See What is my IP address?
What is a WebRTC leak?
WebRTC lets websites start calls and video chats directly from your browser. To connect you to the other person, it works out your public address by asking a helper server, and that conversation can go around your VPN tunnel. A website can then read your real address, even though everything else looks protected.
How to fix a WebRTC leak
- Use a VPN with WebRTC leak protection, and keep its apps updated.
- Keep your browser updated. Modern browsers hide your local network address behind a random name.
- Firefox: type
about:configin the address bar and setmedia.peerconnection.enabledtofalse. This turns WebRTC off, so video calls in that browser will stop working. - Chrome and Edge: there is no built-in switch, so use a reputable extension that controls WebRTC IP exposure.
What about DNS leaks?
A DNS leak is a different problem. Every time you visit a site, your device asks a DNS server to turn the name into an address. With a VPN, those lookups should go through the VPN. If they go to your internet provider instead, your provider can see which sites you visit, even though the content is encrypted.
We don't offer a DNS leak test yet. A real one needs a DNS server that records which resolver contacts it, and we don't run one. We would rather say so than show you a made-up result. In the meantime you can check it yourself:
- Find your DNS servers. On Windows run
ipconfig /alland look at "DNS Servers". On macOS open System Settings, then Network, then your connection, then DNS. - Connect to your VPN and check again. If the DNS servers are still your internet provider's, your lookups are leaking.
- Fix it by turning on your VPN's "DNS leak protection" setting, or by setting trusted DNS servers inside the VPN app.
Frequently asked questions
What is a WebRTC leak?
WebRTC is a browser feature for calls and video chat. It can reveal your real public IP address to a website even when you are connected to a VPN, because it contacts servers directly instead of going through the VPN tunnel.
What is a DNS leak?
A DNS leak happens when your device sends website name lookups to your internet provider's DNS servers instead of through your VPN. Your provider can then see which sites you visit even though the traffic itself is encrypted.
How do I stop a WebRTC leak?
Use a VPN or browser setting that blocks WebRTC from exposing your IP, keep your browser updated, or install a reputable WebRTC-blocking extension. Firefox also lets you turn WebRTC off by setting media.peerconnection.enabled to false in about:config.
Does this test send my IP address to anyone?
Running the test makes your browser contact a public STUN server run by Google to discover how your connection looks from the internet. That request necessarily includes your IP address. Nothing is sent until you press the button.
Is a WebRTC leak dangerous?
It exposes the real address your internet provider gave you, which defeats the point of a VPN. It does not give anyone access to your device.
Why does the test say I'm fine but I use a VPN?
That means WebRTC only revealed the same address websites see (the VPN's), or nothing at all. Both are good results.