🕵️ WebRTC Leak Test
Find out if WebRTC exposes your real IP address behind a VPN or proxy. Runs locally in your browser.
Click the button and wait a few seconds while the browser gathers ICE candidates.
📋 ICE candidates
🛠️ How to fix a WebRTC leak
- Chrome / Edge: Install the WebRTC Network Limiter extension or set the WebRTC IP handling policy to Disable non-proxied UDP.
- Firefox: Open about:config and set media.peerconnection.enabled to false. Note that video calls will stop working.
- Brave: Settings, Shields, WebRTC IP Handling Policy: select Disable Non-Proxied UDP.
🔐 The test runs entirely in your browser. The only external request is a public IP check (ipify.org). No data is sent to 0Appz.
How to use this tool
Overview
WebRTC Leak Test checks whether WebRTC, the browser technology behind video calls, exposes your real IP address. The page gathers ICE candidates locally through public STUN servers, shows exactly which host, STUN and relay addresses your browser reveals, and compares them with the public IP that websites already see. If a different address appears behind a VPN or proxy, you have a leak and the page shows step-by-step fixes for Chrome, Edge, Firefox and Brave. Nothing is uploaded: the test runs entirely in your browser and only the visible-IP check is fetched from a public service.What a WebRTC leak actually is
WebRTC lets browsers open direct peer-to-peer connections for video, voice and file transfer. To find a route between two devices it gathers ICE candidates: local host addresses, server-reflexive addresses discovered through STUN, and relay addresses allocated by TURN. If a VPN or proxy only reroutes normal web traffic, those ICE candidates can still reveal your real public IP to the other peer. That is the leak. Websites can read the candidate list with a few lines of JavaScript, which is why testing matters before you rely on a VPN for anonymity.
How the test works
The page creates a peer connection, gathers ICE candidates locally and groups them by type so you can see exactly what your browser exposes. It then compares the addresses with the public IP that ordinary web requests reveal. When both match, WebRTC is not leaking anything beyond your visible IP. When a different address appears, typically your ISP address behind a VPN, the result is flagged as a leak with concrete fixes.
Technical specifications
| Property | WebRTC leak test behavior |
|---|---|
| Checks performed | Host, STUN (srflx), TURN relay and visible public IP |
| Technology | RTCPeerConnection + public STUN servers |
| Data sent | Only the visible-IP lookup; candidates stay in your browser |
| Result | Address list, leak verdict and browser-specific fixes |
| Supported browsers | Chrome, Edge, Firefox, Brave, Safari and mobile browsers |
| Cost | Free, no account, no history stored |
Privacy: a diagnostic that does not profile you
Running a privacy test should not create new privacy problems. Candidates are processed in page memory and discarded when you leave; no results, addresses or fingerprints are stored server-side. The only outbound request is the public-IP check needed for the comparison, and the test itself works without an account or tracking script.
If the test reports a leak
- Enable your VPN browser extension in incognito and normal windows alike, profiles differ.
- In Firefox, set media.peerconnection.enabled to false to disable WebRTC entirely.
- In Chrome or Edge, install an extension that forces WebRTC through the proxy.
- Use a VPN with WebRTC protection or a TURN-only setup, then retest until addresses match.
Want to check the rest of your connection? Browse the privacy and security tools for DNS leak and fingerprint tests.
When to run a WebRTC leak test
Run the test whenever your real IP must stay hidden. Good moments: right after installing or updating a VPN, because updates can reset proxy settings; before joining a call you would rather not attribute to your home connection; after switching networks on a laptop, since a new Wi-Fi profile may bypass the VPN split tunnel; and whenever you travel, because hotel and airport networks often block VPN protocols and the browser may fall back to direct connections. Repeat the test in the same browser profile you actually use, extensions and settings differ between normal and private windows, and a clean result in one says nothing about the other.
Reading the candidate list
Host candidates are local addresses such as 192.168.x.x and are harmless; they reveal your network topology but not your public identity. Server-reflexive candidates are the ones that matter: they show the public IP a STUN server observed, which is what another peer would see. Relay candidates come from TURN servers and only appear when a direct path is unavailable. A leak usually looks like a server-reflexive candidate with your ISP address while the visible-IP check shows the VPN address, matching public addresses in both places is the pass condition.
Frequently asked questions
What is a WebRTC leak? +
WebRTC is the browser technology behind video calls. To connect peers it discovers your IP addresses through STUN servers, and that discovery can bypass a VPN or proxy. A leak means a website can learn your real IP even while your VPN is on.
How does this WebRTC Leak Test work? +
The page creates a local RTCPeerConnection, gathers ICE candidates through public STUN servers and compares the public addresses with the IP websites already see. Everything runs in your browser.
The test shows my normal IP, is that a leak? +
If you are not using a VPN, seeing your own IP is expected. It becomes a leak only when the WebRTC address differs from the tunnel address your VPN provides.
Why do I only see mDNS addresses? +
Modern Chromium browsers hide local IPs behind random .local names (mDNS). That is good for privacy and means your LAN address is not exposed.
How do I stop a WebRTC leak? +
Use a VPN with built-in WebRTC protection, install the WebRTC Network Limiter extension in Chrome and Edge, set media.peerconnection.enabled to false in Firefox, or select Disable Non-Proxied UDP in Brave.