VPN test

Is your VPN working?

Compare the address, network owner, protocol, and browser exposure before and after you connect. The detector prioritizes explainable evidence and low false-positive rates.

Current observation

Observed connection

No positive signal was found in the available free data. This does not prove that no VPN is in use.

IPv4 216.73.217.140
IPv6 Checking…

Privacy assessment Live
Current verdict No VPN evidence
Known VPN relay
No match
Tor exit node
No match
Hosting network
No match
View detection methodology
Location estimate Location unavailable City data may be unavailable or imprecise
Network Network owner unavailable No reverse hostname
Connection IPv4 No hosting-network match

Evidence

Result basis

No matching VPN or Tor record.

Unlisted and private VPNs may not be identified.

How to use this result

Connection change and VPN detection are different tests.

First: did the route change?

Save the current observation as a local baseline, connect your VPN, and reload. A full tunnel normally changes the public address and network organization. Country may stay the same when you choose a nearby server.

If nothing changes, check split tunneling, browser proxy extensions, and the VPN kill switch. Repeat after switching between Wi-Fi and mobile data.

Second: is the exit recognized?

An exact relay-list match is strong evidence. A hosting ASN is only context because ordinary servers and corporate gateways use the same infrastructure.

A working VPN can still display “No VPN evidence” when its exit is new, private, residential, dedicated, or absent from available free sources.

Local tests

Browser exposure

01

WebRTC candidates

Find public addresses exposed by the browser.

Not run
02

IPv6 route

Check whether an IPv6 path is available.

Not run

DNS leak testing requires controlled DNS infrastructure and is not included.

External links

VPN providers

Provider links do not affect the diagnostic.

Reference

Practical network privacy guides