WebRTC Leak Test
Check whether your browser reveals your real or local IP address through WebRTC, even behind a VPN.
The IP address this site sees
If you use a VPN, this should be the VPN's address.
Your browser has WebRTC turned off or does not support it, so it cannot leak your address this way.
| Address | Kind | Found |
|---|---|---|
|
The test asks Google's public STUN server (stun.l.google.com) which address your connection comes from, the same way video-call apps do. Nothing is stored.
WebRTC Leak Test
WebRTC lets browsers make video and voice calls directly, and to do that it discovers your IP addresses. A website can ask for them without any permission prompt, which can reveal your real public IP address even when you use a VPN or proxy. This test shows the addresses your browser exposes and compares them with the public IP address our server sees.
How to use WebRTC Leak Test
- Connect your VPN if you use one.
- Click Run the leak test.
- Compare the addresses found with your public IP. A public address that is not your VPN's means a leak.
When it comes in handy
- Checking a VPN before relying on it for privacy.
- Testing browser privacy settings and extensions.
Frequently asked questions
- How do I stop a WebRTC leak?
- Use a VPN app with WebRTC leak protection, or a browser setting or extension that limits WebRTC. In Firefox, media.peerconnection.enabled in about:config turns WebRTC off, which also disables browser video calls.
- What is an mDNS (.local) address?
- Modern browsers hide your local IP address behind a random .local name. That is the protection working, not a leak.