IPdidi
English

WebRTC leak test

Browsers use WebRTC for video calls and file sharing. To set up a call, the browser asks a STUN server for its public address, and that request can go around a VPN or proxy. This test makes the same request and compares the result with your connection IP.

Result

Checking…

Your connection IP: Checking…

Run the full browser fingerprint test

Addresses found through WebRTC

What a WebRTC leak is

Any website can start a WebRTC request with a few lines of JavaScript, without asking permission. If the public address it gets back differs from your connection IP, the site now knows both.

On a VPN or proxy, that second address is usually your real one.

Why proxies leak and VPNs usually don't

A system proxy, such as a proxy client like Clash in system proxy mode, only carries traffic that apps hand to it, which in a browser means HTTP and HTTPS. WebRTC sends UDP packets directly, so they leave through your normal connection.

A VPN, or a proxy client in TUN mode, captures traffic at the network level, including UDP. The STUN request then exits through the server like everything else.

How to fix a WebRTC leak

Guides