Browser connection check

Check your IP and confirm your current connection.

Check your current connection, then switch routes and check again. Results reflect this browser request only—not the connection used by every app.

VPNBegin · Current connection

Waiting for a check. Enable JavaScript to look up your current connection.

Public IP address
Temporarily unavailable
Country / region
Temporarily unavailable
ISP / Internet provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Proxy status comes from the category returned by the lookup service. It doesn’t indicate whether your connection is secure or whether DNS is leaking.

What this information means

Use this as a starting point for checking your connection, not as a complete network diagnostic report.

Public IP: where this request comes from

This is the public address seen by our server. After you connect a client, the address shown here will usually change if this page’s request uses an international route. If your rules send this page’s traffic directly, the address may stay the same. Check which rule applies to this page before deciding whether the connection is working.

Country, region, and ISP: details associated with the address

Location data comes from an IP geolocation database, and the ISP is the provider associated with that address. The address may belong to a data center or network operator, and location records can take time to update. This is not device location data and can’t confirm where you are physically located.

Proxy detection: a classification signal, not a verdict on your connection

“Proxy detected” means the lookup service classified this address as proxy-related. “No proxy detected” only means the service didn’t return that classification; it doesn’t prove the request used a direct connection. If the service doesn’t return this field, this page shows “Temporarily unavailable” rather than guessing.

No change after switching? Check your routing rules

Make sure your client is connected, then check the rule and route used for this page’s request. With split tunneling, other apps may use different routes; browser extensions can also change the browser’s connection path. Compare using the same browser and rules to make it easier to identify what changed.

Check for DNS leaks

An IP lookup and a DNS check are not the same thing. This page does not run an active DNS leak test.

DNS translates domain names into network addresses. Even if web traffic uses your selected route, DNS requests may take a different path. Conversely, a DNS server in a different region from your exit point doesn’t by itself prove that a leak occurred.

  1. Start by defining what you expect. Check your client’s DNS, routing, and direct-connection settings. Using local DNS for local websites may be part of your rules; not every DNS result from a different region is a problem.
  2. Check your browser settings. See whether Secure DNS or a separate proxy extension is enabled. These settings may differ from your client’s. Before troubleshooting, note your current settings, then adjust them according to your client’s instructions.
  3. Review request logs. If your client provides diagnostic information, check how the destination domain was resolved, which rule matched, and which route was actually used. Don’t judge the DNS path solely by whether a page loads.
  4. Cross-check with a dedicated test. If you use a trusted DNS testing tool, first find out what data it collects, then compare the DNS providers before and after connecting. Differences in region need to be understood in the context of your rules; they aren’t conclusive on their own.

This page only checks your browser’s connection details. It won’t claim “no DNS leaks” without running a test. If a site won’t load or only some apps are affected, see our troubleshooting guide.