WebRTC Leak Test

Check if your browser exposes your real IP address through WebRTC. Run this with your VPN on: if a different public IP shows up below, your VPN is leaking.

Your IP (web traffic)–
Public IPs seen by WebRTC–
Local addresses–
Technical details (ICE candidates)

    How to test your VPN for leaks

    1. Turn your VPN off and run the test. Note your real public IP.
    2. Turn the VPN on, reload this page and run the test again.
    3. With the VPN on, both "Your IP" and any WebRTC public IPs should be the VPN's address. If your real IP from step 1 appears, WebRTC is leaking.

    Reading the results

    • No public IP from WebRTC: WebRTC is blocked or limited. No leak.
    • Same public IP as your web traffic: no leak; WebRTC uses the same route (your VPN's) as everything else.
    • A different public IP: possible leak, especially if it matches your home internet address.
    • Addresses ending in .local: normal privacy protection in modern browsers.

    Also check your IP, IPv6 and location databases with what is my IP, and look up any address with the IP lookup.

    Last reviewed October 2026.

    Frequently asked questions

    What is a WebRTC leak?

    WebRTC is a browser feature for video calls and peer-to-peer connections. To connect two people, it discovers your network addresses using a STUN server. If a VPN does not handle WebRTC traffic, a website can use it to see your real public IP address even while the VPN is on. That is a WebRTC leak.

    How does this test work?

    Your browser opens a WebRTC connection to a public STUN server, the same way a video call would, and lists the addresses it discovers. The test compares any public addresses with the IP address your normal web traffic uses. If WebRTC reveals a different public IP, your real address may be leaking.

    What do the "local" or ".local" addresses mean?

    Modern browsers hide your private network address behind a random name ending in .local (mDNS). That is normal and not a leak. Older browsers may show a private address like 192.168.1.20, which only identifies you inside your own network.

    How do I fix a WebRTC leak?

    Turn on your VPN's WebRTC or leak protection setting, use the VPN's browser extension, or install an extension that limits WebRTC. In Firefox you can set media.peerconnection.enabled to false in about:config, but that also stops browser video calls.

    Is my data sent anywhere?

    Only the standard STUN request that every video-call website makes. The results are shown in your browser and are not stored.