IP Address & Network Check
See the public IP used for this browser request. Check before and after connecting to a route to see whether it changes. Results don’t reflect the connection status of every app on your device.
Current connection details
Lookup via this site- Public IP address
- Temporarily unavailable
- Country / region
- Temporarily unavailable
- Internet service provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
No lookup results yet.
Only information returned by the lookup is shown. Missing fields are marked “Temporarily unavailable”; location and proxy status aren’t inferred.
What this information means
Distinguish your public IP, its registered location, and your connection method before deciding whether to change routes.
Your public IP is the request’s source address
This is the public address seen by this site, not your device’s local network address. If your browser uses a proxy, it will usually show the proxy’s exit IP. If your browser is set to connect directly, it may still show your local network’s public IP.
Location and ISP are estimates
Location comes from an IP address database, not device location services. The ISP field may identify an internet provider, data center, or address holder. Database updates vary, so this information doesn’t prove a device’s physical location or access to a particular platform.
Proxy detection doesn’t confirm your connection
Detection depends on how the lookup classifies an IP address. “No proxy detected” doesn’t mean you aren’t using one, and “Proxy detected” doesn’t mean your connection has a problem. If the lookup doesn’t return a clear status, this page won’t treat that as “No proxy detected.”
DNS Leak Check
An IP lookup isn’t a DNS leak test. This page doesn’t collect DNS resolver addresses or report a “pass.”
-
Check your client’s DNS settings
Check the DNS mode and routing rules in your client settings. Confirm that domains meant to use the proxy are resolved through the expected route. A client showing “Connected” doesn’t mean DNS queries use the same route.
-
Check your browser and system settings
Your browser’s Secure DNS, your system’s encrypted DNS, or other networking software may use different resolution paths. Check your client’s documentation to confirm these settings work together. Avoid changing several settings at once, so you can identify the cause if a problem occurs.
-
Consider the resolution results in context
To verify which resolver is actually being used, choose a dedicated test tool that displays resolver details and read its privacy policy first. A resolver’s location being different from your exit location doesn’t by itself indicate a leak. Consider your expected configuration, the resolver’s ownership, and the domain’s resolution path together.
-
Check again after making changes
After changing settings, refresh the connection or clear the DNS cache as directed by your client and browser documentation, then compare the results. If the issue persists, submit a support ticket through the user panel. Include the platform, client settings, and what you’re seeing; don’t send your password or full subscription URL.