Your browser’s public IP address

IP Lookup and Checks

Check once before connecting, then again after switching routes. First see where your browser is accessing the internet from, then decide whether to adjust your connection.

Current connection details

Lookup via our API

Waiting for lookup. Enable JavaScript to get your current connection details.

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

Results reflect only the connection used for this lookup request; other apps may use a different route. This tool does not automatically check for DNS leaks.

What this information means

Public IP address: the source websites see

This is the public IP address received by our lookup API, not your device’s local network address. After you connect to a route, the address will usually change if your browser traffic goes through it. Split-tunneling rules, browser proxy settings, and differences between IPv4 and IPv6 paths can cause different requests to show different addresses.

Location and ISP: useful for comparison, not precise location data

The country or region comes from an IP geolocation database. The ISP is the provider or network organization associated with the address in that database. Database updates can lag, and the reported location does not necessarily match your device’s physical location. A data center or network operator name is not automatically a sign of a problem; consider it alongside your selected route and actual browsing experience.

Proxy detection: a database result, not a connection switch

“Proxy detected” means the API flagged the current address as a proxy. “No proxy detected” means only that no such flag was returned this time; it does not prove that your connection is inactive. If the API does not provide this field, this page will show “Temporarily unavailable” rather than treating missing data as a negative result.

A location that matches your expectations does not guarantee access to every website or AI tool. Services may still make decisions based on your account region, access rules, and their own risk controls.

DNS Leak Checks

DNS translates domain names into network addresses. An IP lookup only observes web requests and cannot, on its own, confirm that DNS requests are using the expected route. Checking for DNS leaks requires looking at client settings and the actual resolution path. This page does not present a single IP lookup as a complete test.

  1. Establish a baseline. Note your connection details before connecting, then connect to the route you want to check and run the lookup again. Confirm that the client shows a successful connection and compare the location shown here. If it hasn’t changed, first check whether your browser is covered by the split-tunneling rules.
  2. Check your DNS settings. In your client, review DNS, domain resolution, and related routing settings to confirm that resolution requests are handled as expected. If secure DNS is enabled in your browser, check its configuration too, so the browser and client aren’t using separate resolution paths.
  3. Clear the cache and check again. After changing settings, reconnect and clear the DNS cache using the method provided by your operating system or browser, then reopen the page you want to check. Old cached results can affect comparisons, so don’t draw conclusions from a single visit.
  4. Review diagnostic details. If your client provides DNS diagnostics, check which resolver and route it actually used. A difference between the resolver’s location and your public IP location does not necessarily mean there is a leak; what matters is whether requests left the expected path. If you’re still unsure, share redacted settings and details of what you observed with support.

If you’re connected but websites won’t load, or only one app is having trouble, see the troubleshooting guide. For a first-time setup, use the getting started guide to check your client and subscription settings.

Lookup privacy and troubleshooting

We do not log lookup requests. HiHiVPN’s service is described as “no logs.” This page gets connection details through our own API and does not use a third-party public API as a fallback. The API must receive the public IP address of your current request to return the corresponding results. You won’t be asked to enter account details.

If you see “Temporarily unavailable,” your network may not be able to reach the API, the API may have timed out, or the response may be missing a required field. This does not by itself mean your connection has failed. Try again later or switch routes and retry. The page will not fill in missing results with sample addresses.

The copy button copies only your public IP address; it does not include account information. Before sharing a screenshot, hide your IP address and any other personal information you don’t want to disclose. For help, use a support ticket in the user dashboard and include your client platform, selected route, and the error you’re seeing. Don’t share your password or subscription link. See the Privacy Policy for details.