VPN65 · NETWORK CHECK

Current Public IP Lookup

See the network route used by this browser request. Query again after connecting to check whether your public IP has changed. Results reflect only this browser’s route to our API.

IP Details

Lookup via our API

Checking your current network route…

Public IP
Checking
Country / Region
Checking
Internet Service Provider (ISP)
Checking
Proxy detected
Checking

What These Results Mean

Public IP and Location

Your public IP is the address our API sees for the request, not your device’s local network address. Location comes from an IP database and usually indicates the region of the network exit point. It does not show your device’s precise location and may differ from the name of your selected route.

Internet Service Provider

The ISP field identifies the network operator associated with the exit IP. When using an accelerated route, it may show the name of a data center or exit network rather than your usual broadband provider. A missing value does not mean the connection failed.

Proxy Detection

The proxy indicator depends on the detection data available to our API. A detected proxy does not mean your connection has a problem; no proxy detected does not prove that all traffic uses the same route. If the API does not return this field, this page displays “Unable to retrieve.”

DNS Leak Checks

This page checks the route used for HTTP requests; it does not actively test DNS resolvers, so it cannot confirm that you have passed a DNS leak test. DNS translates domain names into IP addresses. DNS queries and web requests may take different network routes, so check them separately.

  1. Check Your Client’s DNS Settings

    Open your client settings and review the DNS resolution method and split tunneling rules. Confirm that DNS queries are handled by the client according to your current connection mode. Setting names vary by client. If you’re unsure, consult its documentation rather than entering an unfamiliar DNS server address.

  2. Check Your System and Browser Settings

    Check whether DNS is manually configured on your system and whether your browser has Secure DNS enabled separately. The browser’s own DNS settings may differ from your client’s policies. Assess the actual routing rather than concluding there is a leak based only on the resolver’s name.

  3. Verify the Route Using DNS Logs

    If your client provides DNS or connection diagnostic logs, check how DNS queries are handled when you visit a domain. Further verification requires a dedicated test that shows the actual resolver. Without that evidence, treat the result as “not confirmed”—don’t assume everything is clear just because your public IP changed.

Check your public IP and DNS route again after switching networks or changing settings. For help confirming the connection process, read the subscription setup guide. If you have connection issues, see the FAQ.

Privacy Notice

We do not log queries. This page retrieves your current public IP through an API on our own domain and does not use third-party public lookup APIs. If the API is unavailable, the page displays an error instead of switching to an external service.

“Copy Results” writes the current results to your clipboard only when clicked. Before sharing a screenshot or diagnostic details, consider whether the full IP address needs to be visible, and avoid sharing account details or subscription links at the same time. See our Privacy Policy for more information.

Try It Free