Am I Using VPN
VPN / proxy
Checking…
Heuristic only — compares IP data and ISP names. Datacenter IPs and browser VPN extensions can skew results.
How to use
- Open the page with your VPN connected or disconnected — the headline updates automatically.
- Read HTTP public IP, WebRTC public IP, ISP, and the signal list in Details.
- Toggle your VPN and click Refresh to compare Likely yes vs Likely no.
FAQ
Am I using a VPN?
This page does not read your VPN app directly. It uses heuristics: whether your ISP/organization name looks like a VPN or datacenter provider, and whether HTTP and WebRTC report different public IPs (possible leak or split tunnel).
Why does it say likely yes on a normal home connection?
Some residential ISPs lease addresses from hosting ranges, or your ISP string matches datacenter keywords in our heuristic list. Treat the result as a hint and read the signal bullets.
Why does it say likely no while my VPN is on?
A well-configured VPN with consistent HTTP and WebRTC routing and a residential exit IP may show no strong indicators here. Use your VPN app’s status and a WebRTC leak test for certainty.
What is the HTTP vs WebRTC IP mismatch?
Most sites see your HTTP exit IP. WebRTC can discover addresses via STUN. If they differ while you expect one tunnel, WebRTC may be bypassing the VPN — see [WebRTC leak test](/tools/webrtc-leak).
Does this work on browser VPN extensions?
Extensions that only proxy browser traffic may still change the HTTP IP shown here. System-wide VPNs affect both paths more consistently.
Is my IP sent to your servers?
Public IP lookup uses the same /api/my-ip route as other tools on this site for geo and ISP — not for building a VPN database about you.
Introduction
Am I Using VPN gives a cautious answer — Likely yes, Likely no, or Uncertain — based on what your browser reveals about your public IP path and ISP name. It cannot see your VPN application’s on/off switch, but it surfaces the same clues websites and leak testers use.
People turn VPNs on for privacy, region access, or work policy — then wonder if the tunnel is actually active, or if WebRTC is exposing their real line. Comparing HTTP and WebRTC public addresses alongside ISP strings is a practical first check before diving into dedicated leak tools.
What the heuristic looks at
| Signal | Interpretation |
|---|---|
| ISP/org matches VPN/datacenter keywords | Exit node may be a VPN provider or cloud host |
| HTTP IP ≠ WebRTC public IP | Possible VPN split tunnel or WebRTC leak |
| HTTP IP = WebRTC IP | Consistent public path (still compatible with VPN) |
| Uncertain | Lookup failed or inconclusive signals only |
Likely yes vs likely no
Likely yes does not prove criminal intent or misconfiguration — it means “this session looks like a VPN, proxy, or datacenter exit.” Likely no means no strong indicators fired, not a guarantee that no VPN exists.
Corporate networks, cloud desktops, and privacy relays can trigger false positives. Consumer VPNs with leak protection can trigger false negatives.
Common use cases
- After connecting a VPN — refresh and confirm ISP name changed away from your home broadband brand.
- Leak debugging — spot HTTP/WebRTC mismatch before streaming or gaming.
- Support — document what the browser reports when a site geo-blocks incorrectly.
- Compare with dedicated tools — pair with what is my public IP and WebRTC leak test.
Best practices
- Run the test twice: VPN off, then VPN on, and compare ISP and IPs.
- Fix WebRTC mismatches in the VPN client or browser before trusting “private” browsing.
- Remember DNS leaks are not fully covered here — use what is my DNS server separately.
- For raw address and location, open what is my IP.