Live tool · WebRTC & privacy tells

WebRTC IP Leak Test

Is your VPN leaking your real IP? Run a WebRTC leak test with a baseline comparison, then check the privacy tells browsers reveal alongside an IP. Each check is a separate, button-triggered session — nothing runs behind your back.

Exposure

WebRTC IP leak test

Your browser negotiates a peer connection the way it would for a video call. Any candidate IP it discovers is shown and compared against your baseline — mDNS-only (.local) candidates mean your browser is already hiding local addresses.

Waiting — nothing runs until you press the button.

    Fingerprint

    Privacy tells

    Your timezone and language settings are shared automatically — compared against your IP's country to spot mismatches, along with your Do Not Track setting.

    Waiting — nothing runs until you press the button.

      Every request these tests make

      Each session is button-triggered and makes direct, browser-side calls — our server is not in the path:

      • stun.l.google.com:19302 — WebRTC candidate discovery (leak test)
      • speed.cloudflare.com/meta — your baseline public IP (run it on What Is My IP)

      Nothing else is contacted. Nothing you type on this site is ever sent anywhere — the password tools on oopsmypassword.com are 100% client-side.

      How this works — and how to verify it

      These tests make direct, browser-side calls to three services — speed.cloudflare.com, api.ipify.org and dns.google — and to a public STUN server. Nothing else is contacted. Verify it yourself: open your browser's Network tab, run each test, and compare the request list.

      How a WebRTC IP leak happens

      WebRTC needs real addresses to build peer-to-peer audio and video streams. To find them, the browser asks a STUN server — in this test, a public Google one — to report the IP it sees. The catch: this lookup can use the direct network interface instead of the VPN tunnel, which is exactly how your real IP ends up in the candidate list while everything else looks protected.

      The baseline comparison turns that into a definite answer. The What Is My IP page captures your public IP in this tab's memory; with your VPN on, run the leak test and any candidate matching that baseline belongs to the real connection, not the tunnel. If no baseline exists, the verdict says so instead of guessing. And if your browser only reports .local mDNS candidates — the default on modern Chrome and Edge — local addresses are already masked and there is nothing sensitive to leak.

      WebRTC & IP leaks — common questions

      What is a WebRTC IP leak?

      WebRTC is the browser technology behind in-browser video and voice. To connect quickly, it can discover your real IP addresses through STUN lookups — even while a VPN is active. If a candidate address here matches your real connection instead of your VPN's, the VPN is leaking.

      How do I read the verdicts on this test?

      Local (host) addresses are what your device exposes on its own network; mDNS aliases mean your browser is already hiding them. Public addresses seen via STUN are compared against your baseline — if they match, they belong to your current connection; if they differ while a VPN is on, that is a likely WebRTC leak.

      Does the site see my IP when I run this test?

      Only two services are contacted, and only when you press the button: a Google STUN server (stun.l.google.com:19302) for the WebRTC candidates and speed.cloudflare.com/meta for the baseline IP. Your browser talks to them directly — our server is not in the path.

      What is the baseline comparison?

      The baseline is your public IP captured by the What Is My IP page — held in this tab's memory only. Turn your VPN on and run the leak test: any WebRTC candidate matching that baseline belongs to the real connection, not the tunnel. If no baseline exists yet, the verdict says so instead of guessing.

      Should I disable WebRTC in my browser?

      Not necessarily. On Chrome and Edge, WebRTC already hides local addresses behind mDNS (.local) candidates, and modern browsers give you IP-handling policies. If your VPN consistently leaks, first update the VPN app — blocking WebRTC entirely can break legitimate video calls.