WebRTC leak test

Compare your web exit with WebRTC candidates and inspect public and local address visibility.

Browser WebRTC

Not checked

Collect public and local candidates and compare them with your web exit.

Usually about 10 seconds

No camera or microphone permission neededThe test connects to Google STUN, which will see this connection’s network address.

Test results

Not started

Actual observations only

See which addresses your browser exposes

Start a test to compare public addresses and inspect local address visibility.

Public IPv4 / IPv6Local addresses & mDNSICE candidates

Results cover the connection candidates collected by this browser in this run, not every app, network path or established connection.

About the results

Check the public exit, then local addresses

Does a matching exit mean no leaks?

A match only covers the observed public candidates of the same address family. Network changes, split tunneling and other apps need separate checks. Learn about WebRTC network paths ↗

How do mDNS and local IPs differ?

An mDNS name ending in .local replaces a local IP. A readable private IP reveals local network information, which is distinct from exposing a public exit.

Why might no public address appear?

Browser policies and network settings affect collection. A completed collection with no public candidates is shown separately from timeouts and STUN failures.