What is WebRTC leak?
A WebRTC leak is when a browser's real-time communication APIs reveal your true IP address even though you're behind a VPN or proxy. WebRTC gathers candidate IPs via STUN to establish peer connections, and those candidates can expose the underlying public or local IP a VPN was meant to hide.
Last updated
Because WebRTC operates below the page's normal network layer, it can surface an IP that differs from the one your HTTP requests appear to use — a strong tell that the visible IP is a proxy or VPN.
Modern browsers limit this with mDNS hostnames for local addresses, but a public-IP mismatch between WebRTC and the HTTP source remains a useful detection signal.
How does a WebRTC leak expose a VPN user?
A WebRTC leak happens when a browser's real-time communication features reveal your true IP address while you are behind a VPN or proxy. WebRTC gathers candidate addresses to set up peer connections, and those candidates can expose the public or local address the VPN was meant to hide. For detection, the leak is a strong tell. The address WebRTC reports can differ from the one your normal web requests use, and a mismatch indicates the visible address is a relay. Modern browsers limit local-address exposure with mDNS hostnames, but a public-address mismatch still stands out. A user who sees a mismatch should review the browser's and the VPN's settings. IPLogs can compare a WebRTC-reported address with the source address of the request. You can test your own connection at iplogs.com/webrtc-leak-test. Checks of an address are free, need no API key and cover IPv4 and IPv6.
How IPLogs handles it
IPLogs can compare a WebRTC-reported IP against the HTTP source IP; a mismatch indicates the connection is being relayed.