IP Lookup and Connection Check

What This Information Means

Public IP: the address seen by websites

The public IP shown here is the source address seen by this site’s lookup endpoint. Check it before connecting to a route, then check again after connecting to compare the addresses. If it hasn’t changed, first confirm that your client is connected and that your browser isn’t set to connect directly by a routing rule. An unchanged address alone doesn’t prove the client is malfunctioning.

Location and ISP: network details, not precise location

Country, region, and ISP information comes from IP address databases, which may not be up to date. The ISP shown may be the operator of a data center or network egress point, rather than your local broadband provider. The displayed region isn’t your device’s precise location and doesn’t guarantee that a website will serve content for that region.

Proxy detection: an indicator, not a security verdict

The page displays “Proxy detected” or “No proxy detected” only when the lookup endpoint explicitly returns a proxy flag. If that field isn’t returned, the page shows “Temporarily unavailable.” No flag doesn’t prove that you aren’t using a proxy, and a detected flag doesn’t mean your connection is unsafe.

Read the guide to checking your public IP, DNS, and individual apps →

How to Check for DNS Leaks

DNS translates domain names into network addresses. Routing webpage requests through a selected route doesn’t mean DNS queries use the same path. This IP lookup doesn’t run a dedicated DNS leak test, so it won’t report that “DNS passed.”

1. Check your client’s DNS settings. See whether the client handles DNS resolution, and review the documentation for your current mode. System proxy, tunnel mode, and split-routing configurations may use different DNS paths; the connection icon alone doesn’t tell you which one is in use.
2. Check your browser’s Secure DNS settings. Your browser may use its own encrypted DNS settings. Confirm that they follow your intended routing rules. If you’re unsure, keep the current settings, note the configuration, and consult your client’s documentation before making changes.
3. Check your system and other networking tools. Look for other proxies, virtual network tools, or custom DNS settings running at the same time. Change one setting at a time, then reconnect and check again to avoid conflicting changes.
4. Use a dedicated test when you need a definitive result. A dedicated DNS test triggers domain lookups and observes where the requests come from. Compare the DNS provider shown in the results with your expected configuration; a resolver in a different region alone doesn’t prove a leak. Review an external test’s privacy policy before using it. This page doesn’t call these services automatically.

If you’re having connection issues, start with the Quick Start Guide to review the import and connection steps. If you still need help, use the support ticket portal and include your platform, client mode, and the app affected. Don’t share your password or full subscription link.

Lookup Privacy and Error Messages

We don’t log lookups. This tool sends requests only to an endpoint on this site, doesn’t save lookup results in your browser’s local storage, and won’t switch to a third-party public endpoint if a request fails. Copying your public IP requires clicking the button; only the IP address is copied.

If “Temporarily unavailable” appears, the network may be unreachable, the endpoint may not be responding, or the returned data may be incomplete. This doesn’t mean your route is disconnected. Check your connection and try again. If only some fields are missing, use the available information and don’t treat blank fields as a negative result.

Before sharing a screenshot, consider hiding any IP address or network details you don’t want to make public. See our Privacy Policy for information about how we handle privacy.