TC / NETWORK INSPECTION

Public IP & DNS Check

First check where your browser is connecting from, then review the route used to resolve domain names. The IP check reflects this request only; it doesn’t show how every app on your device connects.

TC · EXIT INSPECTOR

Current connection details

Browser request

Preparing to check.

Public IP IP ADDRESS
Not checked yet
Country / Region LOCATION
Not checked yet
Network provider / ISP PROVIDER
Not checked yet
Proxy detected PROXY SIGNAL
Not checked yet

After switching routes or connection modes, check again to compare your public IP. Location and proxy detection are based on information returned by the API; they don’t determine whether a destination website will let you in.

What these results mean

Public IP: the address used for this request

The address shown to a website is the public IP that made the request. In rule mode, this page may use your local network or a proxy, depending on how your client routes this site’s domain. If your IP stays the same after switching routes, first check whether a rule sends this page directly. Don’t assume the route is not working.

Location and ISP: registration details for the IP address

IP location is an estimate made by an IP database. ISP usually refers to the network provider or organization associated with the connection. Neither necessarily reflects your device’s physical location, and the result may differ from a route’s city label. Address registration, database updates, and network routing can all affect what’s shown.

Proxy detection: an indicator, not a verdict

“Proxy detected” means the API found a related indicator. “No proxy indicator detected” doesn’t confirm that your connection is direct. If the API doesn’t return a detection field, this page shows “Temporarily unavailable.” This indicator can’t prove anonymity or predict whether ChatGPT or a streaming platform will accept your current IP.

A matching location doesn’t guarantee access to a particular service. Check your account region, access rules, and the service’s status separately.

To verify your connection setup, see the getting started guide. If you can connect but websites won’t load, follow the troubleshooting guide step by step.

Check for DNS leaks

DNS translates domain names into network addresses. Even when web traffic uses a proxy, DNS requests may still use your local network. To check for an unexpected resolution path, review your client’s DNS settings alongside actual DNS records. Your public IP alone can’t confirm a DNS leak.

This page checks your public IP; it doesn’t run a DNS leak test or read your system DNS settings. The steps below are for manual checks and won’t produce an automatic “passed” or “leak detected” result.
  1. Confirm the expected route. Check whether your client is in rule mode or global mode, and confirm whether the app and domain you’re testing should use a proxy. A domain explicitly set to connect directly by a rule may use local DNS without indicating a configuration error.
  2. Review your client’s DNS settings. Check whether DNS is enabled, how DNS requests are routed, and whether any direct-resolution rules operate separately from web traffic. Options vary by client, so refer to its documentation rather than judging by a toggle’s name alone.
  3. Check your browser’s encrypted DNS settings. Browsers may have separate DNS settings. Compare your browser and client configurations to confirm that DNS requests follow the expected route. Encrypted DNS protects DNS traffic in transit; it doesn’t automatically route requests through a proxy.
  4. Review actual DNS records. If your client supports local connection logs, you can temporarily check the DNS requests and routes for the domain you’re testing. System DNS settings can provide context, but they can’t prove on their own which resolver the app ultimately used. Turn off any local debug logging you no longer need when you’re done.
  5. Test the app again. After changing settings, reopen the app you’re testing and, if needed, clear the DNS cache as described in your system’s documentation. Test the same domain and compare its resolution path with the previous result. Change one setting at a time to identify what affected the outcome.

If you’re still unsure, open a support ticket in the dashboard and include your operating system, client settings, connection mode, and the issue you’re experiencing. Before sharing screenshots, hide subscription links, account details, and other sensitive information.

QUERY PRIVACY

Check privacy

VPNTC doesn’t log checks. The IP check calls only VPNTC’s own API and doesn’t fall back to third-party public lookup services. Results appear on this page; its scripts don’t save them to your browser’s local storage.

The copy button copies only your public IP. Before sharing it in a public forum, consider whether you want to disclose this network information. See the Privacy Policy for details about how VPNTC handles privacy.