Testing…
WebRTC leak test
WebRTC, used for video calls, can bypass the VPN and show your real IP address to sites. Check your browser.
What does this test check?
WebRTC is the technology behind video calls, screen sharing and voice chats that run right in the browser, with nothing to install. To connect two people as directly as possible, the browser collects every address it can be reached at, its address on the local network and its public address on the internet, and hands that list to the page.
The catch is that a page does not need your camera or microphone to get that list, and the browser asks for no permission. Any site can quietly run a WebRTC request in the background and read your public address from it. If that request bypasses the VPN, the site learns your real IP even though everything else it sees comes from the VPN server.
How does it work?
WebRTC lets browsers make direct connections for video calls and file sharing. To do that the browser asks a STUN server how it looks from outside and may share that address with the site.
If the VPN only works as a system proxy, this UDP request can go outside the VPN and reveal your real address. The test compares the addresses WebRTC finds with the address sites see.
What result should you see?
With the VPN off, you will usually see one public address, the same as in the IP card, plus local addresses shown as hidden “.local” names. The status is green, because WebRTC reveals nothing that sites do not already see; this is your baseline.
With Colitu connected there are two healthy results: no public address at all, or only the VPN server's address, exactly matching the IP card. A warning means WebRTC found a public address that differs from the one sites see: your provider's IPv4 address or, on many home and mobile networks, your IPv6 address. If the browser blocks WebRTC completely, nothing can leak, but calls in the browser will not work.
How to fix a bad result
- A different public address on Windows
- Colitu's default system proxy mode covers the browser's web traffic, but WebRTC uses UDP, which can go direct. Turn on TUN mode: all traffic, UDP included, then goes through the tunnel.
- You want to stay in system proxy mode
- Restrict WebRTC in the browser. In Firefox set media.peerconnection.enabled to false in about:config; in Brave choose “Disable non-proxied UDP” as the WebRTC IP handling policy; in Chrome and Edge install Google's official WebRTC Network Limiter extension. With the strictest options, calls in the browser may stop working.
- A VPN or proxy extension is active in the browser
- Extensions only route web pages through their proxy and usually leave WebRTC alone. Turn the extension off and let the Colitu app carry the traffic.
- A leak on Android or iPhone
- There the app tunnels the device's IPv4 traffic, so a different IPv4 address usually means the VPN was not connected at that moment. On iPhone, IPv6 is neither tunnelled nor blocked by default, so your real IPv6 address can show if your network uses IPv6. Check the status in the app and run the test again; on Android, turn on Always-on VPN and Block connections without VPN to stay protected after drops.
Frequently asked questions
Is it normal that my local address shows as “.local”?
Yes. Modern browsers hide your local network address behind a random .local name; that is not a leak.
How do I stop the leak?
On Windows use Colitu in TUN mode; all UDP traffic then goes through the tunnel. If needed, use a browser setting or extension that restricts WebRTC.
Which server does the test use?
Your browser sends a request to Cloudflare's public STUN server (stun.cloudflare.com). The result is evaluated only in your browser.
Read more
With Colitu, sites see our server's address instead of your real IP. 1 GB free every month. Download the app
The tools do not store your results. The DNS test keeps a random ID in memory for ten minutes; the other tools run only in your browser.