Checks whether your browser exposes extra IP candidates through WebRTC. Modern browsers often replace local IPs with mDNS hostnames, which is not always a leak.
- Extra IPsWaitingā¦
- ResultWaitingā¦
See the public identifier websites receive, plus country, city, ISP, ASN, and a privacy-route estimate. To inspect another value, use the lookup tool.
Start with a 2-hour free VPN test, then buy access with crypto if the protected route works well for you.
Checks whether your browser exposes extra IP candidates through WebRTC. Modern browsers often replace local IPs with mDNS hostnames, which is not always a leak.
This basic check verifies whether a DNS-over-HTTPS service is reachable. It does not identify your active DNS resolver or confirm whether a DNS leak exists.
A probability-based estimate from ASN and provider signals: privacy service, proxy, Tor, relay, or hosting. This is not a definitive result.
This page answers a common question by detecting the public connection label your browser presents and enriching it with approximate country, region, city, postal code, time zone, provider, and Autonomous System Number. The snapshot loads first, while the map and privacy checks wait until later for better performance.
Geolocation is approximate by design. It reflects the route carrying your traffic, such as home broadband, a mobile carrier, a workplace gateway, or a privacy-service exit. If a tunnel is active, the details shown here usually belong to the exit server rather than your original connection.
Use the provider and ASN fields to confirm which route is visible to websites. After connecting to a VPN, refresh this page and compare the new country and owner. For allow-lists or server logs, copy the shown value and inspect it with the lookup tool or follow the ASN with ASN lookup.
This checker does not reveal your street address, name, device identity, or browsing history. It shows the public route your browser uses. Mobile carriers, corporate gateways, VPNs, proxies, and data-center exits can all make the visible location differ from your physical location.
The page checks the public connection details available to a website request, then enriches that result with location, provider, ASN, and browser-side privacy checks. It also tries to show IPv4 and IPv6 separately because many modern connections use both. If one version is missing, that does not always mean there is a problem; it may simply mean your provider, router, browser, or privacy app prefers one route.
The browser loads the page, the site reads request metadata and public lookup data, then the interface fills in the snapshot, map, provider fields, and privacy indicators. Heavier checks wait until lower sections are visible so the first result stays fast on mobile.
Use this page to confirm a VPN exit, copy your current public value for an allow-list, check whether travel or mobile data changed the visible country, verify provider details before contacting support, or compare results before and after changing router settings.
If the country or city looks wrong, refresh once and compare the provider name. Geolocation databases can lag behind routing changes, and mobile carriers often route traffic through regional gateways. If the result changes after connecting to a VPN, that usually means websites now see the exit server. If WebRTC or DNS checks do not load immediately, scroll to the privacy section and allow a few seconds; those checks are delayed so the main result appears quickly.
Use IP Lookup when you want to inspect a value from server logs or a firewall rule. Use ASN Lookup to understand the operator behind a route. Use the IPv6 test when one device works differently from another, and use the WebRTC leak test after changing VPN or browser privacy settings.
It is the public identifier websites see when your browser connects. This page shows the visible value, country, city, ISP, and ASN.
It estimates whether the route looks like a VPN, proxy, relay, or hosting provider using ASN and ISP signals. It is a heuristic, not proof.
Geolocation is approximate. Public databases may point to your provider, mobile carrier hub, or privacy-service exit rather than your exact location.