Internet privacy & network intelligence toolkit
VPN checker: is my VPN working?
Check VPN, proxy, and Tor signals for your connection or a public IP. Database recognition and a working VPN tunnel are different questions; compare your exit addresses as well.
Your current IP is the HTTP exit used to reach this site. Lookups use external IP intelligence services.
Compare before and after connecting
Record your public IP and ISP before connecting, then enable the VPN and repeat the check. Confirm the exit changes as expected and inspect IPv4, IPv6, WebRTC, and DNS separately. A browser proxy extension may only route part of the browser’s traffic.
VPN signals are not a security guarantee
Residential exits may go unrecognized, and data-center addresses do not necessarily run a VPN. Providers may disagree. Low or unknown signals describe the available evidence; they do not prove anonymity, encryption, or the absence of leaks.
Frequently asked questions
Why is my connected VPN not detected?
The database may not cover that exit or may be outdated. First verify the public exit changed, then check DNS, WebRTC, and dual-stack paths separately.
Is Tor the same as a VPN?
No. Tor uses a multi-hop anonymity network, while a VPN tunnels traffic to a server. We display the signals separately; an IP alone cannot reveal the entire connection path.
Continue checking your network
Proxy checker
Check a public IP for proxy, residential proxy, VPN, Tor, and hosting signals. Review source evidence and understand the limits of proxy detection.
Open tool →DNS leak test
Use one-time hostnames and authoritative DNS observations to inspect recursive resolver exits. Compare your expected VPN path and understand test limits.
Open tool →WebRTC leak test
Test public WebRTC candidates through multiple STUN servers and compare them with your HTTP exit to investigate possible VPN or proxy bypass paths.
Open tool →