NETWORK CHECK
Current connection result
Checking your current public connection details through the VPNCK API…
- IP address
- Loading
- Country or region
- Loading
- ISP
- Loading
- Proxy detected
- Loading
Reads the IP, country or region, ISP, and proxy detection signals shown to the public by the current network request. Results come from VPNCK’s same-origin API and are not relayed through a third-party public lookup service.
NETWORK CHECK
Checking your current public connection details through the VPNCK API…
The result describes the network exit presented when the current browser request reaches the public internet. It is not the device’s local network address and cannot, by itself, prove that every app uses the same route.
This is the address visible to the public for the current request. If the address changes after connecting to a network acceleration service, the browser’s public internet exit has changed. If it does not, check the connection status and reload this page to run the lookup again.
The location comes from an IP address database and usually indicates the registered address range or the region where the data center is located. It can help identify the route’s exit direction, but it does not represent the device’s actual location and may differ as databases are updated.
The ISP field identifies the carrier network, data center, or autonomous network associated with the public address. Naming conventions vary between databases, so use it as a route-ownership reference—not as a conclusion about connection quality or bandwidth.
This result comes from identification signals provided by the GeoIP API. If a proxy is detected, it only means the address characteristics are flagged by the database. If none is detected, websites may still reach a different conclusion because they can use other data sources and rules.
The public IP and DNS requests may take different paths. This page reads only the GeoIP result and does not fabricate a DNS test conclusion; browsers also provide no universal interface for directly reading the resolver actually used by the operating system.
After connecting to the target route, run this lookup again and record the public IP, country or region, and ISP. Use these results for comparison with the system’s DNS resolution path.
Open the system terminal and query this site’s domain. Focus on the resolver field in the command output, rather than the address ultimately returned for the domain.
If DNS requests are still clearly handled by the original network provider while the public exit is on another network, check the client’s DNS takeover, split-routing rules, and custom system DNS. When encrypted DNS is enabled, a different resolver name does not necessarily indicate a leak.