R9 / IP Details

My IP Address

See the address your browser currently uses to reach the internet. After connecting or switching routes, run the lookup again to compare the results.

Current IP Details

Lookup via our API

Enable JavaScript to check your current IP details.

Public IP Address
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

This result reflects the route used for this page request only; it doesn’t show how every app on your device connects.

What this information tells you

A changed address can help you check your connection, but it doesn’t provide a complete picture of your privacy.

Public IP: the address websites see

This is the public IP address our site detected for this request, not your device’s address on the local network. Check once before connecting, then connect to the route you want to test and check again to see whether the address changed. If your browser uses a direct-connection rule, this page may still show the original IP even when the client is connected.

Location and ISP: information from IP databases

Country, region, and ISP information comes from IP address databases and may not be up to date. The ISP shown may be the network operator for the route’s exit point, not your local broadband provider. IP geolocation can’t establish your device’s actual location and may not match the region a content platform assigns to you.

Proxy detection: an indicator, not a verdict

Proxy detection relies on information returned by the API. A detected proxy doesn’t mean your connection is faulty, and no proxy detected doesn’t mean all your traffic is going direct. If the API doesn’t provide this field, this page will show “Temporarily unavailable” rather than infer a result from a change in address.

How to check for DNS leaks

Checking your public IP and testing DNS are separate tasks. This page won’t automatically tell you that your DNS is leak-free.

DNS translates domain names into network addresses. Web traffic and DNS requests may take different routes. Even if your public IP has changed, that alone doesn’t tell you whether DNS requests are following the same route.

  1. Check your client’s DNS settings. See whether the client is set to handle DNS, and check whether it’s in global or rule-based mode. Depending on the mode, some DNS requests may be routed through your local network.
  2. Check your browser’s Secure DNS settings. The DNS service selected in your browser may differ from your system or client settings. Note the current setting and check whether requests follow the intended route. Don’t rely on the setting’s name alone to determine whether DNS is leaking.
  3. Compare the resolver with the expected route. If you use a trusted, dedicated DNS leak test, check whether the detected DNS provider matches your configuration. A difference between the resolver’s location and your IP’s location doesn’t necessarily indicate a leak. Consider your routing rules and how the DNS service is deployed.
  4. Test again after making changes. Reconnect and refresh the test. If needed, clear your system or browser DNS cache. If the results don’t match your settings, note your client mode, DNS settings, and symptoms, then troubleshoot in the Help Center.

For connection and routing issues, visit the Help Center. For client setup instructions, see our getting started guides.

Query Privacy

We don’t log queries. Lookups use our own API; this page doesn’t connect to third-party public IP lookup services or store lookup history in your browser.

If the API is unavailable, we’ll show “Temporarily unavailable” rather than substitute a sample address. When you copy an address, it goes to your device’s clipboard. Before sharing a screenshot or troubleshooting details, check that they don’t include network information you’d rather keep private.

Read our Privacy Policy