VPN & Proxy Leak Detector
Test your network for VPN, Proxy, and WebRTC leaks. Our deep scanner detects hidden IP addresses, mismatched timezones, and transparent proxies instantly.
How This VPN Leak Detector Works
Multi-Layer VPN & Proxy Leak Analysis
True anonymity requires passing multiple independent tests simultaneously. Our detector runs four parallel checks to paint a complete picture of your connection's privacy level.
WebRTC Leak Detection
Using the browser's native RTCPeerConnection API, ICE candidates are harvested from Google STUN servers. Any public IP appearing here means your VPN is failing to block WebRTC — a critical leak channel overlooked by many VPNs.
IP Reputation Check
By cross-referencing the visitor's ASN/ISP against a custom list of known cloud and hosting providers (AWS, Azure, GCP, DigitalOcean, OVH, Hetzner, etc.), we detect VPN exit nodes, datacenter IPs, residential proxies, and Tor exit nodes in real-time. Even if your VPN hides your real IP, the exit node IP itself is still flagged.
HTTP Header Fingerprinting
Transparent and anonymous proxies inject headers like X-Forwarded-For, Via, and Proxy-Connection into your HTTP requests. Our server-side scanner detects over 14 proxy header signatures.
Timezone Correlation
Your browser reports your local timezone via the JavaScript Intl API. We compare this to the timezone associated with your IP's geolocation. A mismatch is a strong statistical indicator of location spoofing via VPN.
VPN Leak Detection — FAQ
Quick answers to the most common questions about this tool.
How does this VPN leak detector work?
It runs four parallel checks: WebRTC ICE candidate harvesting, IP/ASN reputation lookup, HTTP proxy-header fingerprinting and a timezone-vs-IP correlation attack. A single failure flags a leak.
What is a WebRTC leak?
WebRTC can expose your real public or local IP through STUN even when a VPN is active, because the protocol bypasses the system proxy. Most major VPNs do not block this by default.
Why is my IP shown as a "datacenter" or "hosting" IP?
Because your VPN exit node lives in a cloud or hosting network (AWS, OVH, Hetzner, etc.). That itself is not bad — it just means the destination site can tell you are using a VPN.
Does this test work behind Tor?
Yes, but Tor exit nodes are flagged separately. WebRTC is disabled in Tor Browser, so that test will report "not supported" — which is the secure outcome.