Free network tool

WebRTC leak test

Check whether your browser reveals another public address through WebRTC, especially while using a VPN.

Your result

Checking WebRTC addresses…

Gathering connection candidates and comparing them with your web request.

Checking
Web request IPChecking…
Public candidatesChecking…
Local candidatesChecking…

This test contacts Google’s public STUN service (stun.l.google.com:19302). Candidate addresses are inspected locally and are not uploaded to Localtonet.

How it works

Understand an address mismatch

WebRTC helps browsers make direct connections for calls and data transfers. During connection discovery it can expose candidate IP addresses, which may use a different network route from an ordinary website request.

Connect to your VPN before running the test, then compare any different public address with the route your VPN should use. Only addresses from the same IP family are compared: IPv4 and IPv6 can both be normal on one connection. Use the DNS leak test to inspect DNS resolver paths separately.

Different public address

This may be a VPN bypass, split tunneling or another gateway. Compare it with the route your VPN is expected to use.

Local address visible

A private address exposes local network information. It does not by itself show that traffic bypassed a VPN.

No public candidate

Browser privacy controls, blocked STUN traffic or network policy may hide candidates. The result is inconclusive.

What to do next

Review your VPN’s WebRTC controls and browser privacy settings, then check again after making a change.

View candidate addresses and connection details

Run the test to see its detected details.

Common questions

Does no mismatch mean my VPN is fully protected?

No. This is a single browser observation, and candidate gathering can be blocked or limited.

What is an mDNS candidate?

Browsers can replace a local address with a temporary .local hostname. This helps hide the raw local address from page scripts.

Does the test use my camera or microphone?

No. It creates a data channel to gather connection candidates and does not request media access.

Are the candidate addresses saved?

This tool keeps them in the page. It does not upload the candidate list or the complete session description to Localtonet.

support