If you use a VPN, you probably care about what websites can see about your connection. Checking whether your public IP changed is the most reliable first step.
A WebRTC exposure check is a useful secondary test: it looks for extra network information your browser might reveal in certain situations.
Try it here: VPN Status Check (includes WebRTC exposure check).
What is WebRTC?
WebRTC is a browser technology that enables real-time communication features like voice calls, video calls, and peer-to-peer connections.
What is a “WebRTC leak”?
A “WebRTC leak” is when your browser reveals additional IP addresses through WebRTC. These can include:
- Local/private IPs (common and usually not a big deal)
- IPv6 addresses (can matter for VPN privacy depending on your setup)
- A different public IP than the one shown on the page (rare, but the strongest exposure signal)
Why we offer a WebRTC exposure check
Many “VPN detector” tools try to guess whether you’re on a VPN using IP reputation labels. Those labels can be wrong.
Our approach is simpler and more reliable:
- Primary check: did your public IP change after turning the VPN on?
- Secondary check: does WebRTC reveal extra IP information?
The WebRTC exposure check is there to help you catch obvious surprises. In many modern browsers, WebRTC IPs are intentionally hidden — and that’s a good outcome.
How to use the WebRTC check correctly
- Turn VPN off → run the WebRTC check.
- Turn VPN on → run the WebRTC check again.
- Compare results.
Tip: if your VPN check shows your IP changed, your VPN is likely routing traffic correctly. WebRTC is an extra layer of validation.
What results mean
No IPs shown
This is common in modern browsers due to privacy protections. It typically means your browser isn’t exposing WebRTC IP candidates to scripts.
Only local/private IPs shown
Also common. Local/private IPs (like 192.168.x.x) don’t necessarily indicate a privacy leak.
IPv6 addresses shown
This can matter if your VPN doesn’t tunnel IPv6 or if you’re trying to ensure everything routes through the VPN. If you care about IPv6 privacy, consider adding an IPv6 leak test later.
A different public IP than the page IP
This is the strongest red flag. It suggests WebRTC may be exposing a public IP that differs from what the page sees. It’s uncommon, but worth investigating if it happens.
Related guides: Is my VPN working? · VPN not detected — what it means