IP Check

What This Information Means

Public IP: Where This Request Came From

The public IP is the source address seen by our API, not your device’s address on your local network. If your browser traffic goes through a selected route after you connect a client, the public IP will usually change. Note the result before connecting, then connect to your chosen route and select “Check Again.” Compare the result with your client’s routing mode and route name.

Location and ISP: Clues About Your Public IP

The country or region is based on an IP geolocation database and may differ from the data center’s actual location. The ISP may identify the data center or network operator behind the public IP, rather than your local internet provider. IP geolocation isn’t device location, and this field alone can’t confirm how a destination website identifies your region.

Proxy Detection: An Indicator, Not a Verdict

“Proxy detected” means the API classified the current public IP as a proxy. “No proxy detected” means only that the API didn’t identify that label for this request; it doesn’t prove the request connected directly. If the API doesn’t return enough information to assess, this page shows “Temporarily unavailable” rather than treating missing data as a negative result.

DNS Leak Check

DNS translates domain names into network addresses. Even if your public IP has changed, DNS queries may still take a different route. The IP check above is not a DNS leak test. This page doesn’t automatically detect DNS resolvers or conclude that there are no leaks.

1. Check your client’s DNS settings. See whether the current configuration handles DNS queries and sends them through the intended route. Routing modes may use different policies, so refer to the settings in your client.
2. Check your browser’s Secure DNS settings. A browser’s built-in encrypted DNS may differ from your system or client configuration. Note its current status and check compatibility with your client’s documentation. Don’t assume that encrypted DNS means queries are going through a proxy.
3. Use DNS logs to verify the route. If your client provides DNS or connection logs, check where queries go and which rules apply when you visit a test domain. If you use a separate DNS testing tool, read its privacy policy first, then compare the resolver’s network with your expected configuration.
4. Run the check again after changing settings. Follow your client’s instructions to clear the DNS cache or reconnect, then revisit the destination service. A difference between the resolver’s region and your public IP’s region is a troubleshooting clue, not proof of a leak.

If your public IP looks right but a service still isn’t working, read the full troubleshooting guide or check common connection issues on the support page.

Query Privacy and Troubleshooting

We don’t log queries. The check runs through an API on this site, and your browser sends it a standard network request so we can identify your public IP. This page doesn’t save query history or store results in your browser, and it doesn’t fall back to a public third-party lookup API.

If the API is unavailable or returns incomplete information, the affected fields show “Temporarily unavailable.” This doesn’t mean your connection is down. Check whether other pages load on your network, then select “Check Again.” If the information is still unavailable, use a support ticket in the dashboard to describe your connection setup and the error message. Before sharing a screenshot, hide any public IP address or account details that aren’t needed.

Copying only copies the current IP; it doesn’t include account details or client settings. For information about how we handle data, see our Privacy Policy.