Privacy
What the checks do
The six checks run in your browser. Most of them work by having your browser contact a server and seeing which of your addresses it reports. Any other company's service listed here receives your IP address when your browser contacts it, and its own privacy policy applies.
- Your addresses. Your browser connects to
v4.x.ismyvpnworking.com, which can only be reached over IPv4, andv6.x.ismyvpnworking.com, which can only be reached over IPv6. Each answers with the address the connection came from. These requests are not logged. - Who owns them. Your browser sends those addresses to this site, which looks up the network's owner and location in copies of DB-IP's IP to ASN Lite and IP to City Lite databases, and checks them against published lists of VPN, data-centre and Tor exit addresses, all stored on this server. No request is sent to anyone else, and the addresses are not written to a file or a database beyond the server log described below.
- WebRTC. Your browser contacts the STUN servers
stun.l.google.com(Google) andstun.cloudflare.com(Cloudflare), the same way a video call does, and lists the addresses they report back. - Time zone. Your browser's time zone is read in the browser and is not sent anywhere.
The results are shown to you and not sent to this site, apart from the DNS check described below.
Your saved real connection
If you press "Save my real connection", the IPv4 and IPv6 addresses, network and location found at that moment, and the time, are stored in your browser's local storage. They are not sent to this site. "Forget it" deletes them. The site sets no cookies of its own.
The DNS check
Your browser looks up six made-up names under x.ismyvpnworking.com, such as 3fa94c0d81be22a7-0.x.ismyvpnworking.com. The first part is random and new each time the checks run. Because nobody has looked these names up before, the DNS resolver your device uses has to ask this site's DNS server directly.
For each of those lookups the DNS server records the random part, the query type, the time, and the IP address of the resolver that asked. That is usually your VPN's resolver, your internet provider's or a public DNS service's, and not your own address. Some resolvers also pass along part of your own address, known as EDNS Client Subnet (for example 72.201.14.0/24). If yours does, that is recorded too.
The page then asks this site which resolvers came for its random name, and shows them with their network and country, looked up in the same DB-IP copies.
These records are deleted within ten minutes. Lookups of other names under x.ismyvpnworking.com are answered and not recorded.
Your browser also requests each made-up name from this server over HTTPS. Those requests appear in the server log described below.
Server logs
The web server keeps an access log for this site. Each line holds the client IP address, the date and time, the requested address including any query string, the HTTP status, the response size, the referring page and the browser's User-Agent string. There is also an error log, which can contain the client IP address and the requested address.
Logs are rotated daily and seven are kept, so entries are deleted within seven days. A copy also goes to the server's container log, which is capped at a few tens of megabytes and holds well under a day.
The logs are used to run and protect the site. An address that makes requests no ordinary visitor makes is blocked for 24 hours. Logs are not shared and not combined with other data.
Advertising
The page shows Google AdSense ads. Google, and other advertising companies that Google works with, use cookies to choose ads based on your earlier visits to this site and to other sites. You can turn off ads personalised in this way: for Google, in Google's My Ad Center; for other participating companies, at aboutads.info or, in Europe, youronlinechoices.eu. Google describes how it uses data from sites that show its ads at policies.google.com/technologies/partner-sites.
Content loaded from other sites
The fonts are served from this site. Besides the STUN servers the WebRTC check uses, the only other company's content is advertising: the main page loads Google's AdSense script from pagead2.googlesyndication.com, which loads the ads from further Google servers. These servers receive your IP address, your User-Agent and usually the address of the page, and Google can set and read its own cookies through the ads.
Sharing
The records described here are not sold or shared. The site's operator has access to them.