Toolsky

Free Online Tools & Utilities for Every Task.

WebRTC Leak Test

Check if your real IP address is leaking through WebRTC.

This test will identify if your browser leaks your real IP address via WebRTC APIs.

Detected IP Addresses
Public WebRTC IPs
Local / Private IPs
Privacy Insight: If you are using a VPN and see your **real ISP public IP** in the list above, your browser is leaking your identity through WebRTC. Consider using a WebRTC blocker extension.

A VPN can be connected, showing a reassuring foreign location, while a website still learns your real IP address through a side channel in your browser. That side channel is usually WebRTC. The WebRTC Leak Test checks whether your actual public or local IP addresses are being exposed through WebRTC, even when the rest of your traffic is routed through a VPN or proxy.

How WebRTC Can Reveal an IP Address

WebRTC is the browser technology behind voice calls, video meetings and peer-to-peer file sharing on the web — it powers in-browser calls on many familiar platforms. To set up a direct connection between two browsers, WebRTC gathers "ICE candidates": the network addresses through which your browser can be reached. To find your public address it asks a STUN server, which reports back the IP it sees.

The catch is that this discovery happens at browser level, and historically it bypassed VPN tunnels: the STUN request could travel outside the tunnel, or the browser would happily hand a website your real public and local (LAN) addresses as connection candidates. Any site you visit can trigger this gathering silently — no call needs to take place. Modern browsers have improved matters, notably by masking local addresses behind random mDNS hostnames, but public-IP exposure through an improperly routed VPN remains a genuine and testable concern.

Features of the WebRTC Leak Test

  • Public IP detection: shows the public address WebRTC reports for your connection, which you can compare with the address your VPN claims to give you.
  • Local IP visibility check: reveals whether your private network address (such as a 192.168.x.x address) is exposed or properly masked.
  • Instant in-browser results: the test runs where the leak would happen — in your own browser — with no software to install.
  • VPN verification: run it with your VPN on and off to see, concretely, whether the tunnel covers WebRTC traffic.

How to Run the Leak Test

  1. Connect to your VPN or proxy, if you use one, and let it settle into its connected state.
  2. Open the WebRTC Leak Test in the browser you normally use.
  3. Allow the test a few seconds to gather ICE candidates.
  4. Read the reported addresses: note the public IP and any local IPs shown.
  5. Compare the public IP against the one your VPN is supposed to provide — check it against your IP as seen normally.
  6. If the public IP matches your real ISP address rather than the VPN's, WebRTC is leaking; disconnect the VPN and run the test again to confirm what your unprotected address looks like.

Reading the Results

Three outcomes cover most situations. No leak: with the VPN connected, the test shows only the VPN's public address, and local addresses appear as meaningless mDNS strings (random characters ending in .local) or not at all — this is a modern browser behaving correctly. Public IP leak: the test shows your ISP-assigned address while the VPN is supposedly active — websites can identify your real connection and approximate location regardless of the tunnel. Local IP exposure: your true LAN address is visible; less serious alone, but it fingerprints your home network setup and was the classic early WebRTC leak.

The test pairs naturally with a DNS leak test, because a connection can pass one check and fail the other: DNS requests leaking to your ISP reveal which sites you visit even when WebRTC is sealed. Together with a browser fingerprint audit, they give a realistic picture of what your browser discloses before you change any settings.

Tips, Fixes and Common Misunderstandings

Fix options, from gentlest to strongest: use a VPN whose own browser extension or app explicitly blocks WebRTC leaks; enable any "prevent WebRTC IP leak" setting your VPN or browser offers; or disable WebRTC entirely in the browser (Firefox exposes this directly; Chromium browsers typically need an extension or enterprise policy). Disabling WebRTC completely can break legitimate browser-based voice and video calls, so prefer a leak-prevention setting where one exists.

A masked local IP is not a failure. Strings ending in .local are mDNS masks doing their job. Worry about a recognisable public address or a plain 192.168/10.x address in the results instead.

Test each browser separately. VPN coverage and WebRTC behaviour differ between browsers and between a browser with and without the VPN's extension. Passing in one browser proves nothing about another.

The test shows exposure, not intent. Most websites never inspect ICE candidates; the risk comes from the minority that log them. A leak means the information is available to any site that asks, which is the thing worth fixing. The broader WebRTC picture is documented in MDN's WebRTC API reference.

Frequently Asked Questions About WebRTC Leaks

What exactly is a WebRTC leak?

It is the exposure of your real IP address — public, local, or both — to websites through the WebRTC API, potentially bypassing a VPN or proxy that correctly hides the same address from ordinary web traffic.

Does a WebRTC leak mean my VPN is broken?

Not necessarily broken, but incompletely configured for browser traffic. Many VPNs route ordinary requests correctly while WebRTC discovery escapes through the browser; a leak setting or extension usually closes the gap.

Is my local IP address dangerous to expose?

By itself it cannot locate or reach you from the internet, but it aids browser fingerprinting and reveals your network layout. Modern browsers mask it by default, so a visible local IP means a setting or browser version needs attention.

Can websites really see this without my permission?

Yes. Gathering ICE candidates requires no permission prompt and no active call. Any page can run the check silently in the background, which is precisely why testing matters.

Should I just disable WebRTC altogether?

Only if you do not use browser-based calls or meetings. Disabling it stops leaks completely but also breaks legitimate WebRTC applications; a leak-prevention option in your VPN or browser is usually the better balance.

Why does the test show an address ending in .local?

That is an mDNS hostname masking your real local address — a privacy protection built into modern browsers. It is expected behaviour and not a leak.

Does incognito or private mode prevent WebRTC leaks?

No. Private windows change local storage behaviour, not network discovery. WebRTC exposes the same candidates in a private window as in a normal one.

Know What Your Browser Gives Away

Privacy tools only protect the paths they cover, and WebRTC is the path most often forgotten. A ten-second test tells you whether your browser quietly contradicts your VPN — and if it does, the fix is usually one setting away.