DNS & IP Leak Test
Check for WebRTC IP leaks and IPv4/IPv6 inconsistencies that can expose your real IP address even while using a VPN.
Run a Leak Test
How to Use the Leak Test
Check your VPN or proxy for real leaks in seconds.
Connect Your VPN
Turn on the VPN or proxy you want to test first.
Click Run Leak Test
The tool checks WebRTC and IPv4/IPv6 consistency live.
Check Your Public IP
Confirm it matches your VPN's IP, not your ISP's.
Review WebRTC IPs
See if any IP was exposed outside the VPN tunnel.
Check IPv6
See if your ISP's IPv6 address leaks around the VPN.
Fix Any Leaks
Follow the recommendations if a leak is found.
Why Use This Tool?
Real browser-level checks for common VPN leak vectors.
Real WebRTC Check
Uses the actual WebRTC API to detect exposed IPs.
IPv4/IPv6 Compare
Flags mismatches many VPNs fail to tunnel correctly.
Transparent Method
We explain exactly what is and isn't tested, and why.
Instant Results
Get a full report in just a few seconds.
Privacy Focused
No data is logged or stored by this tool.
100% Free
No sign-up, no limits, completely free to use.
Frequently Asked Questions
Everything about IP/DNS leaks and this tool's methodology.
WebRTC is a browser technology for real-time communication that can reveal your real public IP address via STUN server requests, even when a VPN is active, if the browser or VPN doesn't properly block this behavior.
A true DNS leak test requires a backend server that generates unique subdomains per test and logs which DNS resolvers query them — infrastructure a static browser-based tool cannot replicate. This tool focuses on the leak types that are genuinely verifiable from within the browser itself.
Many VPN applications only route IPv4 traffic through their encrypted tunnel, leaving IPv6 traffic to travel over your normal ISP connection unless "IPv6 leak protection" is explicitly enabled in your VPN settings.
Use a VPN that explicitly blocks WebRTC leaks, install a browser extension that disables WebRTC, or adjust your browser's WebRTC IP handling policy in its privacy settings (available in Chrome and Firefox).
Modern browsers mask local network IPs behind random ".local" hostnames by default, reducing (but not eliminating) WebRTC exposure. The public IP revealed via STUN servers can still leak regardless of this protection, which is what this tool specifically checks.
Not necessarily — passing these checks rules out the most common WebRTC and IPv6 leak vectors, but a comprehensive audit would also include a dedicated DNS resolver leak test and a review of your VPN's kill-switch behavior.
DNS Leak Test: How to Check If Your VPN Is Actually Hiding Your IP
Turning on a VPN feels like flipping a privacy switch — but a VPN can be active and still leak your real identity to the sites you visit. This isn't a rare edge case; it's a well-documented weakness in how browsers and some VPN apps handle two specific things: WebRTC connections and IPv6 traffic.
A leak test checks for exactly that. Rather than just trusting that your VPN is working, you can verify it directly from the browser and see, in plain terms, whether your real public IP address is showing through the tunnel.
What "DNS Leak" Actually Means (And Why the Name Is a Bit Misleading)
The term "DNS leak" gets used loosely to describe several different privacy failures, but they're not all the same thing:
A true DNS resolver leak happens when your device sends DNS lookup requests (the process of turning a website name into an IP address) outside the VPN tunnel, straight to your regular internet provider's DNS servers — even while the VPN is technically connected.
A WebRTC leak is a different mechanism entirely. WebRTC is a browser technology built for real-time video and audio calls, and it can reveal your real public IP address through STUN server requests, bypassing the VPN tunnel completely, even if DNS itself is fine.
An IPv6 leak happens when a VPN only routes IPv4 traffic through its encrypted tunnel and leaves IPv6 traffic to travel over your normal, unprotected connection — which is common because IPv6 support lags behind IPv4 in a lot of VPN software.
Why a Browser-Based Tool Focuses on WebRTC and IPv6, Not Classic DNS Leaks
A complete DNS resolver leak test technically requires dedicated backend infrastructure — a server that generates a unique subdomain for each test and logs exactly which DNS resolver ends up querying it. That's not something a static, browser-only tool can replicate.
What a browser-based tool can do reliably is use the actual WebRTC API to gather every IP candidate your browser is willing to expose, and separately fetch your public IPv4 and IPv6 addresses directly. These are genuine, common leak vectors — just measured through a different, verifiable method than a full DNS resolver audit.
How to Read Your Results
If your WebRTC public IP matches your primary detected IP: that's the expected, safe outcome — it means WebRTC isn't exposing a separate, real identity behind your VPN.
If your WebRTC public IP is different from your primary IP: this is the sign of an actual leak. It usually means your browser is pulling your real ISP-assigned IP through a STUN request while the rest of your traffic goes through the VPN — which defeats the purpose of using one.
If a public IPv6 address shows up while a VPN is active: check whether your VPN app has an IPv6 leak protection setting. Many VPN clients only tunnel IPv4 by default, silently leaving IPv6 requests to travel over your normal connection.
If no WebRTC candidates appear at all: that's actually a good sign for privacy — it usually means your browser or VPN is already blocking WebRTC's IP-gathering behavior before it can run.
Fixing a Leak Once You Find One
If the test flags a WebRTC leak, a few options actually fix it rather than just hiding the symptom:
Switch to a VPN provider that explicitly advertises WebRTC leak blocking as a built-in feature, rather than assuming all VPNs handle this by default. Alternatively, install a browser extension built specifically to disable WebRTC's IP-gathering behavior. Chrome and Firefox also both expose a WebRTC IP handling policy setting directly in their privacy preferences, which can be tightened manually without installing anything extra.
For an IPv6 leak specifically, look for an "IPv6 leak protection" or "block IPv6 traffic" toggle inside your VPN app's settings — this is a common option that's simply switched off by default in many clients. It's also worth running an internet speed test before and after connecting, since a VPN with poor performance is often the same one skimping on leak protection too.
One Leak Test Isn't a Full Privacy Audit
Passing a WebRTC and IPv6 check rules out two of the most common leak vectors, but it isn't proof that a VPN is airtight in every scenario. A more complete review would also include a dedicated DNS resolver leak test through infrastructure built for that purpose, and a check of your VPN's kill-switch behavior — whether your internet connection actually drops if the VPN connection itself fails unexpectedly.
It's also worth pairing a leak test with a straightforward check of what your connection is showing publicly right now. The My IP Address Checker shows your current public IP, location, and ISP in one place — useful for confirming your VPN's IP is actually what's being shown to the outside world, not your ISP's.
Frequently Asked Questions
Should I run this test before or after connecting my VPN?
Run it once with the VPN off to see your baseline real IP, then again with the VPN connected. Comparing the two results makes it immediately obvious whether the VPN is actually changing what's publicly visible, rather than just checking the connected result in isolation.
Does using a different browser change the leak test result?
Yes, potentially. WebRTC IP handling policies and default privacy protections vary by browser, so a leak that shows up in one browser might not appear in another, even with the same VPN active on the same device — worth testing your specific everyday browser rather than a different one.
Can a mobile VPN app leak the same way as a desktop one?
Mobile browsers and apps implement WebRTC and IPv6 handling differently from desktop browsers, so leak behavior isn't automatically identical across devices — it's worth testing on each device and browser combination you actually use with the VPN, rather than assuming a desktop result applies to mobile.
Is a leak always the VPN's fault?
Not necessarily — some leaks stem from browser-level WebRTC behavior or OS-level IPv6 settings that a VPN doesn't fully control unless it specifically builds protection for them. That's why enabling any built-in leak protection settings in your VPN app, alongside browser-level fixes, gives the most complete protection.
Want to check more about your connection? Try the My IP Address Checker for full location and ISP details, run an Open Port Checker or DNS Lookup Tool for deeper network diagnostics, or use the Domain Age Checker and Page Speed Checker to research other sites' technical details.
