IP Details · Connection Check

VPNDV IP Lookup

See the public IP used by this browser to access our site. After connecting or switching routes, run the check again and compare the results.

Current IP details

Not checked yet

Public IP: Temporarily unavailable
Location: Temporarily unavailable
Internet service provider (ISP): Temporarily unavailable
Proxy detected: Temporarily unavailable

Preparing your lookup. Results come only from our site’s interface.

What these results mean

Public IP: the address our site sees

Your public IP is the address used by the request when it reaches our site. It is not your device’s local network address. Note the result before connecting to a route, then connect and run the check again to see whether your request to our site uses a different IP. If it has not changed, check your client’s connection status and routing rules. In split-tunneling mode, requests to our site may still use your regular connection.

Location: an estimate based on IP data

The location is based on the IP geolocation data used by the lookup interface. Database update cycles, IP allocations and providers’ network deployments can all affect the result; it does not necessarily reflect your device’s actual location. If the reported location differs from the route name, check the route selected in your client and how the destination service identifies the connection. Don’t assume there’s a connection problem based on geolocation alone.

ISP: the network behind the IP

The ISP field typically identifies the carrier or hosting network associated with the public IP. When you connect through an international route, it may show the name of the exit network rather than your regular broadband provider. This field alone cannot confirm whether an IP is residential, a native IP or dedicated. See our IP types guide for more about the differences.

Proxy detection: a label, not a verdict

The proxy field shows how the interface classifies characteristics of an IP address. “Proxy detected” does not mean a destination platform will necessarily block access, and “No proxy detected” does not mean every platform will accept the address. If the interface can’t provide an interpretable result, this page shows “Temporarily unavailable” rather than treating missing data as a negative result.

This page checks only the request made to our site. Other websites, apps or browsers may follow different routing rules. To confirm that a connection works as expected, visit the destination service itself.

Connection and route help →

Manual checks

Check for DNS leaks

The public IP lookup does not test for DNS leaks. This page will not automatically report that your connection has passed a leak test.

DNS translates domain names into addresses your device can reach. Browser requests and DNS lookups may take different routes: even if web traffic uses your selected route, domain lookups may still be handled by your local network or a DNS service configured in your browser. To determine whether there’s a leak, check whether lookups follow the route you expect—not just the country where the DNS service is located.

Confirm the expected route. Check whether your client is using global or split-tunneling mode, and review its DNS settings. If you want DNS queries to follow your selected route, make sure the relevant option is enabled and save the configuration as described in your client’s documentation.
Check your browser settings. Review your browser’s Secure DNS or encrypted DNS settings. If the browser uses a separately configured DNS service, its actual route may differ from your system or client settings. Encrypted DNS is not, by itself, a leak—and it does not prove that lookups follow your selected route.
Check system and client logs. Review the DNS servers currently configured on your system. If your client provides DNS or connection logs, check which rule handled the domain in question. System settings can offer a clue, but the actual route may differ when the client handles DNS resolution.
Run a dedicated test if needed. A full DNS leak test sends queries for test domains and checks where they came from. This page does not provide that functionality. Before using another testing tool, review its privacy policy and compare its results with your client’s logs.
Verify again after making changes. After changing DNS settings, reconnect as directed by your client, then visit the destination service. If needed, clear your system or browser DNS cache so cached results don’t affect your checks.

If DNS requests aren’t following the expected route, describe your device platform, connection mode and symptoms in a support ticket in the user panel. Don’t submit passwords, full subscription URLs or unredacted logs that contain browsing activity.

Query privacy

We don’t log lookups. Check requests are sent only to our site’s interface. If a lookup fails, this page won’t call a third-party public interface, and results aren’t saved in your browser’s persistent storage. The copy function runs only when you click the button.

Your public IP can still identify your network. Before sharing a screenshot or troubleshooting notes, redact any address details that aren’t needed. See our Privacy Policy for more information.