See the public address used to access this site. After connecting through a route, run the lookup again to compare locations.
Current Exit IP
Lookup via 1KVPN
Waiting for lookup. Results will load automatically when JavaScript is enabled.
Public IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network provider
Temporarily unavailable
Proxy detected
Temporarily unavailable
Results apply only to this request. They do not represent the connection path used by every app and are not a DNS leak test.
What this information means
Public IP: the address websites see
The public IP is the address identified by 1KVPN’s API when it receives your request. It is not your device’s local network address. When connected through a route, websites will usually see that route’s exit IP. If your browser connects directly or uses split-tunneling rules, the result may still show your local network’s public IP.
Location and ISP: information from IP databases
The country, region, and network provider are based on IP registration data. They describe the network associated with the address, not your device’s precise location. IP allocations and database updates may take time to reflect changes. The provider may also appear under the name of a data center or upstream network.
Proxy detection: an indicative signal
This page displays a proxy detection result only when the API explicitly returns one. No proxy detected does not mean your connection is not using a proxy; a detected proxy does not mean there is a connection problem. If the API does not provide this field, the page will show it as temporarily unavailable rather than infer a result.
Before and after connecting: compare the actual route
Check your current exit IP first, then connect to your target region and run the lookup again. If the address has not changed, check the client’s connection status and your browser’s split-tunneling rules. Other websites may use different connection paths, so this page alone cannot confirm that all services are using the target route.
DNS Leak Check
DNS translates domain names into network addresses. A changed public IP does not prove that DNS requests use the same route. This page checks only exit information; it does not probe DNS resolvers, so it cannot automatically determine whether DNS is working as intended or leaking.
Check your client’s DNS settings. Make sure the DNS method matches your connection mode. Check whether the client offers DNS interception or an option to resolve requests through the route, and configure it according to the client’s instructions.
Check your browser’s Secure DNS settings. Your browser may use a separate DNS service. Review the browser and client settings together so you don’t overlook the browser while checking only system DNS.
Run a dedicated test while connected. If you use a separate DNS leak test, review its privacy policy first, then check which network the resolvers belong to. A difference between the resolver’s location and your exit IP does not necessarily indicate a leak; consider how DNS is configured.
Verify again after making changes. Reconnect, refresh the DNS cache as instructed by your client, then check your exit IP and DNS separately. If you still have questions, contact support through the user panel and describe your device platform, connection mode, and what you observed.