IP ADDRESS
Public IP
Checking
CURRENT NETWORK RECORD
Public IP and Network Route Check
View the address, region, and ISP presented by your current connection. Results come from this site’s same-origin check API and help verify whether a route switch has taken effect.
LOOKUP RESULT
Current public IP record
Once the check begins, the page displays only fields returned by the API. Missing information is not filled in by inference.
Reading this site’s check API…
LOCATION
Country or region
Checking
NETWORK
ISP
Checking
PROXY SIGNAL
Proxy status
Checking
FIELD NOTES
What this information means
The result describes the public network exit presented when the request reaches the internet. It is not the device’s address on a local network.
IP → PUBLIC ROUTE
Public IP
Websites and online services typically use the public IP to determine where a connection comes from. After switching routes, run the check again. If the address and region change, the page request is being sent through the new public exit. Older connections still running in the browser may need a page refresh to reconnect.
LOCATION → DATABASE MATCH
Country or region
The region is matched against an IP database and reflects the area registered or identified for that address range. It is useful for checking route direction, but does not represent the device’s precise location. Database update schedules vary, so the region name may differ from the actual data-center label.
ISP → NETWORK OWNER
ISP
The ISP field identifies the network operator or autonomous system associated with the current address range. Home broadband, mobile networks, cloud networks, and international routes may show different names. Use this field as one clue when assessing the exit type, not as a standalone measure of connection quality.
SIGNAL → INTERFACE RESPONSE
Proxy status
Proxy status shows only the determination returned by the check API. A network exit may be classified based on address-range attributes, sharing patterns, or database labels. If no result is returned, the page clearly states that the API provided no determination rather than inferring one from the ISP name.
DNS CHECK
DNS Leak Check
DNS translates domain names into addresses that can be reached. If the route has changed but domain resolution is still handled by the previous network, the resolution path and access path may not match.
Confirm the public route first
Note the public IP, region, and ISP shown above. After switching to the target route, run the check again and confirm that the request is coming from the expected region before reviewing DNS settings.
Check your system network settings
Open the detailed settings for your current network connection and check whether DNS is assigned automatically or specified manually. If addresses from the previous network are still configured, confirm that they match your current connection setup.
Review browser DNS settings
Some browsers enable encrypted DNS independently and bypass system settings. Check the browser’s security or privacy settings to confirm that the selected resolution method matches your current network setup. Using a separate resolver does not necessarily indicate a leak, but its destination should be clear.
Reconnect
After changing settings, close pages that are still using the old connection, reconnect the route, and refresh the check results. If the public details remain unchanged, disconnect the current route and reconnect to the target region in your client.
PRIVACY NOTE
Lookup results are not retained
KvVPN does not record the results of checks on this page or write returned fields to browser local storage. The page displays the check API response only during the current session; closing or refreshing the page starts a new check.
If the API is temporarily unavailable, the page shows only a retrieval failure notice. It does not switch to a third-party public lookup service or generate substitute results.