WebRTC Leak Test
Your browser gathers the addresses it would offer a WebRTC peer. We compare them with the addresses websites normally see.
Result
Needs JavaScriptYour IP as websites see it
WebRTC addresses
WebRTC support
Session description (SDP)
Media devices
Frequently asked questions
What is a WebRTC leak?
To set up direct calls and file transfers, a browser asks a STUN server over UDP which public address it has. Browser proxies and many proxy extensions carry only web traffic, so that request goes out over your real connection, and any page can read the address that comes back.
How does this test work?
Your browser asks our STUN server for its public address, and we compare the answer with the IPv4 and IPv6 addresses websites see. If our server does not answer within three seconds, the test asks Cloudflare and Google instead. No connection is made to another peer.
Is a local address or a .local name a leak?
A name ending in .local means the browser is hiding your local address, which is what you want. A real local address such as 192.168.1.5 does not show where you are, but it does make your fingerprint more distinctive.
How do I fix a WebRTC leak?
Use a VPN or proxy client in TUN mode, so UDP and IPv6 go through it as well. You can also restrict WebRTC in the browser, though calls in the browser may then fail or get worse. In Firefox, set media.peerconnection.enabled to false in about:config, or install Disable WebRTC. In Chrome, install Google's WebRTC Network Limiter and choose "Use my proxy server (if present)" in its options. In Brave, set WebRTC IP handling policy to "Disable non-proxied UDP" in settings.
What is the SDP log?
SDP (Session Description Protocol) is the text a browser sends to set up a WebRTC connection. It lists codecs, ICE credentials, the DTLS certificate fingerprint and every candidate address, so you can check the raw data behind the result.