See the public IP, location and ISP currently used by your browser. Proxy detection is based on network signals returned by the API and should only be treated as an additional indication of the current connection state.
The results reflect only the network exit used by the current browser request.
Each field answers a different question. To determine whether the connection is working as expected, consider the public address, location, ISP and proxy signal together.
This is the public address seen by this site’s API when it receives the request. Check it before and after connecting to a route; if it changes, the browser request is using a different network exit. If it stays the same, check the client connection status and routing rules.
The location comes from an IP address database and is not the device’s precise location. Data-center registration addresses, ISP records and the actual network exit may differ, so this field is best used to confirm an approximate region.
This usually identifies the carrier, cloud network or data center associated with the current network exit. After connecting to an accelerated route, the name may change from the local access provider to the network provider used by the route’s exit.
This is an auxiliary signal returned by the API based on network characteristics. Corporate gateways, shared exits and data-center routes can affect the result. When no result is available, this page clearly shows “Temporarily unavailable” rather than making a guess.
Your public IP and the path taken by DNS requests are separate matters. This page’s API returns network-exit information only; an IP lookup alone cannot confirm whether DNS requests are following the expected route.
Temporarily disconnect from the accelerated route and note your current public IP, location and ISP. Then review your device’s network settings to confirm where the active DNS configuration comes from.
Connect to the target route and refresh this page. Confirm that the public IP and location match the selected route. If nothing changes, first check whether the client is using split tunneling that applies only to selected apps.
Review the DNS settings in your system or client again. If the client offers DNS takeover, remote resolution or encrypted DNS, confirm that each option is set as expected. A browser’s built-in Secure DNS setting may also override the system configuration, so check it as well.
First disable the browser’s independent DNS setting and reconnect to the route. If the result still differs from expectations, check the system network configuration, the client’s routing rules and local network caches. Change one setting at a time to identify which layer caused the difference.
This page sends only a same-origin request to this site’s GeoIP API and does not connect to third-party public lookup services. The server must process the current request to return IP and location data, but this site does not record the lookup result or forward failed lookups to another service.
If the API is temporarily unavailable, every result field will show “Temporarily unavailable.” The page does not generate a substitute address or infer location or proxy status from the browser environment.