Current browser · Egress details

IP Lookup & DNS Check

First check where your request is coming from, then see how domain names are resolved. These results apply only to this lookup request, not to the network paths used by every app on your device.

Egress details

Lookup via our API

Waiting for lookup. Enable JavaScript to automatically retrieve your current egress details.

Public IP
Temporarily unavailable
Country / region
Temporarily unavailable
Network provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

What these details mean

Public IP: the network address used by this request

The destination service sees the public address used when the request reaches it, not your device’s address on the local network. After connecting to K6VPN, run another lookup and compare the results. With split tunneling, this page may use a direct connection while other services use the proxy. An unchanged IP doesn’t necessarily mean the client isn’t working.

Location and ISP: IP registration and network ownership

The country or region is estimated using an IP database, not your device’s location. Database updates, address allocation and network routing can all affect what’s shown. The ISP may be the name of the egress data center or network provider, rather than your local internet provider. Check the selected route in your client as well; the name alone isn’t enough to determine whether a route has a problem.

Proxy detection: a useful signal, not a connection verdict

Proxy detection relies on classification data provided by the API. A proxy detected result doesn’t mean your connection is unsafe, and no proxy detected doesn’t prove the request is using a direct connection. If the API provides no clear result, this page shows “Temporarily unavailable” rather than guessing from the IP or ISP name.

Check for DNS leaks

DNS translates domain names into network addresses. If your public IP has changed but DNS requests still take an unexpected route, investigate further. This page doesn’t automatically detect DNS resolvers or treat proxy detection as a DNS test result.

  1. Note your settings before connecting. Check your system and browser DNS settings, including any custom DNS or secure DNS options. Save the original configuration so you can restore it after troubleshooting.
  2. Check what your connection routes through. Review the current mode and DNS settings in your client. Rule-based mode may handle different domains differently. Keep test conditions consistent; don’t change your network, route and browser at the same time.
  3. Check where DNS requests go. Start with resolver and routing details in your client’s diagnostics. If you use a separate DNS test tool, review its privacy policy and compare the resolver’s network ownership with your client settings—not just its listed location.
  4. Rule out configuration conflicts one at a time. Check whether secure DNS in your browser, custom system DNS or other proxy software is overriding the client settings. Change one setting at a time, then reconnect and check again. Don’t delete settings if you’re unsure what they do.

A resolver and your egress point being in different regions doesn’t automatically mean there’s a leak. Public DNS services may use nearby access points or distributed egress. What matters is whether DNS requests follow the expected route and whether the available records match your configuration.

If the egress or DNS route still isn’t what you expect, see the troubleshooting guide for details on split tunneling and DNS, or submit a ticket through the user panel. Include your platform, connection mode, what you were doing when the issue occurred, and any error details with sensitive information removed.

Lookup privacy and errors

We don’t log lookups. Egress details come only from our API; we don’t fall back to a public third-party API if a lookup fails. This page’s script doesn’t save lookup results to persistent browser storage. When you copy an IP, it’s placed on your device’s clipboard, so take care where you paste it.

“Temporarily unavailable” means the API couldn’t return usable information; it doesn’t mean your device has no public IP. Check your internet connection and try again. If only some fields are missing, the others may still be useful. Run a new lookup after changing networks or connection modes so you don’t mistake old results for the current status.

Before sharing a screenshot, hide the full IP address and any account details. See our Privacy Policy for more on how data is handled.

Start Free