VPN Connection Check
Instantly verify your VPN is working correctly. Checks your IP, IPv6 exposure, WebRTC leaks, and DNS servers — all at once.
Checking your connection…
Running IPv4, IPv6, WebRTC, and DNS checks simultaneously.
Public IP
Detecting…
ISP / Network
Detecting…
Location
Detecting…
Timezone
Detecting…
Security Checks
Quick Answer
The VPN Connection Check runs four tests at once: your public IPv4 (should show VPN server IP), IPv6 exposure (should be blocked), WebRTC leak detection (real IP must not appear), and DNS server detection (should show VPN DNS, not ISP DNS). All four must pass for full protection.
- • Most VPNs fail IPv6 — check even if you think you're protected
- • WebRTC bypasses VPN at the browser level — requires app-level blocking
- • A 'protected' result means no technical leaks — not full anonymity
- • Run this check every time you switch networks or VPN servers
Is Your VPN Actually Protecting You?
Many VPN users assume that connecting to a VPN is enough to stay private — but VPN leaks are more common than you think. WebRTC leaks, IPv6 exposure, and misconfigured DNS can all expose your real identity even while connected to a VPN.
This tool runs four independent checks simultaneously and shows you exactly what a website sees when you connect: your public IP, whether IPv6 is reachable, whether WebRTC exposes your local IP, and which DNS servers handle your queries.
Understanding the Four Checks
Public IPv4 Address
The most basic check. When you connect to a VPN, your public IPv4 address should change to the VPN server's IP, not your home or office IP. The ISP / Network field reveals who owns the IP — a VPN provider or datacenter is a good sign.
IPv6 Leak Detection
IPv6 is the next-generation internet protocol and is active on most modern networks. Many VPNs only tunnel IPv4 traffic and leave IPv6 completely unprotected. If your device has an IPv6 address and the VPN doesn't block it, every site you visit can log your real IPv6 — making your IPv4 protection useless.
WebRTC Leak Detection
WebRTC is built into Chrome, Firefox, Safari, and Edge for real-time communication. It bypasses your network stack and can use STUN servers to discover your real IP address and local network IPs — even when connected to a VPN. Browser extensions or in-app WebRTC blocking are the only reliable fixes.
DNS Server Detection
Every domain you visit requires a DNS lookup. If those lookups go to your ISP's servers instead of your VPN's servers, your ISP sees every website you visit — even if your traffic is encrypted. This check probes three resolvers to see which IP they receive your query from. Matching IPs indicate your DNS is tunneled correctly.
Fix VPN Leaks with LimeVPN
LimeVPN includes WebRTC leak protection, IPv6 blocking, private DNS, and a kill switch on all plans. Starting at $5.99/mo.
Get LimeVPN — From $5.99/moAES-256 Encryption · No-Logs Policy · 30+ Locations · Kill Switch
Frequently Asked Questions
What does the VPN connection check test? ▼
What is a WebRTC leak? ▼
Why does IPv6 matter for VPN privacy? ▼
What does "DNS server detected" mean? ▼
Why do I see multiple IP addresses in the DNS section? ▼
My connection shows "protected" — does that mean I'm 100% anonymous? ▼
More Privacy Tools
What Is My IP
See your public IP address, location, and ISP in real time.
DNS Leak Test
Check if your VPN is leaking DNS queries to your ISP.
IP & WebRTC Leak Test
Full technical leak test — IPv4, IPv6, WebRTC ICE candidates, and DNS.
Browser Fingerprint Test
See how trackable your browser is without cookies.