Public IP Check

What These Results Mean

Public IP: the address seen by our service

Your public IP is the address used by this request to reach our service, not your device’s address on the local network. If your client uses split tunneling, our service and other apps may take different routes. A changed address here only confirms that this request took a different route; it doesn’t show that other apps are using the same route.

Location and ISP: network details from IP databases

The country or region is based on IP geolocation data and doesn’t indicate your device’s actual location. The ISP is the network provider associated with the address; it may show a carrier, data center, or hosting provider rather than VPNGift. IP databases can lag behind changes, and the location shown may differ from the one reported by a website.

Proxy Detection: an Indicator, Not a Security Verdict

The proxy result reflects how the lookup service classifies the current IP. “No proxy detected” doesn’t mean you aren’t using a proxy, and “Proxy detected” doesn’t mean the connection has a problem. If the service doesn’t provide this field, this page shows “Temporarily unavailable” rather than inferring a result from the IP address or ISP name.

For connection steps, see the Getting Started Guide, or run another check on this page. Results from before a network change don’t automatically reflect the new connection.

How to Check for DNS Leaks

DNS translates domain names into network addresses. Checking your public IP and checking DNS are separate: even if web traffic goes through your chosen route, domain lookups may still use your local network. This page doesn’t collect DNS resolver details or report whether a DNS leak test has passed.

1. Review your client’s DNS and routing settings.

   Check whether your current configuration handles DNS, and which resolution methods are used for direct and proxied domains. Setting names vary by client, so refer to the client’s interface. An enabled connection toggle alone doesn’t confirm the DNS route.

2. Check your browser’s Secure DNS settings.

   A browser may use encrypted DNS independently, so its lookup route may not follow the system settings. Note the current settings first, then compare them with your client configuration. Avoid changing multiple options at once, which can make the cause harder to identify.

3. Check the actual DNS resolution path.

   Use your system network settings, client DNS logs, or connection records to see which resolver handles a domain. If you use a dedicated DNS testing tool, first review how it handles data, then compare results before and after connecting.

4. Evaluate results against your expected routing rules, not just location.

   A resolver in a different location from your public IP isn’t necessarily a leak; direct-routing rules may intentionally use local DNS. Focus on whether domains that should use the proxy are unexpectedly sent through a DNS route that doesn’t match your configuration.

For help checking subscription imports, connections, and routing settings step by step, read the Complete Guide. Before sharing screenshots with support, hide subscription links and account credentials.