IP Lookup & Location Check

What These Details Mean

Public IP: A Snapshot of This Request

The public IP shown is the address our endpoint sees when your browser sends a request. It is not your device’s local network address. If your client uses split tunneling, this lookup may go through your local network while international websites use a proxy route. So an unchanged IP here does not necessarily mean your client is disconnected.

To compare results, note your IP before connecting, connect to your chosen route, then select “Run Lookup Again.” Also check which client rule matches requests to this site. If you switch modes to troubleshoot, restore your usual settings afterward.

Location & ISP: Useful for Cross-Checking

IP geolocation comes from databases and may differ from a data center’s actual location or the route name shown in your client. The ISP usually refers to the network associated with the exit IP; it may show the data center operator rather than the provider your device is currently connected through. Database delays and IP address transfers can also affect the result.

Proxy Detection: Not a Connection Verdict

“Proxy detected” means the endpoint has flagged this exit as a proxy. “No proxy detected” only means it wasn’t identified by this lookup; it doesn’t prove the request went directly to its destination. If the endpoint doesn’t return this field, this page shows “Temporarily unavailable” rather than treating missing data as a negative result. This flag also can’t tell you whether a streaming service or AI tool allows access.

Check for DNS leaks

DNS translates domain names into IP addresses. If a domain you expect to route through a proxy is still sent to your local network’s resolver, the resolution path may not match your intended setup. An IP lookup alone can’t confirm a DNS leak, and this page does not run an automatic DNS leak test.

1. Confirm your intended setup. Check whether your client uses rule-based routing or a global proxy, and which domains should be resolved through the proxy. Using local DNS for local domains isn’t necessarily a configuration error.
2. Check your client’s DNS settings. Review whether remote DNS, DNS interception, and routing rules are enabled, and check for any direct-connection exceptions. Refer to your client’s current interface and dashboard documentation for the exact options.
3. Check your browser settings. Secure DNS in your browser may differ from your system or client settings. Note the current settings, then follow your client’s guidance. Avoid changing several options at once, so you can identify what caused any difference.
4. Test with the actual domain. Use your client’s connection logs or DNS diagnostics, if available, to check which resolver and outbound route are used for the domain you’re testing. The default DNS address shown by your system is only a clue; on its own, it can’t prove how a lookup was handled.
5. Refresh and check again. After changing settings, clear the DNS cache as instructed by your client, then reopen the page you’re testing. If the issue persists, keep a redacted copy of the error and use the dashboard support ticket to share your client, selected location, and steps to reproduce the issue.

A difference between the resolver’s displayed location and your exit location does not, by itself, prove a leak; public DNS services may process requests across regions. Check your client settings and DNS logs against your intended routing rules.

Lookup Privacy & Error Messages

We don’t log lookups. They run through an endpoint on this site, and this page doesn’t save results to your browser’s local storage. “Copy Public IP” writes the current address to your clipboard only when clicked. IP and network provider details can reveal information about your connection, so hide anything you don’t want to share before posting a screenshot.

If you see “Temporarily unavailable,” check your connection and select “Run Lookup Again” later. If the endpoint is unavailable or a field is missing, this page will show a clear notice. It won’t generate a substitute result or switch to a third-party public endpoint.

For details, see our Privacy Policy. For help setting up a client, see the setup guide. Find client downloads in the user dashboard.