// EXIT INSPECTION

Current IP Lookup

Check which route your browser is using, then see whether the connection matches your expectations. This page shows network details for this lookup only; it doesn't reflect the connection status of every app on your device.

// CURRENT EXIT

Connection details

Waiting for lookup
Current public IP
Temporarily unavailable
Location
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Enable JavaScript to check your connection through our service. If the details don't load, try again later.

// READ THE RESULT

What these details mean

IP address: the address seen by this lookup

The public IP is the source address seen by our lookup service. Check it before and after connecting your client to compare results. If your browser is routed through the selected connection, the public IP will usually change. If the browser is set to connect directly, the lookup may still show your local network's public IP.

If the result hasn't changed, check that your client is connected, that its current mode includes browser traffic, and that the lookup request isn't being routed separately. A connection indicator in the client doesn't prove that all traffic uses the same route.

Location and ISP: network registration details, not your device's location

Location is based on an IP geolocation database, not your device's precise location. Database updates, IP allocation, and network operations can all cause the result to differ from the route's name. The ISP is the provider associated with the public IP; it may instead show a data center or another network operator.

Proxy detection: an indicator, not a privacy verdict

The proxy field shows only the detection result explicitly returned by the lookup service. “No proxy detected” doesn't mean your connection isn't using a proxy, and it says nothing about encryption, anonymity, or whether a destination site will allow access. If the service doesn't return this field, this page shows “Temporarily unavailable” rather than assuming the answer is “No.”

// DNS SELF-CHECK

DNS Leak Check

DNS translates domain names into network addresses. Web traffic and DNS requests can take different routes, so a changed public IP alone doesn't prove that DNS is following the intended route. This page checks connection details only; it doesn't run a DNS leak test or report a pass.

  1. Check your client's DNS settings

    Open the client you're using and review its DNS handling and routing rules. Check whether the client handles DNS lookups for the domains your browser visits. Exact setting names vary by client.

  2. Check your browser and system DNS settings

    Check whether your browser uses its own Secure DNS setting and whether your system is configured to use another DNS service. Separate DNS settings may not follow your client's DNS rules. Note your current settings first, then check them against your client's guidance. Avoid changing several options at once, so you can identify the cause.

  3. Review DNS logs

    If your client provides connection or DNS logs, check where DNS requests go while you visit the site in question. Focus on whether the resolver matches your expectations, not just its location. A public resolver in a different region from your exit IP isn't, by itself, proof of a leak.

This page doesn't automatically send requests to external testing sites. If you're still unsure, open a support ticket in the user panel and include your client platform, connection mode, and what you're seeing. See the getting started guide for setup steps, or the complete guide for detailed troubleshooting.

First Month Free