WebRTC leak test

See which connection candidates your browser exposes.

The test runs locally. It distinguishes public candidates, private network addresses, and privacy-preserving mDNS names instead of treating every candidate as a leak.

Local tests

Browser exposure

WebRTC candidates

Find public addresses exposed by the browser.

Not run

IPv6 route

Check whether an IPv6 path is available.

Not run

DNS leak testing requires controlled DNS infrastructure and is not included.

Interpretation

What counts as a meaningful warning?

Public address mismatch

A public candidate that differs from the server-visible VPN address can indicate another route. Compare its network owner with your original ISP before concluding that it is a leak.

Private address or mDNS

Private addresses are not public internet identities. Modern browsers often replace them with temporary .local names, preventing the page from learning the literal interface address.

Reference

Practical network privacy guides

WebRTC leaks explained without the myths Run a WebRTC leak test, understand ICE candidates and mDNS masking, and learn when a browser result indicates a genuine VPN problem. IPv6 leaks: what they are and how to fix them Check whether IPv6 traffic bypasses your VPN, understand why dual-stack connections leak, and apply practical fixes without guesswork. Can websites see your real IP behind a VPN? Learn which IP websites normally see through a VPN, how leaks occur, and why accounts, cookies, and browser signals still identify users.