Checking for VPN or WebRTC Leaks...
Please wait, running tests...
What the Results Mean
- ✅ No Leak Detected: WebRTC returned a public address on the same network that is serving this page, so it is not exposing anything your VPN or ISP already hides.
- ✅ No Leak — WebRTC Blocked: WebRTC returned no public address at all. Nothing can leak this way.
- ⚠️ Real IP Leak Detected: WebRTC exposed a public IP belonging to a different network to the one serving this page — typically your real ISP address escaping a VPN that only tunnels IPv4. The leaked IP and its provider are shown above.
- 🚫 WebRTC Disabled: This browser has WebRTC turned off entirely.
A .local address is not a leak. Chrome, Edge and Safari deliberately replace your local IP with a random *.local name so websites cannot read it — seeing one means the protection is working. Private addresses such as 192.168.x.x are not a leak either; they are not routable on the internet.
How to fix a real WebRTC leak:
- 🔧 Chrome/Edge: Install the WebRTC Leak Prevent extension
- 🔧 Firefox: Set
media.peerconnection.enabledtofalsein about:config - 🛡️ Best solution: Use a VPN with built-in WebRTC leak protection