WebRTC Leak Test
Check if your browser is exposing your real IP address, even with a VPN on
Running WebRTC leak test…
What Is a WebRTC Leak?
WebRTC (Web Real-Time Communication) lets browsers make video calls, voice calls and file transfers directly between devices. To connect two devices, the browser asks a STUN server for your public IP address and shares the addresses it finds with the website.
A WebRTC leak happens when those addresses include your real IP while you are using a VPN or proxy. Any website can run a few lines of JavaScript to read them, without asking permission, and see where you really are.
This test does the same thing a website would: it collects the addresses WebRTC reveals and compares them with the IP websites normally see. If WebRTC shows a different public address, your real IP is leaking.
How to Fix a WebRTC Leak
Pick your browser, then run the test again
Firefox
Type about:config in the address bar, search for media.peerconnection.enabled and set it to false. This turns WebRTC off completely.
Brave
Open Settings → Privacy and security → WebRTC IP handling policy, and choose “Disable non-proxied UDP”.
Chrome and Edge
There is no built-in switch. Install Google’s official “WebRTC Network Limiter” extension and select “Use my proxy server (if present)”.
Safari
Safari hides local addresses by default. Keep Safari updated, and use a VPN that routes all traffic so the public address WebRTC reveals is the VPN’s.
On Android, the SafePassVpn app routes your whole device through an encrypted WireGuard tunnel, so the public address WebRTC reveals is the VPN server’s, not yours. If you use split tunnelling, keep your browser inside the tunnel. Also check your IP with our IP checker and run the DNS leak test.
WebRTC Leak FAQs
Common questions about WebRTC leaks and how to stay private.
Keep Your Real IP Private with SafePassVpn
SafePassVpn routes your whole device through an encrypted WireGuard tunnel, so your real IP stays hidden from websites and apps.