What these results mean
Public IP: the address seen by the website
The public IP shown here is the source address seen by our lookup API, not your device’s local network address. Home networks, mobile networks, and subscription routes may use different public IPs. Devices sharing a public IP may show the same address.
To check whether a route is active, note the results before connecting, then connect to the route and select “Check again.” With per-app or per-site routing, your browser’s path to this site may differ from the path used by other apps. If the address hasn’t changed, first check whether this request uses the selected route rather than assuming the entire client has stopped working.
Location and ISP: classifications from IP databases
IP databases estimate location, which may differ from the device’s actual location, the route name, or the server’s physical location. The ISP field may show an internet provider, hosting company, or organization associated with the network your traffic exits through; it won’t necessarily show VPN73. Use these details as clues, not as a precise way to locate a device.
Proxy detection: not proof of connection status
“Proxy detected” means the API classified this public IP as a proxy. “No proxy detected” doesn’t prove that your request didn’t use a proxy, nor does it indicate whether encryption is enabled. If the API returns no clear result, this page shows “Temporarily unavailable” rather than treating missing data as a negative result.
DNS Leak Check
DNS translates domain names into IP addresses. Seeing the expected public IP for a web request doesn’t mean DNS queries used the same route. Checking your public IP and testing for DNS leaks are separate checks; the results on this page can’t replace a DNS leak test.
- Confirm the intended route. Start by checking your client’s routing rules, DNS settings, and active route. Identify which apps and domains should use the subscription route. Domains deliberately set to connect directly shouldn’t be mistaken for unexpected routing.
- Check your system and browser settings. Review your system’s DNS configuration and see whether your browser has Secure DNS enabled separately. Browser-specific settings can change the DNS resolution path, so check your client’s documentation too.
- Test in your actual setup. To identify the resolvers in use, choose a dedicated test tool that shows resolver details, and read its privacy policy first. You can also review client diagnostic logs; redact subscription addresses and account details before sharing them.
- Distinguish unexpected routing from intentional routing. A resolver name or location that differs from your public IP doesn’t, by itself, prove a leak. Check domain rules, resolver ownership, and client settings together, then test again after making changes.
Privacy and lookup scope
We don’t log queries. This page retrieves the public IP details for your current request through an API on our own domain; it doesn’t fall back to third-party public lookup APIs. If the API is unavailable or returns no valid address, you’ll see “Temporarily unavailable” and can try again manually later.
The Copy button writes the current public IP to your clipboard only when clicked. A public IP may reveal information about your network location, so consider redacting it before sharing a screenshot. See our Privacy Policy for details.