tools / webrtc-test
WebRTC exit & leak check/
Check WebRTC’s UDP exits against HTTP exits of the same IP version to investigate proxy routes and IP exposure.
WebRTC / STUN exits
Your browser connects separately to the STUN services listed below to collect UDP exit addresses, waiting up to 10 seconds for each. No camera or microphone is used. Results do not represent the final route used by actual calls or other applications. The STUN services can see where requests come from.
A different exit from HTTP does not necessarily mean a leak; it may reflect proxy routing rules. After switching networks, refresh the HTTP exits below, then run the test again. Missing candidates may be due to browser policies, network restrictions or STUN timeouts. Local candidate addresses are not displayed.
HTTP exit comparison
After switching networks, refresh the HTTP exits before starting the WebRTC test. Compare addresses of the same IP version and check the test times.
FAQ
Will this turn on my camera or microphone?
No. It creates a data channel and gathers STUN candidates. It does not access the camera or microphone or establish a real call.
Does a different WebRTC IP mean a leak?
Not necessarily. UDP and HTTP may follow different proxies or routes. This page only compares addresses of the same IP version. Check your intended exit; a difference is not automatically a leak.
Why compare only the same IP version?
IPv4 and IPv6 are inherently different addresses. Comparison runs only when a successful HTTP result of the same version is available, with its check time displayed. Without that reference, it stays unconfirmed.
Why can an exit appear despite STUN errors?
A connection may produce both error events and valid candidates. The page keeps valid UDP exits received throughout the run. Error counts aid diagnosis but do not invalidate results already obtained.
Does getting no STUN exit mean I am safe?
No. Browser policies, network restrictions, service faults or timeouts may prevent candidates. Each test waits up to 10 seconds and supports retry and stop. Unconfirmed results are never labeled safe.
Does the test expose local IPs or store results?
Local and mDNS candidate addresses are counted but not displayed. STUN services see the connection source. Results stay on this page. Stopping or leaving closes connections; hiding IPs disables copying and geolocation links.