WebRTC / STUN leak check

WebRTC Leak Check

After changing networks or using a proxy, check WebRTC for additional public exits. Private addresses and masked host names are shown separately, not automatically treated as public IP leaks.

Leak score--Waiting
Server public IP--
WebRTC public candidates--
Local address exposure--
STUN reachability--
Waiting
IP info lookupDNS leak checkBot detection

WebRTC evidence matrix

Check whether WebRTC reveals additional public exits and whether they match your network or proxy setup.

Network & identity
Total candidates--ICE
Host candidates--host
Srflx candidates--server reflexive
mDNS masks--local masking
Relay candidates--TURN relay
SDP report ID--TraceScope vector v1
ICE events--ordered event log
RTCPeerConnection--browser API
Media permission--no prompt
Public IP parity--server vs STUN

ICE candidates

Each row keeps source, type, protocol, address, port and scope. Raw candidate strings are preserved in the JSON block below.

STUNTypeProtocolAddressPortRelatedScope

Raw evidence JSON

Includes STUN node receipts, candidates, server public proof, permission state and the final verdict for evidence packages.

{}

How to read it

Check whether a page can see additional IP addresses.

01

Public IP parity

When WebRTC srflx candidates match the server-observed public IP, there is usually no proxy bypass leak.

02

Private exposure

If host candidates reveal 10.x, 192.168.x or 172.16-31.x addresses, review browser privacy policy first.

03

mDNS masking

Modern Chrome / Edge often replaces host addresses with .local names; this is privacy protection, not a failure by itself.