Public IP Address Lookup

What This Information Means

Exit Address, Not Your Device Address

The public IP address shown here is the source address seen by this site's endpoint. Devices on a home network may share an exit address, and a network acceleration route may show its own exit address. This is not your device's local network address and does not, by itself, reveal your device's physical location.

Location and ISP Are Database Labels

Country and region are usually based on IP geolocation databases, so they may differ from expectations if an address has been reassigned or a database update is delayed. The ISP field may identify a network operator, data center, or organization associated with the exit network—not necessarily your local broadband provider. Missing fields appear as “Temporarily unavailable”; they are not filled in using a route name.

Proxy Detection Is Not a Connection Verdict

The proxy field only shows a detection result explicitly returned by the endpoint. “No proxy detected” does not prove that a request did not pass through a proxy, and “Proxy detected” does not mean the connection is faulty. If the endpoint returns no clear result, this page shows an unknown status rather than treating a missing value as a negative result.

Browsers and other apps may follow different rules, and IPv4 and IPv6 may use different routes. This page shows the address used by the request; it does not test every network protocol. If you need to change routes, see the getting started guide and global node guide.

DNS leakcheck

DNS translates domain names into network addresses. A changed exit IP does not automatically mean DNS queries are using the expected route. This page looks up your exit address; it does not run an active DNS leak test or label a result “passed” based on IP geolocation.

1. Check your client's DNS settings. Make sure the DNS handling method matches your current connection mode, and note the differences between system proxy mode and virtual network interface mode. Refer to the settings shown in your client.
2. Check your browser's Secure DNS settings. Browser-configured encrypted DNS may use a different route from the system resolver. Confirm that its settings match your expectations. If you're unsure, note the original settings and troubleshoot using the client guide; avoid changing several options at once.
3. Verify the DNS resolution route. Use your system's network diagnostics or client logs to check the resolver and which rules were applied. Assess the resolver address, connection route, and exit address together; a DNS provider name or country label alone does not prove a leak.
4. Retest under the same conditions. After changing routes, wait for existing connections to close, clear the DNS cache as directed by your operating system, and reopen the app you're checking. If the issue persists, send a support ticket through the dashboard with your client mode, relevant settings, and redacted error details.

DNS sent over an encrypted connection and DNS sent over the expected route are separate issues. The first concerns how DNS traffic is protected; the second concerns its routing. Do not treat them as a single setting.

When you open a support ticket in the dashboard, hide account credentials, subscription links, and unrelated browsing records.