First check where your request is coming from, then verify that DNS resolution follows the expected route. After connecting to a route, run the check again and compare the results.
This check reflects only the current browser request. Other apps, address types, or routing rules may use a different public IP. This page does not run an automated DNS leak test.
Public IP details can help with troubleshooting, but they don’t provide a complete picture of connection quality or privacy.
The public IP is the address our endpoint sees as the source of your request. It is not your device’s address on the local network. Country and region are based on an IP geolocation database, which may be out of date and cannot confirm your device’s actual location.
ISP usually refers to the network operator associated with your public IP. When you connect through an international route, it may show the name of the exit network or data center—not your local broadband provider, and not necessarily VPNBasic.
Proxy status depends on the identification data returned by the endpoint. A proxy detected result doesn’t mean your connection has a problem; no proxy detected doesn’t prove that all traffic is using the intended route. If the endpoint doesn’t provide this field, the result will say that it can’t be determined.
If your public IP hasn’t changed after connecting, check that the client is connected and that this page’s request isn’t set to bypass the proxy. Even after the IP changes, test connectivity in the app you actually use.View connection and troubleshooting guides →
An IP lookup shows only the public IP used for a webpage request. It can’t tell you which route a DNS query took.
DNS resolves domain names to network addresses. If DNS queries should follow your client’s proxy rules, check the client’s DNS, system proxy, and tunnel settings, and confirm its current mode. With system proxy enabled alone, some apps may handle DNS outside those rules.
Check whether your browser uses its own Secure DNS setting and whether your system specifies a different DNS resolver. Browser settings, system settings, and client rules may all apply at once. Note the original settings before making changes, and follow your client’s instructions to avoid changing multiple things at once and making the cause harder to find.
If your client provides DNS or connection logs, visit the domain you want to check and see which rules match the DNS query and the subsequent connection. A difference between the DNS resolver’s location and your public IP’s location doesn’t necessarily indicate a leak. Check whether DNS queries are using the intended route.
Note your platform, client mode, domain, and the issue you’re seeing, then submit a ticket through the user portal. Don’t include full subscription URLs, access credentials, or other account details in screenshots shared publicly. This page does not present an IP lookup as a DNS security test.
We never log queries. Check requests are sent only to a same-origin endpoint on this site; if a request fails, we don’t fall back to a third-party public lookup service. This page’s scripts don’t save results in your browser’s local storage. The public IP is only written to your clipboard when you click the copy button.
Read the privacy policy →