MyVPNCheck
Run quick check

Check for WebRTC address exposure

WebRTC can reveal your real public IP or local network addresses even when using a VPN. This test inspects ICE candidates gathered via STUN.

DIAGNOSTIC CONSOLE

Public IP

Not checked yet
Not checked yet

Connection

Not checked yet
Not checked yet

Browser Exposure

Not checked yet
Not checked yet

Usually takes a few seconds

How the WebRTC test works

We create a temporary RTCPeerConnection with a STUN server. The browser gathers ICE (Interactive Connectivity Establishment) candidates — potential connection paths — which include:

  • Host candidates — your local network IPs (often masked as .local mDNS names in modern browsers)
  • Server-reflexive (srflx) candidates — your public IP as seen by the STUN server
  • Relay candidates — TURN relay addresses (if configured)

We compare any public srflx candidates to the HTTP public IP. If they differ, your browser may be exposing a different network interface.

Understanding results

No differing public address observed
The WebRTC test found no public IP that differs from your HTTP IP. This is the expected result when your VPN is working correctly in this browser.
Different public address detected
A public IP in the WebRTC candidates differs from your HTTP IP. This may indicate a WebRTC leak — your real ISP IP or another VPN interface is exposed.
Only private/mDNS candidates
The browser returned only local addresses (masked as .local names). This is common in modern browsers with WebRTC IP masking enabled. We cannot verify public exposure in this case.
Inconclusive / Timeout
The test couldn't complete within 8 seconds, or WebRTC is blocked/unsupported. No conclusion can be drawn.

Important limitations

  • Results apply only to this browser's WebRTC configuration. Other browsers, apps, or system-level traffic may behave differently.
  • Modern browsers (Firefox 68+, Chrome 70+, Safari 12+) mask local IPs with mDNS names (.local). This is a privacy feature, not a leak.
  • The test uses a public STUN server (Google by default) which receives connection metadata.
  • Browser extensions, firewall rules, or VPN client settings can affect results.

If a leak is detected

  • Disable WebRTC in browser settings — Firefox: media.peerconnection.enabled = false in about:config; Chrome/Safari: use an extension
  • Use a browser extension — "WebRTC Control" (Chrome/Firefox) or "WebRTC Leak Prevent" toggle WebRTC on/off per site
  • Check VPN client settings — Some VPN apps have built-in WebRTC leak protection
  • Test in a different browser — Verify the behavior is consistent