View your IP address, location, and ISP. Check before and after connecting to see whether your browser’s public IP has changed.
Ready to check your current connection.
Copy your IP address once it appears.
Results reflect this browser request only. Fields with no data show “Temporarily unavailable”; this does not mean the corresponding attribute is absent.
The public IP is the address the request appears to come from to VPNCar’s API. It is not your device’s local network address. Location is based on an IP geolocation database, which may change as the database is updated and cannot pinpoint your device’s exact location.
The ISP field usually identifies the network operator associated with your public IP. When a proxy is enabled, it may show the provider for the route’s exit server rather than your local broadband provider. This field alone says nothing about connection speed or route quality.
Detection depends on the data available to the API. “Not detected” does not guarantee that your connection is not using a proxy, and “detected” is not a security risk assessment. Check the client status, changes to your public IP, and actual access results together.
This page checks your public IP. It does not run an automated DNS leak test or report a “pass” result.
After connecting to your chosen route, check your public IP again. Review the client’s current mode and whether the service you’re checking matches a proxy rule. A changed IP shows that this request took a different route; it does not prove that DNS queries followed the same route.
Check the DNS and remote resolution settings in your client, then review your browser’s Secure DNS settings. Your browser, system, and client may use different DNS paths. Follow the client’s setup guidance to coordinate them; a setting’s name alone can’t confirm whether a leak is occurring.
For further verification, use a test that can observe the source of actual DNS queries. Compare the observed source with your expected network path. A different DNS provider and exit provider do not necessarily indicate a leak; public resolvers, caching, and rule-based routing can all affect the results.
If something seems wrong, note your platform, client mode, route location, and what happened, then submit a ticket through the user panel. Before sharing screenshots, hide your IP, account details, and subscription information. Never share your full subscription URL publicly.
VPNCar does not log queries. Lookup requests are sent only to VPNCar’s API; there is no fallback to a public third-party lookup API. Your public IP is still network information, so share it only with trusted support channels.
“Temporarily unavailable” means no usable data was returned. It does not mean your connection is down or that a leak has occurred. Try again later or reconnect and run the lookup again. If the problem persists, report it through the user panel. This page cannot replace connection diagnostics in your client.