Egress IP and location
After connecting to an international route, refresh the lookup to check for a change in your egress IP. Results show the network path used by this browser request; other apps may use a different route.
Current lookup results
Same-origin API lookup- Egress IP
- Temporarily unavailable
- Country / region
- Temporarily unavailable
- Network operator / ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
No results yet. The lookup runs automatically when the page loads, or you can refresh it manually.
Understanding the results
Egress IP: the address websites see
The egress IP is the public address shown when this lookup request reaches the API. Run the lookup before and after connecting to see whether your browser's egress IP changes. If your client uses split routing, this page may use your local network while requests to the service you want to access use an international route. If so, check your client rules and the service's response as well.
Location and ISP: information from IP databases
The country, region, and provider are based on IP address data returned by the API; they do not indicate your device's physical location. IP assignments, database updates, and route changes can all affect the results. The provider may appear as a data center or network provider rather than your local broadband company. Use location as one factor when choosing a route, not as the sole way to determine whether a website will be accessible.
Proxy detection: an indicator, not a connection test
This page displays “Detected” or “Not detected” only when the API returns an explicit result. If the field is missing, it shows “Temporarily unavailable.” The indicator does not tell you whether your connection is encrypted and is not a substitute for your client's connection status. “Not detected” does not mean your request did not use an international route, and “Detected” does not mean the destination website will necessarily block access.
Check for DNS leaks
This page checks your egress IP; it does not test for DNS leaks. An expected IP location does not prove that DNS requests use the same route.
DNS translates domain names into network addresses. If your browser or system sends DNS requests to a resolver outside the expected path, the DNS route may differ from the route used to access a website. A resolver's location—local or overseas—does not by itself indicate a leak. What matters is whether the actual path matches your client configuration.
- Check your client’s DNS settings. Confirm whether the current mode handles DNS requests from your system or apps, and whether you have any domain-based DNS routing rules. Settings vary across platforms, so refer to your client’s current interface.
- Check your browser’s Secure DNS settings. A DNS resolver configured directly in your browser may differ from your system settings. Note the original setting before changing it so you can restore it after troubleshooting.
- Check the actual DNS route after connecting. Use your client’s connection logs or your system’s network diagnostics to verify the destination and route of DNS requests. If encrypted DNS is enabled, check that it uses the expected route as well.
- Verify your egress IP and DNS route separately. Refresh this page to check your egress IP, then compare it with your DNS route records. Investigate browser caching, routing rules, and app-specific settings separately.
If your egress IP has changed but a service still won't load, check DNS resolution, your client’s routing rules, and the service’s regional requirements first. Avoid switching routes repeatedly based only on an IP lookup. See the user manual for the full connection process, or start with the getting started guide if you're setting things up for the first time.
Privacy notice
We do not log lookups. To return results, our same-origin API needs to read the egress IP for your request. This page does not save lookup results in your browser's local storage or send requests to third-party public lookup services.
“Copy egress IP” copies the address to your clipboard. Before sharing the address or a screenshot, make sure it is necessary for troubleshooting and avoid posting it publicly. If the API is unavailable, this page will not guess your egress IP or fill in results from another source.
Read our Privacy Policy →