System Properties
Your machine as the edge sees it: everything one HTTP request from your browser revealed to this site. None of it is logged, none of it is stored. Close this tab and it's gone.
🖥 Device Manager · this connection
- 🖧 Network adapter Anycast edge, colo … (…, AS…)
- 🔒 Security coprocessor … …
- 🌐 Transport …
- 🌍 Region …, … (…)
- 🖥 Client … on …
What guards all this: Security Center
Network adapter
- IP address
- …
- ISP / ASN
- … (AS…)
- Country
- …
- Region
- …
- City
- …
- Timezone
- …
- Approx. coords
- …, …
- Cloudflare colo
- … (nearest CF data center serving you)
- Round-trip
- …
- Delivery rate
- … (most recent edge estimate for this connection)
Transport and security
- HTTP version
- …
- TLS version
- …
- TLS cipher
- …
- Accept-Encoding
- …
- Stream priority
- …
- TLS extensions
- … (SHA-1 of the extension list)
Computer
- Best guess
- … on …
- User agent
- …
- Languages
- …
- Do-not-track
- …
This session
- Received at
- … (when the edge rendered these values)
- Referrer
- … (read by your browser from what it sent with this page)
- Cookies sent
- …
- Cloudflare ray
- … (the edge's id for the request that fetched these values)
The request for these values failed, so they stay unknown rather than assumed. /whoareyou/values.html has them for your request.
Edge Trace
Seven things Cloudflare's edge knows about this connection that it never tells the worker. request.cf carries geography, TLS version and protocol, but not whether your SNI was encrypted, nor whether you arrived through WARP. Those live only in /cdn-cgi/trace, so your browser fetches this section for itself, from this same origin, after the page has loaded.
- Encrypted SNI
- …
- Key exchange
- …
- HTTP version seen
- …
- Through WARP
- …
- Through Zero Trust
- …
- Browser isolation
- …
- Edge sliver
- …
Fetching…
What I Can't See
- Your DNS resolver or protocol. Your resolver answers the name before the request reaches this site, so I only see the IP that connected. HTTP/3 implies a modern network stack that probably speaks DoH, though I can only infer that; the request itself never carries your resolver.
- Your real identity unless you've told me. An IP isn't a name.
- The rest of your browsing. I see this one request, nothing else.
- The contents of any encrypted data outside this HTTP session. TLS is doing its job.
Want This To Leak Less?
- Use a VPN or Tor. Either one changes your IP, ASN, and geo. Tor also anonymizes most fingerprintable details.
- Use a private browsing window. It drops cookies and language hints, somewhat.
- Set
DNT: 1or use a browser that does. Almost no servers honor it, though it's still a signal. - Strip the user-agent. Some browsers and extensions let you fake or hide it, which shrinks your fingerprinting surface.
About this page: The page itself is built once at deploy and is byte-identical for everybody, which is what lets it arrive compressed against bytes your browser may already hold. Everything above that describes you comes from a second request, to
Your browser never speaks to a third party. Two requests leave this page after it loads, both to this same origin: the values, and the Edge Trace section's read of
Every script on this page is mine, and that is newer than it sounds. From 2026-08-06 the Cloudflare edge injected a 47KB WebMCP bridge of its own into every document here, after this worker had finished with it, which is why View Source used to show a tag no file in the repository contained. It is off. What builds the tool catalogue now is
Two measurements retired the bridge rather than a preference. It never ran on the busiest page here at all:
Analytics: none. No page loads a Web Analytics or RUM beacon, and this Worker exposes no browser-timing collector. Page-load timings are not sent to Cloudflare.
/whoareyou/values.html on this same origin, which the Cloudflare edge renders from that request and nothing else. So the values describe the request that fetched them: normally the same connection, IP and TLS session as the page, with a slightly later clock and its own ray id. The referrer is the one field that request would get wrong, since its referrer is this page, so your browser fills that row in from what it sent with the page. Your browser never speaks to a third party. Two requests leave this page after it loads, both to this same origin: the values, and the Edge Trace section's read of
/cdn-cgi/trace, because those seven fields are the ones the worker is never told. One call leaves the server: an RDAP lookup to your IP's registry, which the edge caches for 24h so visitors from the same block don't re-hit ARIN. The data above lives for as long as it takes to render, then nothing writes it to storage. View-source if you want, since it's a single JavaScript file you can read end-to-end. Every script on this page is mine, and that is newer than it sounds. From 2026-08-06 the Cloudflare edge injected a 47KB WebMCP bridge of its own into every document here, after this worker had finished with it, which is why View Source used to show a tag no file in the repository contained. It is off. What builds the tool catalogue now is
/webmcp.js, which is in the repository and which you can read end-to-end like the rest. Two measurements retired the bridge rather than a preference. It never ran on the busiest page here at all:
/ is served as a compressed delta against bytes your browser already holds, and the edge cannot rewrite one, so the homepage advertised nothing to anybody while every other page advertised 25 tools. And your browser keeps only ONE of the five annotations the protocol defines for a tool, readOnlyHint, discarding the rest on the way in. So the bridge had no way to tell your agent which of these tools WRITE data. /webmcp.js restates that in the description an agent reads, and anything that writes stops and asks you, by name, showing you the arguments, before it runs. Analytics: none. No page loads a Web Analytics or RUM beacon, and this Worker exposes no browser-timing collector. Page-load timings are not sent to Cloudflare.
