See which public addresses WebRTC exposes.
Start a check to compare the public IP seen by this website with addresses exposed through WebRTC. The result cannot identify your real ISP address or confirm whether a VPN is connected.
No sign-up · test details shown before you start
Starting this check contacts this website for your public IP and Google’s public STUN service for WebRTC addresses. Results remain on this page and are not submitted to our click analytics. These services necessarily receive connection information.
DNS is not tested here
Read the DNS leak-check guide for the separate steps. This tool cannot determine your real ISP address or whether a VPN is connected.
Our application does not save these test IPs. Hosting and STUN services may process network metadata under their own policies. See our privacy policy.
Review your VPN settings
Check your provider’s leak-protection instructions and repeat the check after changing settings. A matching result does not prove complete protection. DNS is not tested by this tool.
Common questions
- Does a matching result mean I am anonymous?
- No. It means the public WebRTC addresses observed in this run matched the address seen by this website. DNS, other apps and other network paths were not tested.
- Does a different IP prove a VPN leak?
- No. Different routing, proxies, multiple connections and IPv4 versus IPv6 can produce different addresses. Compare with your VPN app and your VPN-off baseline before drawing a conclusion.
- What happens when I start the check?
- Your browser contacts this website for your public IP and Google’s public STUN service for WebRTC addresses. The test does not submit these results to our analytics.
- Does this tool test DNS?
- No. Follow the separate DNS guide to check which DNS resolvers answer your requests.