Public IP
Not checked yet- Not checked yet
FREE BROWSER-BASED DIAGNOSTICS
Your VPN.
Put to the test.
See the public IP your browser presents, inspect browser-level address exposure, and test connection responsiveness — in one clear report.
No account. No installation. Results aren't saved by default.
Diagnostic Console
DIAGNOSTIC CONSOLE
Connection
Not checked yet- Not checked yet
Browser Exposure
Not checked yet- Not checked yet
Usually takes a few seconds
What you can check
Each tool focuses on one aspect of your connection. Run them individually or use the quick check above for all three.
What Is My IP?
See the public IP address websites see, with approximate location and network provider details.
Run IP check →WebRTC Leak Test
Check if your browser exposes local or public IPs through WebRTC, even when using a VPN.
Run WebRTC test →Connection Check
Measure HTTPS round-trip time to this site — not a ping, but a real TLS connection test.
Run connection check →A result you can understand
ObservedExample result — not your actual data
- Public IP observed by this site
- 203.0.113.42
- Approximate location
- Sydney, AU (ISP/VPN exit region)
- Network / ASN
- AS13335 Cloudflare, Inc.
How it works
- 1
Run the tests
Click "Run quick check" — we'll fetch your public IP, measure HTTPS round-trip time, and inspect WebRTC candidates in parallel. Each test takes a few seconds.
- 2
Review observations
Each check returns a clear status: Observed, No issue observed, Needs review, Inconclusive, or Unavailable. We explain what was seen, what it means, and what we cannot prove.
- 3
Follow the guidance
Each result includes a limitation statement and a practical next step. No security scores, no fake guarantees — just evidence and honest interpretation.
What this test cannot prove
Your VPN is "secure" or "working perfectly"
We only observe what this browser reveals to this website. We cannot test your VPN's encryption, kill switch, logging policy, or traffic from other apps on your device.
"No leaks" guarantee
A clean WebRTC test in one browser doesn't prove other browsers, apps, or system-level traffic aren't leaking. IPv6, DNS, and routing table leaks require different test infrastructure.
Your exact VPN provider or protocol
We see the exit IP and its network operator (ASN). Many VPNs share hosting infrastructure. We cannot definitively identify your commercial VPN provider or tunnel protocol (WireGuard, OpenVPN, etc.).
Your physical location
IP geolocation maps to the VPN/ISP exit point, often a data center. It does not reveal your home address, city, or GPS coordinates.
FAQ
- Is this really free? What's the catch?
- Yes, completely free. No account, no upsell, no data collection by default. We may add optional account features later for history, but the core diagnostic will always be free and anonymous.
- Why does my IP show a different country than my VPN?
- VPN providers often use hosting companies (AWS, DigitalOcean, etc.) whose IP blocks are registered to the hosting company's HQ, not the VPN server's physical location. The ASN/network org field usually reveals the actual hosting provider.
- The WebRTC test shows a different IP — is my VPN leaking?
- If the WebRTC public IP differs from your HTTP IP, your browser may be exposing your real ISP address or a different VPN interface. This is a known WebRTC behavior. Disable WebRTC in browser settings or use an extension like "WebRTC Control" to prevent it.
- Why don't you test for DNS leaks?
- A real DNS leak test requires controlled authoritative DNS infrastructure that can observe which resolver your browser uses. Without that infrastructure, any "DNS leak test" would be unreliable. We'll add it when we can do it properly — not before.
- Do you store my IP or test results?
- No. Results stay in your browser memory only. We don't log IPs, don't save scan history, and don't send diagnostic data to analytics. See our Privacy Policy for details.