Client IP & WebRTC Leak Test
See the public and local IP addresses your browser exposes, including addresses a VPN or proxy might not hide.
Public IP (HTTP request)
WebRTC candidates
Scanning for local network addresses…
Related tools
About this tool
A "WebRTC leak" is a well-known privacy gap: the same browser API that powers video calls and peer-to-peer file transfers also negotiates a direct connection between two browsers, and that negotiation process can expose IP addresses that never show up in an ordinary HTTP request. This tool runs both checks side by side — the plain public IP address a website sees from your HTTP requests, and the addresses your browser's WebRTC stack reveals during connection setup — so you can compare them and see whether anything is being exposed that you didn't expect.
The public IP section makes two lookups: a strict IPv4-only request and one that returns whichever address family your connection actually prefers, which can be an IPv6 address on a network with native IPv6 support. This is the address a normal website, and anyone it shares logs with, sees you connecting from.
The WebRTC section starts a local connection attempt using the standard ICE candidate-gathering process (the same mechanism a video call app uses to find the best path between two peers) and lists every unique address that surfaces, tagged by candidate type: "host" candidates come from your machine's own network interfaces, "srflx" (server-reflexive) candidates come back from a STUN server and typically match your public IP, and "relay" candidates route through a TURN server. A host candidate with a real IP address rather than a browser-generated ".local" placeholder is the classic leak: it can reveal your actual LAN IP address even when a VPN is correctly hiding your public IP everywhere else.
Modern versions of Chrome and Firefox mitigate part of this by replacing the real local IP in host candidates with a random per-session ".local" hostname resolved only through mDNS on your own network, rather than exposing the literal address to the page. This tool flags that case separately, since it means the leak has already been mitigated by your browser rather than by your VPN or network configuration — a real host-type IP address showing up is the case actually worth investigating.
Both checks require genuine network activity: the public IP lookups need a live HTTP connection to a lookup service, and the WebRTC scan needs to reach a public STUN server to discover its reflexive address, so this is one of the few tools in this toolbox that doesn't work fully offline. Nothing about your results is stored anywhere — the page just reports what your own browser and network stack reveal, the same way any other website you visit could observe it.
Frequently asked questions
What is a WebRTC leak? expand_more
It's when the address-negotiation process WebRTC uses to set up a peer-to-peer connection reveals your real local network IP address (and sometimes your public IP) to a web page, even if a VPN or proxy is hiding your address for ordinary web traffic.
I'm using a VPN — why does this still show my real local IP? expand_more
A VPN typically only re-routes traffic that goes through the operating system's normal networking stack. WebRTC's ICE candidate gathering can enumerate your machine's actual network interfaces directly, which a VPN doesn't always intercept, so a "host" candidate with a real IP can bypass it.
Why does my "local" address look like a random string ending in .local instead of an IP? expand_more
That's mDNS obfuscation, a privacy feature in modern Chrome and Firefox: instead of exposing your literal LAN IP in a host candidate, the browser hands out a random per-session hostname that only resolves on your own local network. It's a sign the leak has already been mitigated.
Does this tool need an internet connection? expand_more
Yes — both the public IP lookup and the WebRTC STUN check require live network access, unlike most tools in this toolbox.
Is my IP address logged anywhere by this tool? expand_more
No. The results are computed and shown directly in your browser for your own inspection; this page doesn't store or transmit them anywhere beyond the standard lookups needed to detect them.