WebRTC test details (ICE candidate list)
WebRTC may expose private LAN IP addresses; this risk may remain even when network forwarding is enabled.
Method & precision limits
- An RTCPeerConnection is created only when you click "Run diagnostics"; candidates are read from onicecandidate. No camera or microphone permission is requested. Clicking the button means you agree to the processing scope shown directly below it.
- Modern browsers replace host private addresses with temporary names ending in .local; private addresses and temporary names are excluded from the leak decision. When unavailable we state "Not exposed by browser" instead of guessing 192.168.x.
- The decision uses host public and srflx public candidates: private host addresses (10/8, 172.16/12, 192.168/16, fc00::/7 and .local temporary names) are removed first; both kinds are compared with the connection exit separately for IPv4 and IPv6, never across versions. Any same-version public address that differs from the exit is treated as a leak.
- srflx is a STUN reflexive exit; when its public address differs from the page exit it is included in the leak decision. relay is a TURN relay address, shown in the table only and never used for any risk decision.
Note: WebRTC detection is affected by browser-level policies, network forwarding configurations and WebRTC-blocking extensions; this tool is for self-check only and cannot be 100% accurate. Most networks now support both IPv4 and IPv6; this tool checks the two address families independently.