Check My IP

What These Results Mean

Egress IP: Where This Request Came From

The egress IP is the source address our API sees for this request, not your device’s private address on the local network. With VPN27 enabled, the egress will usually change if browser traffic passes through the selected route. It may stay the same if your browser uses a direct-connection rule or keeps using an existing connection.

First, note the result before connecting. Then connect to your chosen route and check again. A changed address can help confirm routing, but doesn’t prove that other apps use the same egress. Command-line tools, IDE extensions, and system apps may each use their own proxy settings.

Country, Region & ISP: Based on IP Geolocation Data

Location and network provider details come from the address data returned by the API. They may be affected by database updates, network reselling, or changes in IP address assignments. The ISP field may show a data center or network operator and may not match the route name. Location isn’t your device’s precise position, nor does it determine the region a service ultimately assigns to you.

Proxy Detection: An Indication, Not a Guarantee

“Proxy detected” means the API identified this address as a proxy-related egress. “No proxy detected” means only that this lookup didn’t flag it; it doesn’t mean your connection isn’t using a proxy. If the API can’t provide a clear result, this page shows “Temporarily unavailable” rather than treating an unknown status as negative.

This page isn’t a comprehensive anonymity or security test. One egress address can’t confirm that DNS, traffic from other apps, or different IP protocols use the same network path.

How to Check for DNS Leaks

DNS translates domain names into addresses that devices can connect to. Routing your browser traffic through a proxy doesn’t automatically route DNS lookups the same way. This page’s API returns egress details only; it doesn’t run DNS leak tests or automatically contact third-party testing services.

1. Check your client settings first. Review the connection mode and DNS settings in your VPN27 client to confirm whether it handles DNS resolution. Settings may be located differently on each platform, so check the client interface you’re using.
2. Check your browser’s Secure DNS settings. Custom encrypted DNS settings in your browser may differ from your system or client settings. Note your current options and check whether DNS requests follow the intended route. Don’t assume there’s a leak—or that there isn’t one—based on a feature’s name alone.
3. Rule out cached DNS and existing connections. After switching routes, close existing browser connections and reopen the test page. If needed, follow your system’s instructions to clear the DNS cache, then check again to avoid mistaking cached results for the current DNS path.
4. Consider resolver results in context. If you choose to use a dedicated DNS test, read its privacy policy first, then compare the resolver’s location with your client settings. A difference between the resolver and egress locations doesn’t necessarily indicate a leak; check whether it matches your routing rules.

If results don’t match your expectations, first check whether your split-tunneling rules, browser proxy, and system proxy are consistent. Then review the connection steps in the Quick Start Guide. Still have questions? Submit a ticket in the user dashboard and include your platform, connection mode, and steps to reproduce the issue.