WebRTC Local IP Leak Test

Shows which local network addresses your browser reveals to any web page through WebRTC, and whether they are hidden behind randomised mDNS names.

Use the tool

Why this tool exists

WebRTC lets a page ask the browser for network candidates in order to set up peer connections. Historically that gave every page your real local IP address without any prompt, which trackers and ad scripts used as an extra fingerprint signal and which could expose the layout of a private network.

Modern browsers replace those addresses with random .local names, but extensions, older versions and some settings still leak them. This page opens a connection locally, with no STUN server, and lists every candidate the browser offers so you can see whether you are protected. Nothing is sent anywhere. Testing the public IP needs a server and is not part of this tool.

How to use it

  1. Open the page; the test runs automatically.
  2. Read the table of candidates and the verdict below it.
  3. Change a privacy setting or extension, then press Re-run to compare.

Frequently asked questions

Does this test my public IP?

No. That needs a request to a server, which this tool never makes. It only shows local addresses the browser exposes.

What is a .local address?

A random mDNS name the browser substitutes for your real local IP. It is the protected result.

How do I stop a leak?

Update your browser, and if real addresses show, restrict WebRTC in browser settings or with a privacy extension.