WebRTC Leak Test
Check in seconds whether your browser leaks your real IP address through WebRTC, even when you use a proxy or VPN. Free, no sign-up, and the test runs in your browser.
Testing your browser…
IP address websites see
- …
WebRTC in this browser: …
IP addresses exposed through WebRTC
| IP address | Type | Result |
|---|---|---|
| … | ||
The test runs in your browser. Our server only echoes back the IP address it sees and does not store it.
What does this WebRTC leak test check?
WebRTC (Web Real-Time Communication) lets your browser open direct connections for video calls, voice chat and file sharing. To set up those connections, the browser asks STUN servers for its IP addresses, and any website can start that same request with a few lines of JavaScript, without asking your permission.
This WebRTC leak test does exactly that. It collects every IP address your browser reveals through WebRTC and compares them with the IP address websites see when you load a page (checked separately for IPv4 and IPv6). If WebRTC shows a public IP address that websites don't otherwise see, you have a WebRTC leak: your real IP is exposed behind your proxy or VPN.
How to read your results
- No WebRTC leak: every public IP from WebRTC matches the IP websites see. Your proxy or VPN also covers WebRTC traffic.
- WebRTC leak detected: WebRTC reveals a public IP that is different from your visible IP. Usually that is the address your internet provider gave you, which points to your real location.
- Local IP visible: your private network address (such as 192.168.x.x or 10.x.x.x) is exposed. It does not reveal where you are, but it adds detail to your browser fingerprint.
- Hidden (mDNS): Chrome, Edge and Safari replace local IPs with a random
.localname. That is the safe default. - WebRTC disabled or blocked: nothing can leak, but a browser without working WebRTC is unusual, and websites can detect it.
Why a WebRTC leak matters
A proxy or VPN reroutes your web traffic, but WebRTC often uses UDP and can take a different route. That is how your real IP ends up next to your proxy IP. For privacy, it means trackers and advertisers can still see where you browse from. For multi-accounting, it is worse: platforms compare the IP of your connection with the IP that WebRTC reports. A mismatch is a strong signal that something is being hidden, and a leaked IP that shows up in every profile links your accounts to one location.
Read the full explanation in our guide What is WebRTC leakage and how do you prevent it?
How to fix a WebRTC leak
Chrome and Edge
Chrome and Edge have no built-in setting to disable WebRTC. Install Google's official WebRTC Network Limiter extension, or install uBlock Origin and turn on Prevent WebRTC from leaking local IP addresses in its settings.
Firefox
Type about:config in the address bar, search for media.peerconnection.enabled and set it to false. This disables WebRTC completely. To keep WebRTC working, set media.peerconnection.ice.default_address_only to true instead.
Brave
Go to Settings, Privacy and security, WebRTC IP handling policy, and choose Disable non-proxied UDP.
Safari
Safari hides local IP addresses by default. If the test still shows a leak, the cause is usually a VPN or proxy that does not route all traffic.
VPN and proxy
Use a VPN app that tunnels all traffic, including UDP, and has WebRTC leak protection. VPN browser extensions are often proxy-only and do not cover WebRTC. After every change, run this test again.
Disable WebRTC or mask it?
Disabling WebRTC stops the leak, but it also breaks video calls in the browser, and anti-fraud systems notice a browser without WebRTC because almost every real browser has it. For managing multiple accounts, masking works better: WebRTC stays on, but it reports an IP address that matches your proxy.
That is what the Altered WebRTC mode in Incogniton does. Every browser profile gets its own proxy, and WebRTC reports a public IP based on that proxy and a fake local IP. WebRTC keeps working and your real IP stays hidden. See the WebRTC settings documentation for all options.
Frequently asked questions
What is a WebRTC leak test?
A WebRTC leak test checks which IP addresses your browser reveals through WebRTC and compares them with the IP address websites see. If WebRTC exposes a different public IP, your real IP leaks past your proxy or VPN.
Can a VPN leak my IP through WebRTC?
Yes. Many VPNs and especially VPN browser extensions only reroute regular web traffic. WebRTC can use UDP and send STUN requests over your normal connection, which exposes your real IP. Run the test with your VPN switched on to check.
Does incognito or private mode stop WebRTC leaks?
No. Incognito and private windows do not save history or cookies, but WebRTC works the same way as in a normal window, so it can still reveal your IP addresses.
Is it safe to disable WebRTC?
Disabling WebRTC is safe for your privacy, but browser-based video calls (such as Google Meet or Discord in the browser) stop working, and websites can detect that WebRTC is missing. Masking the WebRTC IP keeps WebRTC working without the leak.
What is the difference between a WebRTC leak and a DNS leak?
A DNS leak exposes which DNS server resolves your requests, usually your internet provider's, which hints at your location. A WebRTC leak exposes your IP address itself. Both can bypass a VPN or proxy, so check both.
Do you store my IP address?
No. The test runs in your browser. Our server only tells your browser which IP address it sees, and the IPv4 and IPv6 checks use the public ipify service. Nothing is saved.
