Free · No sign-up · Nothing stored
Proxy and privacy checks that say what actually happened.
Six checks for the questions a proxy or VPN raises. They run on this page, one under the next. A local address is not called a leak.
- No false leaksA VPN tunnel, carrier, or .local address is never printed as a leak.
- Reasons, not a gradeEvery result names the signal behind it. Nothing is scored without one.
- Nothing keptNo account, no stored results, no proxy passwords in a log.
IP Lookup
The address this page actually loaded from, the network that owns it, and a score built only from the checks on this page.
Checking
Reading the address this page loaded from.
WebRTC is gathered in the same check, so a local tunnel address is not reported as a leak.
Your address on this request
Reading…
- Family
- This request on this request
- Network
- —
- Country
- —
The city is left out on purpose. An IPv4-only and an IPv6-only hostname can be configured; until then the other family is not invented.
IP score
Checking the signals that move the score.
A signal that has not come back yet is not treated as clean.
Browser Fingerprint
Sites do not flag a hash. They flag signals that disagree: the clock, the language, the platform, and the WebRTC address.
Checking
Comparing the signals sites actually compare.
A library hash is collected afterwards. It is an id, not a uniqueness score.
Library ids
These are ids from two libraries. They are not a uniqueness score, and they are not uploaded.
- FingerprintJS
- Computing…
- ThumbmarkJS
- Computing…
Bot Detection
Three answers: a normal browser, a privacy browser, or a browser a program is driving. The signal that decided it is named.
Checking
Reading the automation flag.
DevTools is not timed, and a privacy browser is not scored as a bot.
DNS Leak Test
Which resolver answered, and whether that network is the one this page loaded from. A public resolver such as Cloudflare is not called a leak on its own.
Checking
Asking which resolvers answer.
Twelve lookups run, which is the extended test. A public resolver is named, and it is not called a leak by itself.
This sees the resolver this browser used for these lookups, not every program on the computer.
WebRTC Leak Test
A leak is a public address that is not the one this page loaded from. A private, carrier, or .local address is the tunnel or the LAN, and it is not called a leak.
Checking
Gathering WebRTC addresses.
Host, server-reflexive, and relay addresses are kept separate. Only a different public address is a leak.
A private address, a carrier address, a .local name, or a relay is listed so you can see it, and it is not the word Leak. This check is this browser, right now.
Proxy Checker
Paste your own proxies. Each one is checked for a connection, the exit address, and the forwarding headers it actually sends.
Ready
Paste your own proxies, then check them.
HTTP, HTTPS, SOCKS4, and SOCKS5. The password is used for the check and not stored. The only target is this site.
Questions people actually ask
Do these checks need an account?
No. Each check runs in the browser, or against a proxy list you paste. Results are not stored.
Why do other test sites disagree with each other?
They use the word leak for different things. A private tunnel address, a public DNS resolver, and a real second public IP are three different outcomes. These pages separate them.