Network Tools / Current Public IP
See the public IP address and location details used for this request. After switching routes, check again to see whether your browser’s public IP has changed.
Waiting for results. Select “Check again” to view your current IP details.
These results apply only to the connection your browser used to reach this site. They may not reflect the network path used by other apps and can’t, on their own, determine whether your connection is secure.
Understanding the Results
Start with the public IP, then check its location and ISP. These details can help troubleshoot your connection path, but they aren’t identity verification or a complete privacy check.
With an accelerated connection enabled, your browser may reach this site through the selected route. With split tunneling, this site may still use your regular network. If the address hasn’t changed, check your client’s connection status and routing rules, then run the lookup again. Don’t assume the route has failed based on this page alone.
Country and region are based on IP geolocation data. The ISP field identifies a network provider or organization associated with the address in the database; it doesn’t pinpoint your device. Database updates can lag, and the registered location, actual exit point and service provider may differ. For access to a specific site, rely on the result reported by that site.
The proxy field shows only the result explicitly returned by the lookup service. No proxy detected doesn’t mean you aren’t using an accelerated connection, and a proxy detected result doesn’t mean your device has a problem. If the service provides no result, this page shows “Temporarily unavailable” rather than inferring proxy status from the IP location.
Check for DNS Leaks
DNS translates domain names into network addresses. Web traffic and DNS requests may take different routes, so a changed public IP alone doesn’t prove that DNS is using the selected connection as expected. This page’s GeoIP lookup doesn’t collect DNS resolver details or automatically test for DNS leaks.
Check whether your client handles system DNS and how its current rules route DNS requests. Settings may have different names across platforms, so consult your client’s documentation. Avoid enabling network configurations that conflict with each other.
Your browser may use its own encrypted DNS instead of the system resolver. Note the current setting and compare it with your client’s documentation. A resolver in another region isn’t necessarily a leak; what matters is whether the DNS route matches your expectations.
For further verification, choose a trusted DNS testing tool and compare resolver locations before and after connecting, taking your routing rules into account. This page won’t automatically send requests to third-party testing sites. If anything is still unclear, submit a support ticket through the user dashboard with your platform, client settings and a description of the issue.