WebRTC Leak Test
Check whether your browser reveals your real IP address through WebRTC while you use a proxy or VPN. The test compares the IP websites see with the addresses WebRTC shows, and takes a few seconds.
- No sign-up, and nothing from the test is saved
- Checks public and local addresses, IPv4 and IPv6
- Works with any proxy, VPN or anti-detect browser
Your result appears here
The test starts on its own when the page has loaded.
Show what WebRTC returned
- Run the test to see the list
The test uses public STUN servers from Google and Cloudflare. The results stay in your browser.
What your result means
No WebRTC leak
WebRTC shows the same public IP as your connection, or no public IP at all. On a proxy, sites see only the proxyâs address.
WebRTC leak found
WebRTC shows a public IP that websites donât see. With a proxy or VPN on, that address is usually your own. Use one of the fixes below, then test again.
Another IP version
WebRTC shows an IPv6 address next to an IPv4 connection, or the reverse. It can belong to your own network, so treat it as a leak if youâre on a proxy.
WebRTC is off
Your browser has WebRTC turned off or blocked, so it has nothing to leak. Video calls in the browser wonât work while itâs off.
A name ending in .local in place of a local address means your browser is hiding that address from the page. That is normal and isnât a leak.
What is a WebRTC leak?
WebRTC (Web Real-Time Communication) lets a browser make video calls and other direct connections without a plugin. To find a route between two devices, the browser collects its network addresses, called ICE candidates: your deviceâs local address, and the public address that a STUN server on the internet sees.
A web page can start this with a few lines of JavaScript and read the addresses, without asking for camera or microphone access. A proxy set in the browser carries web pages over TCP, but WebRTCâs STUN requests go out over UDP, around the proxy. The STUN server then sees your real public IP, and the page can read it. That is a WebRTC leak. The IETF describes the problem in RFC 8828.
It matters with any HTTP or SOCKS5 proxy. ProxyEmpire proxies carry TCP traffic only, so WebRTCâs UDP traffic canât go through them: the fix is to stop the browser from sending it around the proxy.
How the test works
- Your browser asks Cloudflare, which serves this site, which IP address your connection comes from. That is the IP every website sees.
- It opens a WebRTC connection that asks public STUN servers run by Google and Cloudflare for your address, and lists every address WebRTC finds.
- It compares the two. A public WebRTC address that websites donât see is a leak.
Everything runs in your browser, and nothing from the test is saved. Run it with your proxy on, and again after any change to your browser settings.
How to stop a WebRTC leak
Chrome and Edge
Neither browser has a setting for it, so use an extension that sets the browserâs WebRTC policy. Our free ProxyEmpire Proxy Manager does it while a proxy is connected, and Googleâs WebRTC Network Limiter does it on its own.
Firefox
Type about:config in the address bar, search for media.peerconnection.enabled and set it to false. This turns WebRTC off, so calls in the browser stop working. More in our Firefox proxy guide.
Brave
Go to Settings âș Privacy and security âș WebRTC IP handling policy and choose Disable non-proxied UDP. WebRTC then stops sending traffic around your proxy. See our Brave proxy guide.
Anti-detect browsers
Most take care of it for you. AdsPower, GoLogin, Multilogin, Octo Browser and Incogniton show the proxyâs IP in WebRTC by default. Check that the profileâs WebRTC mode isnât set to Real (Authentic in some browsers), which shows your own address, then run this test inside the profile.
WebRTC leak test FAQ
Is it safe to run a WebRTC leak test?
Yes. The test reads only the addresses your browser already shares with any page that asks. It runs in your browser, uses public STUN servers from Google and Cloudflare, and saves nothing.
Does a VPN stop WebRTC leaks?
A VPN app that covers your whole device usually does, because WebRTCâs UDP traffic goes through the tunnel too. A VPN browser extension works like a proxy and can leak in the same way. Run the test with the VPN on to be sure.
Do anti-detect browsers stop WebRTC leaks?
Usually, yes. AdsPower, GoLogin, Multilogin, Octo Browser and Incogniton show the proxyâs IP in WebRTC by default, so pages see the proxyâs address instead of yours. A profile can still leak if its WebRTC mode is set to Real (Authentic in some browsers). To be sure, open this page inside the profile and run the test.
Does incognito or private mode stop a WebRTC leak?
No. A private window doesnât keep history or cookies after you close it, but WebRTC works the same way inside it.
Can a website see my WebRTC IP without asking me?
Yes. Collecting WebRTC addresses needs no permission prompt. Browsers hide your local address behind a .local name, but the public address the STUN server sees can be read by the page.
Why does the test show an IPv6 address?
Many home and mobile networks give a device both an IPv4 and an IPv6 address. If your proxy uses IPv4 and WebRTC shows your IPv6 address, sites can still see your own network through it.
Will limiting or turning off WebRTC break anything?
Calls that run in the browser, such as Google Meet or the Discord web app, need WebRTC and may not connect while itâs limited or off. Normal browsing isnât affected.
Do ProxyEmpire proxies support WebRTC?
No. ProxyEmpire proxies carry TCP traffic (HTTP, HTTPS and SOCKS5) and donât support UDP, which WebRTC uses. Anti-detect browsers usually handle this for you: most show the proxyâs IP in WebRTC by default. In a regular browser, keep WebRTC limited or off. Either way, run this test with the proxy on to check.
Test your setup with a residential proxy
Try ProxyEmpireâs rotating residential and mobile proxies for $1.97, with 100 MB of residential and 50 MB of mobile data. Connect the proxy, then run this test and our proxy checker.