Am I using a VPN?
Check network-name, ASN and Cloudflare WARP clues for your public IP. These free signals are estimates, so compare them with WebRTC and IPv6 exposure checks before drawing conclusions.
Your visible network location is approximate. It does not reveal an address hidden behind a VPN.
Detection details
VPN, proxy, Tor and hosting are separate signals. None is a security verdict.
Network-name, ASN and WARP clues are estimates. Without a provider lookup, VPN, proxy and Tor database classifications remain unknown. Data use · How VPN detection works
VPN detection and leak testing answer different questions
A detection database reports whether an address has been associated with a VPN, proxy or Tor exit. A leak test asks whether this browser exposes additional addresses or uses different IPv4 and IPv6 exits. Neither test proves that every application on your device is protected. Start with the visible address, then compare your connection before and after turning on a VPN.
Read each signal separately
- VPN detected: the configured provider classifies this request IP as a VPN address. A false positive is possible.
- VPN not detected: the provider returned a negative VPN classification. An unlisted VPN can still be in use.
- VPN or tunnel likely: the network name or a WARP trace is a clue, not an independent database confirmation.
- Proxy or Tor: separate routing classifications. They do not imply malicious activity.
- Hosting: the address belongs to a data-center network. A cloud server, corporate gateway or VPN may use it; hosting alone does not prove a VPN.
- Unknown: the lookup is not configured, failed, or lacks the relevant field. It is not a negative result.
Can this reveal my original IP or real location?
No. A correctly routed VPN presents its exit address to the website. IP geolocation estimates where that network appears to be; it does not reveal your home, GPS location or a hidden address. Our globe uses the coordinates of the request observed by Cloudflare. We do not invent a second location from a time zone or a WebRTC address.
Why can the detection concern IPv6 when my main address is IPv4?
IPNixa prioritizes an IPv4 readout when confirmed. A separate request to this website can nevertheless travel over IPv6. The classification identifies its own request IP so that IPv6 evidence is never presented as a verdict about an untested IPv4 address. A network change between requests can also invalidate a comparison; refresh and check the addresses again.
Which signals are available now?
Current free-only operation uses network-name, ASN and Cloudflare WARP clues. External VPN, proxy and Tor database classification is disabled, so those fields remain unknown. A residential-looking network does not prove that a VPN is absent. You can still compare addresses and inspect WebRTC and IPv6 exposure without a commercial classification service.
Where does the information come from?
The fast IP lookup uses Cloudflare request metadata. Optional provider detection uses proxycheck.io in a separate server request, with a timeout and a short cache. The source, checked time and cache status appear in the details. Without a configured provider, only clearly labeled network hints are available. Provider confidence describes the database observation, not your level of protection.
How is my data used?
When enabled, the provider receives the observed request IP. Our cache uses a secret HMAC-derived key and stores only classification fields and timestamps for up to 15 minutes for positive classifications or one hour otherwise. This is pseudonymous caching, not anonymization. Browser leak checks remain separate. Read the privacy intelligence disclosure for details.