My IP and Location
See the public IP address your browser uses to reach this site. Run the lookup again after connecting to compare your results.
Getting your connection details from TangVPN…
- Public IP address
- Checking…
- Country / Region
- Checking…
- Internet service provider (ISP)
- Checking…
- Proxy detected
- Checking…
What this means
Public IP: the address seen by this site
Your public IP is the address shown when this request reaches our site, not your device’s local network address. Check it before and after connecting to see whether requests to this site are using a different route. With split tunneling, this site and other apps may use different routes, so these results don’t reflect the connection status of every app.
Location and ISP: address data, not device location
Location data comes from IP address databases, not GPS. Database updates, address allocation, and network routing can all affect what’s displayed. ISP usually refers to the provider or network organization associated with the address, which may differ from the operator providing your current connection. If the location doesn’t match your expectations, check your selected route and run the lookup again.
Proxy detection: an indicator, not a privacy verdict
Proxy status is shown only when the API explicitly returns a detection result. “No proxy detected” doesn’t mean you aren’t using a proxy or indicate how anonymous you are. Likewise, “Proxy detected” doesn’t tell you whether your connection is working well. If the API doesn’t return this field, the page will say “Temporarily unavailable” rather than guessing from the ISP name.
DNS leak check
DNS translates domain names into network addresses. A changed public IP doesn’t necessarily mean DNS requests are taking the same route. This page checks only the route used for HTTP requests. It doesn’t run a DNS leak test or identify the DNS resolvers in use.
- Check your client settings. Review your DNS and split-tunneling configuration, and confirm that the client routes relevant domains through the intended DNS path. Option names vary by client, so refer to the settings shown in your app.
- Check your browser settings. See whether Secure DNS or encrypted DNS is enabled and whether a specific resolver has been selected. Browser settings may be separate from system settings, but encrypted DNS alone doesn’t prove that a leak is occurring.
- Review the actual DNS route. If your client provides DNS logs or connection diagnostics, check which resolver handled the test domains. You can review logs locally. Without diagnostic data, treat the DNS status as unverified rather than confirmed safe.
- Verify after changing settings. End the current connection, clear the DNS cache as directed by your operating system or browser, then make a new request. Running this lookup again checks only for a change in your public IP; confirm the DNS route separately using your client’s diagnostics.
A DNS resolver being located in another region isn’t, by itself, evidence of a leak. What matters is whether requests follow your intended DNS policy—not whether the resolver’s name or listed location matches your public IP’s location.