WebRTC Leak Test

Check public addresses exposed by this browser’s real-time connection feature.

Check addresses exposed through WebRTC

This browser check asks a Google STUN server which address it can see. It does not access your camera or microphone, and results stay in this page.

A local address is not your internet address. A different public address deserves investigation, but can also reflect IPv4/IPv6 or split tunnelling. This is not a DNS leak test or an overall security verdict.

How to read a result

Keep the same browser and network for both runs. Note your public IP with the VPN disconnected, connect in the VPN app, then repeat the test. Compare the observed addresses and operators with what your provider documents.

A different address is a clue to investigate. It is not, on its own, a security diagnosis. Browser DNS settings, IPv4 and IPv6, split tunnelling and other extensions can change the result.

How to check whether your VPN is working

Check your public IP address · All tools

Guides

What is WebRTC?

Understand browser calls, connection candidates and why a WebRTC address check differs from a public IP lookup or DNS test.

How to check if your VPN is working

Compare public IP, DNS and WebRTC observations, then test the app you use. Learn what each result establishes and what to investigate next.

What is my IP?

See your public IP address, approximate location and internet provider.

DNS lookup

Look up A, AAAA, MX, TXT, CNAME and NS records through Google Public DNS.

IPv6 connectivity test

Test whether this browser can reach an IPv6-only address service.