Your address, whether your VPN and DNS actually hide you, and the fingerprint your browser leaves behind — measured by this page alone. No third parties. No prompts. Nothing stored.
Preparing collectors…
Straight answers
The verdict at the top compares three things a VPN should change: the network your IP belongs to, the time zone your browser reports, and where your DNS queries go. Toggle the VPN, press Re-run check, and watch exactly what changed.
A VPN can hide your address while your DNS lookups still go to your ISP — which then sees every site you visit. This page resolves a name that only its own nameserver answers for, so it can tell you precisely who asked. Run the leak checks
Canvas, WebGL, audio, fonts, screen and hardware details combine into a hash that can recognise your browser without a single cookie. You get the hash and every component that feeds it, so nothing is a black box. See yours
No. The report is computed for this visit and discarded. The server keeps ordinary access logs, like every web server — address, time, path — and nothing else. Nothing is shared with anyone.
curl wget.me prints your IP. /check is the VPN verdict, /dns the leak test, /port/22 a port check on your own address, /8.8.8.8 looks up any address. Output formats are frozen, so your scripts keep working. Terminal & API
Every row says where it came from, how reliable it is, and what it means. Guesses are labelled as guesses with a confidence, masked values stay masked until you reveal them, and the raw data behind any row is one tap away. Open the full report
Four checks a VPN should pass. Toggle it and re-run.
Resolving a name only our nameserver answers for…
Your browser resolves a random name under t.wget.me, a zone served only by this server’s own nameserver. Whoever asks for that name is your resolver — your ISP, a public resolver, or your VPN’s. If your traffic leaves through a VPN but the lookup came from your ISP, that is a leak.
Reading the first packets of this connection…
A passive observer on this server reads the first packets of your connection: the TCP handshake reveals the operating system that sent it (TTL, window, option order) and the packet size the path allows; the TLS ClientHello reveals the browser stack that started the handshake (JA4). Compared with what your User-Agent claims, they expose spoofed agents, VPN re-origination and TLS-intercepting proxies. Nothing is decrypted.
Checks whether a port is reachable on your own address, from here. Nothing else is ever probed.
A traceroute from this server towards your address, each hop named by network operator. Runs only towards you.
From a terminal: curl -L wget.me/dns · curl wget.me/wire · curl wget.me/port/22 · curl wget.me/trace
What can recognise this browser tomorrow without a cookie — the hash, what feeds it, and how an ad system would read it.
Every component, in the report
Prove private mode doesn’t hide you
Open this page in a private window (or on your phone via the code) and paste that window’s fingerprint here.
Round trip, download and upload, latency under load, a cold DNS lookup and a compute score — all against this server. Run it, toggle your VPN, run again.
The median of twenty small requests to this server, and the spread between the fastest and slowest of them. Jitter is what makes calls and games stutter even when the average looks fine.
Round trip measured again while the download saturates your link. A means under 30 ms extra; F means more than 400 ms — a connection that feels broken the moment anything uploads or downloads.
The time to resolve a name that has never been resolved before, under this site’s own zone. It measures your resolver’s full path, not a cached answer — and shows what a VPN’s resolver costs you.
Every observation with its source, reliability and meaning. Search it, filter it, copy any row.
What a normal web page has no way to read, no matter what some sites imply.
Every answer on this page is one curl away: plain text for terminals, JSON on request, output formats frozen.