BROWSER PRIVACY DIAGNOSTIC

WebRTC Leak Test

See which network addresses your browser can expose through WebRTC ICE discovery. Detect public server-reflexive addresses, local candidates, IPv4/IPv6, mDNS masking, and candidate transport details.

Runs locally in your browserNo camera or microphone permission is requested. The test compares WebRTC candidates with the public IP seen by Fast IP Checking.
Gathering ICE candidates from Google and Cloudflare STUN…00:00
Privacy Result
Start the test to inspect WebRTC
READY
Not testedNo ICE candidates collected yet
Total Candidates—
Public / srflx—
Host Candidates—
mDNS Masked—
IPv4—
IPv6—
IP Seen by Site—
WebRTC Public IP—
Waiting for testPress Start WebRTC Test to gather browser ICE candidates.
—
ProviderTypeAddressIP FamilyProtocolPort
No candidates yet.
srflx — Server ReflexiveA STUN-discovered address associated with your NAT-facing network path. If you are testing a VPN, compare it with the IP shown by your normal IP checker.
host — Local CandidateA candidate associated with a local interface. Modern browsers may replace a local IP with an .local mDNS hostname to reduce local-address exposure.
relay — TURN RelayA relay address supplied by a TURN server. This test uses STUN only, so relay candidates are not normally expected.
ImportantNo candidate returned is not proof that every application is leak-free. Browser privacy settings, VPN policy, firewall rules, UDP/STUN blocking, extensions, or WebRTC policy can suppress candidate gathering.

A leak warning is shown only when a same-family WebRTC server-reflexive address differs from the public IP seen by Fast IP Checking. Local host candidates are reported separately. Browser policy, VPN mode, UDP blocking, extensions, or firewall rules can affect ICE gathering.