Check your current public IP

Public IP: The public address our API detects when it receives your request. Check it before and after connecting to see whether your browser's traffic is using a different exit IP. In rule-based mode, different sites may use different routes, so this result does not show the exit IP used by other sites or apps.

Country / region: Based on IP geolocation data, not your device's location. These records may be out of date, and an ISP's registered address may differ from the route's actual exit location. If the location differs from what you expected, check the route selected in your client and how sites actually connect.

ISP: The network provider or hosting network associated with the exit IP. It may not be the broadband provider for your current connection. When using an international route, the result may show the name of a data center or upstream network.

Proxy status: Shows only what the API explicitly reports. A detected proxy does not necessarily mean there is a connection problem, and no proxy detected does not prove your traffic isn't using one. If the API doesn't return this field, this page shows “Temporarily unavailable” rather than assuming “No.”

DNS translates domain names into network addresses. Routing web traffic through your selected route doesn't mean DNS requests use the same path. This IP lookup can't read the complete DNS resolution path, so it can't confirm that you passed a DNS leak test.

1. Check your client's DNS settings. Review the resolution policy for the current mode and confirm that domain names are resolved as described by your client. System proxy mode and modes that route all system traffic may cover different types of traffic.
2. Check your browser's secure DNS settings. Your browser may use its own encrypted DNS configuration. Compare it with your system and client settings so you don't overlook the browser's separate DNS route when changing client settings.
3. Verify with DNS records. If your client provides DNS logs or connection records, check where DNS requests go when you visit a test domain. Hide account details and subscription information before sharing screenshots.
4. Diagnose issues separately. If the exit location is correct but domain names won't resolve, check your DNS settings first. If domains resolve but connections fail, check the route, split-tunneling rules, and the destination service. Don't rely on the public IP alone to determine whether DNS is leaking.

Without DNS records or evidence from a dedicated test, consider the result “Not yet verified.” For help, submit a ticket through the user dashboard and include your operating system, connection mode, and a description of the issue.