IP Lookup · Location · Proxy Check

My IP and DNS Leak Check

The page queries our API as soon as it loads and reads your current exit IP, country, ISP and proxy detection status. Run it once before and once after connecting a route to confirm the exit really switched.

Current exit details

Checking
Exit IP address

Checking…

Country / Region
Checking…
ISP / Carrier
Checking…
Proxy detection
Checking…

This lookup is only used to display results on this page; nothing is written to your account.

Reading the results

What these details tell you

The four results answer different questions; you need all of them together to judge whether the current exit matches your expectations.

IP address
This is the exit address that destination websites see, not your device's local address. It determines which region they think you're in. If it doesn't change after you connect a route, your traffic is still going out through your local connection.
Country / Region
Derived from the registered location of the IP block, it usually matches the country of your current exit. It's normal for it to differ from where you physically are — the location shown follows the exit. When you need to reach region-locked services, this is the field to check.
ISP / carrier
The organization that owns the exit address. A data center or hosting name means traffic is going out through a server; a local broadband provider means traffic is still going out directly. This field makes it easy to tell an active route from an inactive one.
Proxy detection
Some IP databases flag addresses as proxy or data center for websites to reference. The flag is the database's judgment and doesn't mean the destination will block you; if you keep hitting verification on certain platforms, switching to another route usually helps more.
Self-check steps

How to check for DNS leaks

A changed exit IP doesn't mean DNS resolution goes through the route too. A DNS leak means your traffic is forwarded through the route, but domain lookups are still handled by your local network — exposing your real location in the process.

Why it happens

Domain resolution and traffic forwarding are two separate channels. The client may take over your traffic while the resolver addresses configured in the system stay the same; a browser's built-in secure DNS bypasses system settings and queries its own resolver directly; and resolver settings at the router level are invisible to the client, so lookups can still go out locally.

How to check

  1. On Windows, run ipconfig /all in Command Prompt and check whether the "DNS Servers" line points to an address on the route side.
  2. On macOS, run scutil --dns in Terminal and check the nameserver entries in the resolver list.
  3. Check whether your browser has "Secure DNS" or DNS over HTTPS enabled. When it is, resolution is handled by the provider the browser specifies, regardless of your route's exit.
  4. Come back to this page and look up your exit IP again to confirm the location matches the route you selected.

How to fix it

  • If your client offers options such as "Remote DNS" or "DNS forwarding", enabling them makes resolution follow the route.
  • Turn off the browser's built-in secure DNS so resolution falls back to system settings.
  • After changing resolver settings on your router, restart the client so the new configuration takes effect.
  • After switching routes, run the checks above again.
Note

This page only reads your exit IP and location; it can't see which channel your DNS queries take. The checks above have to be done in your own system settings.

About lookup records

Lookups are handled by our API, and results are only shown on this page — they aren't written to your account or linked to it. Repeating a lookup from the same exit address leaves no searchable history on the site.

VPNAY's privacy policy is anonymous and log-free; browsing content is never recorded. Creating an account only requires a username and password — no email address needed.

FAQ

IP lookup FAQ

Is the IP shown my device's local address?
No. This page reads the exit address used to reach this site — the same address destination websites see. Your device's address inside the local network (commonly starting with 192.168) never appears here.
Why doesn't the location match where I actually am?
The location is derived from the registered location of the IP block. Once you connect a route, the exit moves to the route's location, and the location follows. Without a route connected, a location shown elsewhere is usually due to carrier exit routing or how the IP block is registered — that's normal.
Does a "proxy detected" flag affect my usage?
This field comes from an IP database's flag, not from our own judgment. Most websites won't block you because of it; a few platforms with strict risk controls may ask for extra verification. When that happens, switching to another route or region usually clears it up.
What if my IP doesn't change after connecting?
Check three things in order: whether the client shows as connected; whether a split-tunneling rule is excluding the current destination from the route; and whether a browser proxy extension is overriding the client's settings. Then click "Check again", or try another route.
Why do results sometimes fail to load?
When the API returns no data, the page shows "Temporarily unavailable". This usually means your current network can't reach our API, or the API is under maintenance. Just click "Check again" later — the page never fills in estimated values.
Are lookup records saved?
They aren't written to your account or linked to it. No sign-in is needed, and results only appear on this page. VPNAY's privacy policy is anonymous and log-free; browsing content is never recorded.
120+ countries / 250+ routes Unlimited devices 30-day money-back guarantee No email address needed Alipay / WeChat Pay / USDT
Start Free