Browser IP check

IP Lookup & Egress Check

First check where this browser request is coming from, then see whether the target app uses the same route.

VPNBack · IP Check

Current lookup results

Waiting for lookup

Enable JavaScript to check this browser’s public IP through our API.

Public IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

What these results mean

Public IP: Check your browser’s egress

This is the request source seen by our lookup API, not your device’s local network address. Checking before and after connecting can help determine whether your browser request is using a different egress IP. With split tunneling, a browser proxy, or app-specific settings, other apps may use a different route from this page.

Country or region and ISP: clues, not proof of identity

The location comes from an IP database and may lag behind changes in address allocation. ISP refers to the provider or network associated with the address in that database; it may not match the name of your current internet provider. Target platforms may use different databases, so this page’s location result may not match their own assessment.

Proxy detection: an additional reference only

“Proxy detected” means the API flagged this egress IP as a proxy. “No proxy detected” means only that this lookup returned no positive flag. Neither result proves whether your connection is working or guarantees access in a target app. If the API provides no clear result, this page shows “Temporarily unavailable” rather than treating a missing field as a negative result.

DNS leak self-check

This page checks your public IP. It does not automatically test for DNS leaks or determine whether your DNS is secure. DNS queries may be handled separately by your operating system, browser, or client, so a change in public IP alone can’t confirm how domain names are resolved.

  1. Check your client settings. Review the connection mode, routing rules, and DNS settings in use. Confirm whether the target domain should be resolved through the route or handled by your local network according to the rules.
  2. Check your browser settings. Review Secure DNS or custom resolver settings. A resolver set directly in the browser may differ from your system settings; check your client’s documentation to confirm what to expect.
  3. Run the test again. After switching routes, reopen the target app. If needed, clear the DNS cache as described in your operating system’s documentation, so an old cache doesn’t make it look as though nothing changed.
  4. Compare DNS resolution and access. Review your client’s diagnostic logs to see how DNS requests are handled. The resolver’s location doesn’t have to match your egress location; a location mismatch alone isn’t proof of a leak.

If you need help, first review your connection settings in the Help Center, then describe your operating system, client connection mode, and issue in a support ticket. Don’t share your password or full subscription link.

Lookup privacy and error messages

We don’t log lookups. Requests are handled through our own GeoIP API; this page doesn’t contact public third-party IP lookup services or save results in your browser’s persistent storage. The copy button writes your public IP to the clipboard only when you click it.

“Temporarily unavailable” may mean the network request didn’t complete, the API is temporarily unavailable, or the response didn’t include the relevant field. This doesn’t by itself mean the connection failed. Try again later or check again after switching routes. This page never substitutes sample addresses for real results.

For details on the scope and handling of lookups, see our Privacy Policy. To set up your connection, follow the Guides for client and subscription setup.