Public IP and Location Lookup

What These Results Mean

Public IP: the address your request exits from

This is the source address seen by our lookup interface—not your device’s address on your local network. It may change when you connect to an accelerated route. However, routing rules, browser settings, and client mode can affect how requests to our site are routed. The address shown here may not represent the route used by all your apps.

Country, region, and ISP: information from IP address databases

Location comes from an IP address database; it isn’t your device’s real-time location. Database updates, address assignments, and route exits can all affect the result. The ISP is the provider identified by the database. It may be the data center network at the route exit, rather than your local internet provider.

Proxy detection: an indicator, not a verdict on your connection

This page shows “Proxy detected” or “No proxy detected” only when the interface explicitly returns proxy detection information. “No proxy detected” doesn’t mean your client isn’t connected, and “Proxy detected” doesn’t confirm whether your encryption settings are correct. If the field is missing, the result shows “Temporarily unavailable”; it isn’t inferred from your IP or location.

DNS leak check

DNS translates domain names into network addresses. A changed public IP doesn’t mean DNS requests follow the same route. This page only looks up IP location information; it doesn’t list DNS resolvers or run an automatic DNS leak test.

1. Check your client’s DNS settings. See whether the client’s DNS handling option is enabled, and confirm it matches your current connection mode. Don’t rely on the connection toggle alone to determine how DNS traffic is routed.
2. Check your system and browser settings. Secure DNS in your browser, custom DNS services, and system DNS settings may all be active. Note your current settings, then check each one against your client’s instructions. Changing several settings at once can make it harder to find the cause.
3. Distinguish DNS resolvers from traffic routes. If you use a separate DNS testing tool, interpret its results alongside client logs and routing rules. A resolver’s location alone doesn’t prove there’s a leak, and identifying a DNS provider doesn’t confirm the route your traffic took.
4. Check again after switching networks. Recheck your public IP and DNS settings after changing networks or client mode. If you still can’t confirm what’s happening, submit a question through the user panel.

For help, provide your client platform, connection mode, and the steps you took when the issue occurred. Before opening a support ticket, remove subscription links, passwords, and other account credentials from any screenshots.