WebRTC leak test

Compare WebRTC and HTTPS public IP observations

See which browser-exposed ICE candidates are available and whether eligible direct public WebRTC evidence differs from the public address observed for this HTTPS connection.

Live result

Current WebRTC comparison

JavaScript required

JavaScript is required to gather browser-local ICE candidates and run the live comparison.

The result shows whether WebRTC exposed a public address different from the main connection.

Public-address comparison

HTTPS-observed public IP: JavaScript required
WebRTC public IPs: JavaScript required
Public IP difference: JavaScript required

Candidate exposure

Local/private or mDNS state: JavaScript required
STUN state: JavaScript required

Host: 0
Server-reflexive: 0
Relay: 0
Total: 0

ICE candidate technical details

Relay candidates remain separate and are excluded from direct public-IP comparison evidence.

JavaScript is required to inspect candidates.

ICE candidate errors

JavaScript is required to gather candidates.

What this test measures

The test measures browser-exposed ICE candidate types and addresses, then compares eligible numeric public host or server-reflexive candidates with the public source address observed by MyLeaks for the current HTTPS connection. Relay candidates do not become direct public-IP evidence.

How it works

The browser gathers WebRTC connection candidates and MyLeaks compares any public addresses with the main connection address. The test does not request camera or microphone access.

Candidate types

Host: an address exposed directly by the browser; it may be public, local/private, or represented by mDNS.
Server-reflexive (srflx): a mapped address returned through STUN.
Relay: a relayed path, kept separate from direct public-IP evidence.
Local/private: numeric address space associated with a local interface or private network.
mDNS: a .local name that can hide a numeric local address.

What the result means

A completed match means no different public IP was observed in this comparison. A mismatch means WebRTC exposed a public IP different from HTTPS, proving only that different paths or addresses were observed. Unavailable, timeout, error, or no public candidate remains neutral.

Limitations

Browser privacy policies, extensions, enterprise controls, VPN routing, and browser versions can change candidate exposure.
Blocked UDP can prevent MyLeaks STUN from participating.
The MyLeaks STUN service is IPv4-only. An IPv6 candidate may be shown if the browser exposes one, but MyLeaks provides no dedicated IPv6 Leak Test.