VPN Leak Test – Check IP & WebRTC

Diagram: Three parallel leak probes on a tunnelled connection: address, resolver, and peer discovery — illustrating vpn leak check
Three parallel leak probes on a tunnelled connection: address, resolver, and peer discovery.

This test checks the public IP used for this request and whether WebRTC exposes a different public address. Compare the result with the address shown by your VPN app or with a baseline taken while the VPN is disconnected.

2600:1f28:365:80b0:40db:92d5:6cb9:abcc
⚠ No VPN Signature Detected
⚠ This address is not identified as a VPN, proxy, or Tor exit in our current data. That does not by itself prove a leak: compare the address and provider below with the server shown in your VPN app.

IP Leak Test

Check Detected Value Status
Public IP Address 2600:1f28:365:80b0:40db:92d5:6cb9:abcc ⚠ ISP IP
ISP Amazon.com, Inc. ✓ Privacy provider
Country United States ⓘ Informational
VPN / Proxy Detected No ⚠ Review
WebRTC Leak JavaScript is required for this check ⓘ Not started
DNS Leak A resolver probe is not available on this site ⓘ Not tested
IPv6 Route 2600:1f28:365:80b0:40db:92d5:6cb9:abcc was used for this request ⓘ IPv6 observed

Full Connection Details

Detected IP2600:1f28:365:80b0:40db:92d5:6cb9:abcc
CountryUnited States
RegionVirginia
CityAshburn
Time ZoneAmerica/New_York
ISPAmazon.com, Inc.
OrganizationAWS EC2 (us-east-1)
ASNAS14618
Hosting IPYes
VPN DetectedNo

ⓘ The IP result comes from this HTTPS request. The WebRTC check runs in your browser and always finishes with a result or an unavailable state. A trustworthy DNS leak test requires a unique authoritative DNS probe, so this page does not infer a DNS result from unrelated IP metadata.

Continue this check

Useful tests to run next

Confirm how the connection is classified Check what remains visible beyond the VPN Scan the exposed public IP for risk signals

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: (New to VPNs? Start with our guide on what a VPN is.)

  1. Verify the VPN is connected - Check your VPN client. It should show a green/active status. Reconnect if disconnected.
  2. Enable the kill switch - A kill switch blocks all internet traffic if the VPN drops. Enable it in your VPN app's settings.
  3. Change VPN protocol - Try switching from OpenVPN UDP to TCP, or use WireGuard if available. Some protocols are blocked by certain networks.
  4. Check for DNS leaks - Go to your VPN settings and enable "DNS leak protection" or "Prevent IPv6 leaks" if those options exist.
  5. Disable WebRTC in your browser - In Firefox: about:config → media.peerconnection.enabled → false. In Chrome: install a WebRTC control extension.
  6. Try a different VPN server - Some servers may be overloaded or blocked. Switch to a different location in the same country.
  7. Update your VPN client - Outdated VPN apps may have bugs that cause split-tunneling or routing leaks.
  8. Consider a different VPN provider - If leaks persist, evaluate providers with audited no-log policies and leak-proof clients.

Types of VPN Leaks

WebRTC leaks are the most common browser-level issue - Our guide explains how WebRTC can leak your IP.

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.

Questions about VPN Leak Check

How do I know if my VPN is leaking?

Connect your VPN, then run the test on this page. Compare the displayed IP and provider with the server shown in your VPN app. If WebRTC reveals a different public address, or the page still shows your disconnected baseline address, the tunnel may be leaking.

What is a DNS leak?

A DNS leak happens when your domain-name queries travel outside the encrypted VPN tunnel and go to the resolvers of your ISP instead of the VPN provider. Your traffic stays encrypted, but the ISP still sees every site name you look up, which defeats much of the privacy benefit. Causes include misconfigured VPN clients, manual DNS settings, and certain smart multi-homed resolution features in Windows.

What is a WebRTC leak and how do I stop it?

WebRTC is a browser technology for real-time calls that can discover your addresses through STUN requests - And it can expose your real public IP even while a VPN is connected. To stop it, use a VPN client or browser extension that blocks WebRTC leaks, disable WebRTC in the browser (in Firefox via media.peerconnection.enabled), then re-run this test to confirm.

Tools related to VPN Leak Check

Technical sources for VPN Leak Check

The technical claims on this page are drawn from the primary specifications and vendor documentation below.

  1. RFC 8445 — Interactive Connectivity Establishment (ICE) RFC Editor
  2. WebRTC API Reference MDN Web Docs