VPN Leak Test
This test checks whether your VPN connection is leaking your real identity. If the IP address shown below belongs to your real ISP rather than your VPN provider, your VPN is not working correctly. Use the results to verify your privacy setup before browsing or accessing sensitive services.
216.73.217.61
⚠ No VPN Detected
⚠ No VPN was detected. Your real ISP IP is visible. If you believe your VPN is active, it may not be connected, your VPN client may have crashed (kill-switch may not be active), or this provider may not yet appear in our detection database.
IP Leak Test
| Check | Detected Value | Status |
|---|---|---|
| Public IP Address | 216.73.217.61 |
⚠ ISP IP |
| ISP | Amazon.com | ✓ Privacy provider |
| Country | United States | ⓘ Informational |
| VPN / Proxy Detected | No | ⚠ Fail |
| WebRTC Leak | Checking… | ⌛ Checking… |
| DNS Leak | DNS server matches VPN provider | ✓ Pass |
Full Connection Details
| Detected IP | 216.73.217.61 |
|---|---|
| Country | United States |
| Region | Ohio |
| City | Columbus |
| Time Zone | America/New_York |
| ISP | Amazon.com |
|---|---|
| Organization | Anthropic, PBC |
| ASN | AS16509 |
| Hosting IP | Yes |
| VPN Detected | No |
ⓘ IP and WebRTC checks run in your browser. DNS leak detection requires custom DNS infrastructure - See the note in the "How to Fix" section.
Save results & track changes over time
Free account — Save unlimited lookups, build your IP history, and get instant access to all 25+ tools with no limits.
- Save lookup history
- No rate limits
- Free forever
How to Fix a VPN Leak
If this test shows your real ISP IP instead of your VPN provider's IP, follow these steps to diagnose and fix the issue:
- Verify the VPN is connected - Check your VPN client. It should show a green/active status. Reconnect if disconnected.
- Enable the kill switch - A kill switch blocks all internet traffic if the VPN drops. Enable it in your VPN app's settings.
- Change VPN protocol - Try switching from OpenVPN UDP to TCP, or use WireGuard if available. Some protocols are blocked by certain networks.
- Check for DNS leaks - Go to your VPN settings and enable "DNS leak protection" or "Prevent IPv6 leaks" if those options exist.
- Disable WebRTC in your browser - In Firefox: about:config → media.peerconnection.enabled → false. In Chrome: install a WebRTC control extension.
- Try a different VPN server - Some servers may be overloaded or blocked. Switch to a different location in the same country.
- Update your VPN client - Outdated VPN apps may have bugs that cause split-tunneling or routing leaks.
- Consider a different VPN provider - If leaks persist, evaluate providers with audited no-log policies and leak-proof clients.
Types of VPN Leaks
| Leak Type | What Leaks | How to Test |
|---|---|---|
| IP Leak | Your real public IP address is visible despite VPN being active. | This page - Compare detected IP to your VPN's assigned IP. |
| DNS Leak | DNS queries go to your ISP's DNS servers instead of the VPN's. | Visit a DNS leak test site; check if your ISP's DNS server appears. |
| WebRTC Leak | Your browser reveals your real local or public IP via the WebRTC API. | Check browser developer console or use a WebRTC leak test extension. |
| IPv6 Leak | IPv6 traffic bypasses the VPN tunnel and exposes your real IPv6 address. | Enable IPv6 leak protection or disable IPv6 in your OS network settings. |