$exitYour browser’s network exit

IP Address Check & DNS Checks

Check your exit first, then review your DNS path.

This check reflects the current browser request, not how every app connects.

$exit = current

Current exit details

Checked via VarVPN API

Retrieving exit details…

Public IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network provider
Temporarily unavailable
Proxy detected?
Temporarily unavailable

After switching routes or connection modes, check again to compare exit details. Proxy detection is for reference only and does not determine whether your connection is secure.

What these results mean

Public IP and location

Your public IP is the network address shown when you visit this site. If you use a proxy and your browser traffic passes through the selected route, the result will usually show that route’s exit address instead of your local network’s.

Location comes from an IP database, not device geolocation. Database update times, address assignments, and network exit deployments can all affect the result. It should not be used to determine an exact location.

ISP and proxy detection

The ISP field usually identifies the network provider or hosting network associated with the exit address, not necessarily your local broadband provider. Seeing a data center network name when connecting through a remote route is normal.

“Proxy detected” means the API identified the exit as a proxy. “No proxy detected” means only that one was not identified in this check. If the result is unknown, it stays unknown; it does not confirm whether your connection is encrypted.

$dns

How to check for DNS leaks

DNS translates domain names into network addresses. Even when web traffic goes through a remote exit, DNS queries may take a different route. This page checks only the exit used by HTTP requests. It does not test for DNS leaks or use the exit location as a DNS test result.

Review settings along the DNS resolution path

  1. Check your client’s DNS settings. In the client’s connection and DNS settings, confirm that DNS interception is enabled for your current connection mode. Setting names vary by client; refer to the relevant guide and in-app instructions.
  2. Check your browser’s secure DNS settings. Your browser may use a separate encrypted DNS service. Make sure its settings align with your system and client DNS policies. Encrypted DNS alone does not mean queries go through your selected route.
  3. Compare the resolver with your expected settings. If you use a separate DNS test, check the resolver’s operator and network location, then compare them with your client settings. A resolver and exit in different regions do not, on their own, prove a leak.
  4. Test again after changing settings. Reconnect as instructed by your client, reopen the page, then check the exit and DNS paths separately. Seeing a changed IP alone does not confirm that all DNS queries use the expected route.

This page does not automatically visit external DNS test sites. Before using another test tool, read its privacy policy and avoid sharing subscription links or account credentials.

Query privacy

VarVPN does not log queries. This page retrieves exit details through VarVPN’s API only; it does not send queries to a third-party public API as a fallback or ask for account details.

The copy button copies only the public IP shown on this page. Before sharing your results, check whether they contain network details you don’t want to make public.

Read the Privacy Policy →