Public IP Lookup
See the public IP your browser uses to access this site. After switching routes, run the lookup again to compare.
Lookup Results
Results apply only to this browser's connection to this site, not to the traffic from other apps.
- Current Public IP
- Temporarily unavailable
- Country or region
- Temporarily unavailable
- Internet service provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Understanding the Results
Public IP is the internet-facing address this site sees, not your device's local network address. If it hasn't changed after switching routes, first confirm the connection is active, then check whether your split-tunneling rules are sending this site directly.
Location and ISP information comes from IP databases. The listed location may be where the address is registered, and the ISP may belong to the network hosting the exit point—not necessarily your device's location or your local broadband provider.
Proxy detection indicates whether a database has flagged this address as a proxy. “Not detected” doesn't mean no proxy is in use; “Temporarily unavailable” means no determination could be made.
DNS Leak Check
Before loading a website, your browser typically uses DNS to resolve its domain name to an IP address. Even if web traffic follows the intended route, DNS requests may take a different path. This page checks only the route used by web requests; it doesn't test DNS resolvers.
- First, check your client’s DNS settings to see which resolver the current mode should use. Then check your browser’s Secure DNS settings, which may differ from your system settings.
- Keep your current route and split-tunneling mode unchanged, then use a trusted DNS test to identify the resolvers in use. Choose a test that makes fresh queries for new domain names so cached results aren't mistaken for the current route.
- Compare the results with your expected configuration. If DNS requests should go through the tunnel but you still see your local ISP's resolver, check the client and browser settings, then test again. A resolver's location can differ from your public IP's location; that alone doesn't indicate a leak.