IP and Egress Check

Check Your Current Public IP

Use our API to see the public IP address used by this browser request. Check before and after connecting to compare the egress IP. This result does not mean every app on your device uses the same route.

Egress Details

Not checked yet
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Preparing the lookup. The copy button will be available once a valid IP address is retrieved.

This result reflects a single lookup, not continuous monitoring. Run another check after changing routes, split-tunneling rules, or browser network settings.

Understanding the Results

What the Results Tell You

Consider egress changes, database-based geolocation, and proxy detection separately to assess whether your current connection matches expectations.

Your IP Shows Where a Request Exits

The public IP is the address our API sees for this request, not your device’s local network address. If your browser reaches this site through a proxy, the displayed address is usually that route’s egress IP. If a direct-connection rule applies to this site, the address may still belong to your local network even while your client shows as connected.

Geolocation Is a Database Estimate

Country, region, and ISP information come from the API’s geolocation data; they do not confirm your device’s actual location. Address allocation, network reselling, and database updates can cause results to differ from a route’s name. The ISP shown may not be VPNLQ—it may be the network provider associated with the egress IP.

A Proxy Label Is Not a Security Verdict

A proxy detection result means the API has labeled the egress IP as proxy-related; it does not identify the connection protocol or encryption status. A negative result does not prove the request went direct. If the API does not return this field, this page shows “Temporarily unavailable” rather than treating the missing value as “No.”

A Change in Egress Does Not Guarantee Access

A different egress IP only shows that the route to this site’s API has changed. AI Tools, Streaming services, and other apps may use different routing rules or determine availability based on account region or their own policies. Verify the connection in the app you want to use.

DNS and Manual Checks

Check for DNS Leaks

This page checks the egress IP for HTTP requests; it does not detect DNS resolvers. A changed IP does not prove that DNS queries use the same route.

First, Confirm the Expected DNS Route

DNS translates domain names into IP addresses. A client taking over DNS, the system using a local resolver, and a browser using encrypted DNS can each create a different resolution path. To identify unexpected outbound queries, first determine which domains should resolve through a proxy and which should use local DNS.

  1. Check your client settings. Confirm that DNS takeover, routing rules, and connection mode are enabled as expected. In rule-based mode, check the connection and DNS rules for the domain in question—not just the name of the current route.
  2. Check your system and browser. Review your system DNS settings and the browser’s Secure DNS or encrypted DNS options. The browser may choose a resolver that differs from the client’s settings. Before making changes, confirm where each setting comes from and keep a copy of the original configuration so you can restore it.
  3. Visit the domain again. When you can control the test conditions, clear the DNS cache or restart the relevant app, then make a new request. A cache hit may mean no new DNS query is made, so one visit alone cannot show where the lookup actually went.
  4. Review DNS records. Start with DNS diagnostics in your client or your system’s network logs to check the resolver and request path actually used. If you use a trusted DNS testing tool, review its privacy policy first. Compare its results with your expected configuration; do not draw conclusions from a location label alone.

If the configuration does not match the actual route, first check for rule overrides and app-specific network settings. Then send support a configuration summary with credentials redacted. For basic connection steps, see Getting Started. For connection issues, check the FAQ or submit a support ticket in the user panel.

Lookup Privacy

We do not log lookups. Checks use our own API and will not fall back to a third-party public API if it is unavailable. The copy button writes your current public IP to the clipboard only when you click it.

Your public IP is network information. Before sharing screenshots or ticket attachments, consider whether to redact your IP, account details, and subscription links. For details on how we handle service data, see our Privacy Policy.