Current Public IP Check

What This Information Means

Your Public IP Isn’t Your Device’s Local IP

Your current public IP is the source address seen by VPNTQ’s API. When using an international route, it may be the route’s exit IP. Without one, it may be a public IP shared by your network. It isn’t your device’s address on a local network, and it can’t identify your home address.

Note your current results, connect to your chosen route, then check again. If your browser traffic is using that route, your public IP will usually change. Split-tunneling rules may send requests to this site directly. If the IP hasn’t changed, check your client mode and rules before assuming the connection failed.

Location and ISP Are Indicators, Not Proof

Location is based on IP geolocation data and may be affected by database updates and IP allocation. The ISP field identifies the provider or network organization associated with the IP; it may not be your local broadband provider. Use these details to check whether your exit IP looks as expected, but don’t treat them as a substitute for testing access to the intended website.

Proxy Detection Isn’t a Security Verdict

This field shows only the detection result returned by the API. “No proxy detected” doesn’t guarantee a direct connection, and “Proxy detected” doesn’t mean there’s a problem. If the API can’t provide a clear result, this page shows “Temporarily unavailable” rather than treating missing information as a negative result.

DNS Leak Check

DNS translates domain names into network addresses. If web traffic uses an international route while DNS queries go to an unexpected resolver, the DNS and web traffic paths may not match. This page’s IP lookup does not test for DNS leaks, and an exit IP alone can’t tell you whether a leak has occurred.

1. Check your client settings. Review the client’s DNS, system proxy, and split-tunneling settings. Confirm that the client handles domain lookups as expected. Option names vary by client and version.
2. Check your browser settings. Secure DNS settings may be separate from your system configuration. Check whether a custom resolver is enabled and whether it fits your connection setup. Don’t disable security features just to make the reported locations match.
3. Compare before and after connecting. If you use a trusted, dedicated DNS leak test, compare the resolvers and query paths it reports—not just the country labels. DNS providers may use distributed infrastructure, so a different location alone doesn’t mean there’s a leak.
4. Troubleshoot the symptoms. If domain lookups fail, your exit IP doesn’t change, or apps behave inconsistently, note your platform, client mode, and any error messages, then check the Help Center. Hide account details before sharing screenshots.

For the full connection and verification process, read the Quick Start Guide. For setup help, visit the Help Center or submit a support ticket from your user panel.