WebRTC leak test
WebRTC can reveal the public IP your browser really uses, even when you have a proxy or VPN configured. This test runs entirely in your browser and compares what WebRTC exposes with the IP your connection presents over HTTP.
Testing for WebRTC leaks…
WebRTC can reveal the public IP your browser really uses, independent of your proxy settings.
Public IP via WebRTC
…
Connection IP (HTTP)
…
What is a WebRTC leak?
WebRTC is the browser technology behind video calls and peer-to-peer connections. To establish a direct link, it asks a STUN server for your public IP address — and it does this at the browser level, which can sidestep a proxy that only covers your normal HTTP traffic.
The result is a leak: a website using WebRTC can learn your true public IP even though your proxy makes ordinary requests appear to come from elsewhere. This test flags the problem when the IP WebRTC discovers differs from the IP your HTTP connection presents.
How to stop WebRTC from leaking your IP
You can disable or restrict WebRTC in your browser settings or with a trusted extension, use a browser profile that forces all traffic — including WebRTC — through your proxy, or run the proxy at the operating-system or network level so nothing bypasses it.
For automation, configure your headless browser or scraping framework to route WebRTC through the same proxy as your HTTP traffic, or disable the WebRTC media stack entirely if your workflow does not need it.
Frequently asked questions
- Does this test send my IP anywhere?
- The WebRTC discovery runs entirely in your browser. The tool separately reads the public IP your HTTP connection already presents to every site, purely to compare the two. Nothing about your result is stored.
- Why do I only see one IP, or none?
- Modern browsers hide local network IPs behind mDNS (.local) hostnames, so you may only see a single public IP or none at all. Seeing no public IP different from your connection IP is a good sign for privacy.
- I use a proxy but WebRTC shows a different IP — why?
- That is the leak. Your proxy is covering HTTP traffic but not WebRTC, so WebRTC reached a STUN server directly and exposed your real public IP. Force WebRTC through the proxy or disable it to close the gap.
- Is WebRTC dangerous?
- WebRTC itself is a legitimate, useful technology. The privacy concern is only that it can reveal your real IP independently of your proxy. If anonymity matters for your task, make sure WebRTC is routed through the same proxy or turned off.
Need a different IP or location?
Route your traffic through real residential IPs in 195+ countries — from 5 GB, pay as you go, bandwidth never expires.