This page reads the network details visible to external services through a same-origin API. Use the results to check your exit location, network provider and proxy status; no device settings are changed automatically.
Proxy detection is based on network signals returned by the current API. Treat it as a troubleshooting clue, not a definitive assessment of the connection.
These results provide a quick snapshot of your current network exit. Check the address and location first, then use the ISP and proxy status to see whether the connection matches your expectations.
The IP shown here is the address your current connection presents to websites. After enabling a network acceleration service, refresh this page. If the public address changes, your web traffic is reaching sites through a different network exit. This page displays only the address returned by the API.
The location is matched from an IP address database and is useful for checking an exit’s approximate position. Databases can lag behind real-world changes, so this does not equal the device’s physical location or identify an exact place.
ISP identifies the network operator associated with the current exit address. After connecting through an accelerated route, it may show the route’s data center or upstream provider rather than the network originally used by the device.
The API returns proxy signals based on current network characteristics. A detected proxy does not necessarily mean the connection is abnormal, and no detection does not guarantee privacy or availability. Consider the exit region, ISP and actual browsing experience together.
Your public IP and DNS are two separate clues. The GeoIP result on this page cannot directly show which DNS resolvers the device is using, so check your system’s network details as well.
If web traffic is already leaving through the target region but domain lookups are still handled by the original access network, websites or the network provider may see a DNS source that does not match the exit region. This is commonly related to system DNS settings, browser secure DNS, router configuration or client split-routing rules.
Reconnect to the target route and run the check again. Confirm that the public IP, location and ISP have changed as expected. If the exit itself is unchanged, troubleshoot the client connection or split-routing settings first.
Open your device’s network details and review the DNS source. Also check whether the browser has Secure DNS enabled separately. Your system, browser and router may each use a different resolution path.
If DNS resolution still clearly comes from the original access network while the exit has changed, enable the relevant DNS handling option in the client and review split-routing rules. Reconnect after making changes, then repeat the same checks.
KcVPN does not log the results of checks on this page. Your browser sends a request only to this site’s same-origin GeoIP API, which returns the public IP, location, ISP and proxy status fields; the page does not forward queries to third-party public APIs.
Copying is completed in your current browser. If the API is temporarily unavailable, the page shows “Temporarily unavailable” rather than filling the result with an estimate or sample data.