Public IP & DNS Check

What These Results Mean

Your public IP is the address VPNKZ sees for your request. It reflects the network route used for this browser request, not necessarily your device's address on your local network. With split tunneling, this page and other apps may use different routes. An unchanged IP may simply mean this page is still using the same connection rule.

Country, region and ISP are approximate attribution details, not precise location data. Database updates, address allocation and network routing can all affect what is shown. The provider field may show a hosting network or data center rather than your local internet provider. Don't judge whether a route is working based on the location label alone.

Proxy detection is an indication, not a security verdict. This page displays a result only when the API provides a definitive status. “No proxy detected” doesn't mean your connection isn't using a proxy, and “Proxy detected” doesn't mean anything is wrong. Missing fields are marked as temporarily unavailable; unknown results aren't treated as negative.

This page checks only the route your current browser uses to reach VPNKZ. It doesn't test connection speed or show how all your apps connect, or whether a particular platform allows access.

DNS Leak Self-Check

DNS translates website names into network addresses. A changed public IP only shows that this web request took a different route; it doesn't prove DNS queries followed the same path. This page doesn't probe DNS resolvers, so it won't report results such as “passed.”

1. First, check your client settings. Make sure your connection mode, routing rules and DNS settings match your expectations. If only some traffic uses the selected route, domain lookups may follow different rules too.
2. Next, check your system and browser. Review the DNS settings currently used by your operating system and check whether your browser has its own Secure DNS setting enabled. Browser DNS resolution may differ from your system or client settings, so assess it against your actual configuration.
3. Compare the resolver with your expected route. If you use a trusted DNS testing tool, check which resolver it identifies and which network it belongs to. Public DNS services, caching and infrastructure in different locations can affect the reported location; a location mismatch alone isn't enough to establish a leak.
4. Check again after making changes. Apply the settings as directed by your client, then check your public IP and DNS again. If you need help, note your connection mode and the error message, and redact account details and subscription links first.

To troubleshoot your client setup, read the Getting Started Guide. If your connection isn't behaving as expected, see the FAQ or describe the issue in a support ticket.