Is my VPN working?
Run every leak check at once and get a single verdict. Test it with your VPN off, then on, and compare.
| Public IP & location | … |
| IPv6 exposed | … |
| WebRTC leak | … |
How to use the is my vpn working?
- Load this page with your VPN OFF and note the IP and location.
- Connect your VPN and reload.
- Confirm the IP/location changed and that IPv6 and WebRTC show no leak.
How to use this
Run it once with your VPN off and note the IP/location, then again with it on. When connected, the IP and country should be the VPN's, and IPv6/WebRTC should show no leak. If your real address still shows through, one of the individual tests will tell you where.
Code & API examples
Use this from the command line or your code.
Check exit IP (curl)
curl https://vpn.golf/api/tools/ipResolver check (dig)
dig +short txt o-o.myaddr.l.google.com @ns1.google.comSee all endpoints at /api/tools/.
Frequently asked questions
Your public IP and location should change when connected, and there should be no IPv6 or WebRTC leak exposing your real address. This tool checks all of that in one pass and gives a single verdict.
Common causes are a dropped tunnel, a split-tunnel rule excluding your browser, or an IPv6/WebRTC leak. Run the individual tests to isolate which one it is.
Run it once with the VPN off and note your real IP and location, then connect and run it again. Everything should change; anything that still shows your real details is a leak.
Four things at once: your visible IPv4, any IPv6 that bypasses the tunnel, the DNS resolver answering your lookups, and whether WebRTC exposes a local or public address to JavaScript.
Your traffic is tunneled but your device is still sending DNS lookups to your ISP's resolver outside the tunnel. The destinations you visit are exposed even though the data itself is encrypted.
It can guess. Datacenter IP ranges, a timezone that doesn't match the exit country, and other signals hint at VPN use. This tool flags the mismatches a site would notice.
No. It means your IP and DNS aren't leaking, which is the network layer. Browser fingerprinting, logins, and cookies can still identify you regardless of your IP.
Yes. Leak behavior is per-device and per-browser — a phone, a laptop, and two browsers can each behave differently depending on IPv6 support and WebRTC settings.
Often IPv6 or a split-tunnel/per-app routing difference. Desktops frequently have dual-stack networking that a VPN may not fully cover, while the mobile app routes everything.
No. vpn.golf keeps no logs; the checks run against your live connection to produce a verdict and nothing about the result is stored or linked to you.
Only if you re-run the test during the drop. A kill switch is what protects you between tests by blocking traffic the instant the tunnel fails, so leaks can't slip out unnoticed.
It's built to. Each hole tunnels IPv4 and IPv6, runs its own no-log resolver inside the tunnel, and your keys are generated client-side — so there's no IP, DNS, or key data to leak.
Related tools
Want to hide your IP for real?
vpn.golf is a no-logs WireGuard VPN. Pick a hole, take the shot.
Step up to the tee — free