NETWORK-CHECK

Check Your Exit IP

Opening this page instantly looks up your network's exit IP, location, and ISP, and checks whether the address shows proxy characteristics. Test once before and once after connecting to VPNTd to confirm the route is working; lookups run through this site's own API, not a third-party service.

Current Exit Info Checking
Exit IP · Address
···
Country / Region ···
City / Location ···
ISP / Provider ···
Proxy Detection ···
FIELD-NOTES

What This Info Means

Each of the four fields answers a separate question: what the address is, roughly where it is, who runs it, and whether it's a proxy exit.

Exit IP

The source address seen by the servers you connect to. Without a VPN, this is the address assigned by your local broadband provider; once you connect to VPNTd and select a route, it should switch to the address of that route's landing server. Refresh this page before and after connecting and compare the results to see whether the route is in effect.

Country / Region and City

An approximate location drawn from IP geolocation databases, usually accurate to city level. These databases lag behind reality, so a mismatch with your actual position is normal. To judge whether a route is working, just check that the region changes along with the route—street-level precision doesn't matter.

ISP / Provider

The network operator or data center that owns the IP range. After connecting to a route, this usually shows a data center or cloud provider name; if it still shows your local broadband ISP after a refresh, your traffic isn't going through the route—reselect a node in your client and test again.

Proxy Detection

The API compares your current address against IP reputation databases to see whether it's flagged as a proxy or VPN exit. Seeing "Proxy detected" after connecting to VPNTd is a normal result—it confirms the exit has switched. This check relies on reputation data, so treat it as a reference only.

DNS-CHECK

DNS Leak Test

A DNS leak means you're connected to a route, but your DNS queries are still handled by your local ISP's DNS servers, leaving traces of your browsing on the local network. Follow these three steps to check:

  1. Get a baseline. Disconnect from the service, open this page, and note your exit IP and ISP; then run a DNS lookup command in your terminal and note the default DNS server's address.
  2. Re-test while connected. Connect to VPNTd, select a route, refresh this page, and confirm the exit IP has switched to the route's landing region and the ISP shows a data center provider.
  3. Compare DNS servers. Run the same lookup command again and check the DNS server address in the response: if it still shows your local ISP's address, you have a DNS leak.
# Windows
nslookup example.com

# macOS / Linux
dig example.com
If you find a leak: VPNTd subscription profiles use remote DNS by default, forwarding resolution requests through the route. If a leak shows up, re-import your subscription in the client and check whether any custom DNS settings are left on your system.
PRIVACY

Privacy Notes

Every lookup on this page runs through VPNTd's own API, requires no sign-in, and returns results only to your current browser. We keep no logs of IP lookups.

To learn about route coverage or get started, keep reading:

Guides → All Routes → Pricing →