WebRTC leak investigation
Inspect browser connection candidates and compare with your intended network exit.
Clicking contacts Google STUN for candidates without using a camera or microphone. This connection may follow a different route from the webpage.
Not tested. Click to begin.
Understanding results
Does a candidate IP prove a leak?
Compare with your intended exit. Candidates may be local, STUN-mapped or relayed; they are not necessarily used by all websites. Review the proxy's WebRTC configuration.
Do no candidates mean it is safe?
No. Browser restrictions, mDNS masking or unreachable nodes can hide data. Keep other test conditions unchanged when retesting a setting.
This is a point-in-time observation, not a security certification.Read the methods · Understand data flows