This page compares HTTP network observations with a STUN probe and shows the ICE candidate information your browser permits.
WebRTC leak test
How to interpret a WebRTC leak test
If a public WebRTC address differs from the HTTP egress, check whether your VPN or proxy covers UDP/STUN traffic. Multiple adapters, IPv4/IPv6 and corporate split tunneling can also cause differences. Compare the result with your expected egress.
Local IPs, mDNS and probe limits
Your browser may replace a local IP with a .local hostname. No visible public candidate means this probe observed no additional address; firewalls, browser policy or an unreachable probe can produce that result too. The test does not request camera or microphone access.
Frequently asked questions
Does WebRTC bypass every VPN?
No. Behavior depends on VPN routing, browser policy and the network. Compare any observed difference with the public egress you expect.
Does no leak detected mean complete protection?
No. It applies only to the HTTP and ICE observations in this run. It does not cover DNS, browser fingerprinting or traffic from other applications.
Related browser checks
DNS Leak Test
Observe recursive DNS resolvers with a dedicated probe and compare them with the DNS provider expected for your VPN, proxy or DNS-over-HTTPS setup.
Browser Privacy Check
Check browser privacy signals including storage, permissions, Canvas, WebGL and language. Understand fingerprint exposure and the limits of each check.
Browser Fingerprint Test
Test your browser fingerprint for free. Inspect Canvas, WebGL, audio, fonts, screen, time zone and language signals exposed to websites.