This check collects WebRTC ICE candidates locally in the browser. It is useful when you want to know whether the browser exposes a public address that differs from the address the page sees.
Purpose
WebRTC can gather addresses for peer connections. Modern browsers may hide local addresses with mDNS names, but a public server-reflexive candidate can still be available depending on browser and network policy.
How The Check Works
After you choose Start WebRTC Check, the browser uses only the fixed STUN or STUNS servers configured by the administrator. Candidate addresses stay in the browser; the application records no candidate list.
Reading Results
Matched means a public candidate equals the request address visible to this page. Potential leak means a public candidate differs and deserves review. Inconclusive means there was no comparable public candidate, which is common and does not prove privacy protection.
Privacy And Limits
VPNs, NAT, IPv4/IPv6 routing, browser mDNS masking, extensions, and STUN policy can change results. Use DNS Leak Check to review DNS resolver exposure separately, and open WebRTC Leak Check for the full method and troubleshooting guide.