Skip to tool
KeyboardTester.click

Tool categories

WebRTC leak test

Free WebRTC Leak Test

Free online WebRTC leak test. Detect IP address leaks through your browser even while using a VPN. Checks IPv4, IPv6, mDNS and STUN. Fast, instant, private.

Download from Microsoft Store Download from Microsoft Store

WebRTC Leak Test

Click Start scan to see what IP addresses your browser exposes via WebRTC.

WebRTC can leak your real local and public IP addresses to websites even when you are using a VPN. Click Start scan to detect what your browser exposes.
Public IP -
The IP address websites see. With a VPN on this should match your VPN server, not your ISP.
Local IPs -
Your private network address (192.168.x, 10.x). Modern Chrome hides this behind an mDNS hash ending in .local.
IPv6 -
Your IPv6 address. If your VPN does not tunnel IPv6, this leaks even when IPv4 is protected.
Status -
Rate WebRTC Leak Test: 5.0 (1 rating)

WebRTC Leak Test is a free, browser-based online utility that lets you detect IP address leaks through your browser even when using a VPN.

  • Cost: Free, no signup
  • Install: None — runs in the browser
  • Privacy: Runs locally, no uploads
  • Platforms: Windows, macOS, Linux, Android, iOS
  • Time: Under a minute

WebRTC Leak Test: Understand Browser IP Candidates

This WebRTC leak test shows the network candidates your browser exposes during a connection check. Compare the displayed result with and without your normal VPN setup to see whether the visible addresses change. A public address, private address or masked .local candidate needs context: this browser test cannot certify that every application or network path is protected.

This tool gathers the connection candidates exposed to the page and can contact STUN servers during the check. The result describes this browser session. It is not a local-only network operation and does not establish how every application uses your VPN.

How to Read Your Result

  • Public address — compare a public candidate with the address and routing you expect for the current connection. Split tunnelling, browser policy and VPN configuration need context; an address by itself does not identify the reason it appeared.
  • Local candidates — private addresses or privacy-masked .local names can appear depending on browser and network policy. A masked name is not the same as a directly displayed public address.
  • IPv6 — check the candidate type and your expected IPv6 routing as well as IPv4. The browser result is not a complete audit of VPN or network configuration.

Why WebRTC Leaks Even With a VPN On

VPN routing, split-tunnel settings, proxy configuration and browser candidate policies affect the addresses that are exposed. Read the current documentation for your exact setup and compare repeat runs with the same browser. A brand name or price does not guarantee a particular WebRTC result.

If the displayed candidates differ from what you expect, check the VPN and browser documentation before changing settings. Restricting or disabling WebRTC can affect browser calls and other real-time features, so verify the intended apps after any change.

Per-Browser Fix Summary

  • Chrome / Edge — review the current browser and VPN guidance for candidate-routing controls. A third-party extension is not automatically necessary or sufficient.
  • Firefox — review current privacy and connection settings and understand which call features a change affects.
  • Brave — inspect the current WebRTC IP-handling policy and compare the result after one documented change.
  • Safari — check the current version’s supported controls rather than relying on an experimental flag name from a different release.
  • Any browser — confirm the expected network path and test the apps you need. No single setting change guarantees privacy for every application.

Seeing a .local Address? That Is Not a Leak

A .local ICE candidate is a browser privacy mechanism that can hide a directly displayed local address. Interpret it alongside the other candidates and the expected network path. Its presence alone does not prove either a public-IP leak or complete privacy.

Common Myths Worth Busting

  • Private-browsing mode does not by itself establish how WebRTC candidates are routed. Test the actual mode and connection you intend to use.
  • A VPN label does not show every routing and browser-policy setting. Compare the observed candidates with the expected connection.
  • Disabling WebRTC is not a universal requirement. Understand the current setup and the effect on calling features before changing it.
  • A .local candidate is not a directly displayed public IP. It is also not proof that every other network path is protected.

WebRTC Leak Test FAQs

What does an incomplete WebRTC leak test mean?

The browser may restrict candidate gathering, a STUN request may fail or the network may block the check. Incomplete output is not proof that there is no leak and is not proof that a VPN has failed.

Is a .local address the same as a leaked public IP?

No. A .local candidate can be a privacy-masked local identifier. Read the candidate type and compare public addresses with your expected connection; the label alone does not establish a public-IP leak.

Does a no-leak result guarantee my VPN privacy?

No. This checks browser-visible WebRTC behavior under the current conditions. Other applications, DNS handling and different network routes are separate questions, so it should not be treated as a complete VPN security audit.

Windows app

KeyboardTester.click is available from Microsoft Store

Install the official Windows app shortcut, or keep using the same free testing tools in your browser.

Download from Microsoft Store Download from Microsoft Store

More tools to try

Explore Utility tools & stories

28 tools · 2 Web Stories

View all
Man in eyeglasses fitting a side panel onto an open PC case under colorful light 01 / 10 DDR5 buying math Pay $120 more for 2 nanoseconds? CL30 vs CL36 looks big on the box. The real difference is 2 nanoseconds.
Open full story Read full guide Card 1 of 10 in CL30 vs CL36: Worth Paying More?
Man looking frustrated while holding a smartphone in an office 01 / 10 Phone vibration test Your phone stopped buzzing Before you book a repair, find out whether it is the motor or just a setting.
Open full story Read full guide Card 1 of 10 in Phone Not Vibrating?

Web Story

Opening story…

Utility guides and reviews

View all
More Utility guides