Leak check
This page shows the addresses your browser reaches us from, over IPv4 and over IPv6. With your tunnel on, each should be an ironkeel server's.
| Family | Address we see | Whose |
|---|---|---|
| IPv4 | 216.73.216.212 | Not an ironkeel server |
| IPv6 | Check over IPv6 | |
"Not an ironkeel server" while your tunnel is on means your browser reached us over that family from another address: its traffic went around the tunnel, or through a proxy or relay of the browser's own, or our list of servers is wrong. Unless your browser uses a proxy or relay, tell us through support.
"No answer" means this page got no answer over that family within 10 seconds, so it could not check it; the cause can be on your side or ours. Without JavaScript each check is a link, and a family that does not reach us opens your browser's error page instead. An IPv6 address counts as a server's when it is in that server's /64, the block of addresses the server sends from.
The family your browser did not load this page over is checked through a name of this website that has an address of that family only. We use each address only to compare it with our servers' addresses and show it to you here, and we store and log none of it.
What this page can't show
- Which DNS server answers your lookups, and what your browser's WebRTC, which video calls use, tells a site. ipleak.net, a leak-check site we do not run, tests your browser for both: no DNS server or address it lists should be your internet provider's.
- Traffic other than this visit. Other apps and the system itself can take other routes, which this page cannot see.
- Any other moment, such as before the tunnel is up or while it reconnects.