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 MIA (Amazon Data Services Northern Virginia, AS14618)
- 🔒 Security coprocessor TLSv1.3 AEAD-AES128-GCM-SHA256
- 🌐 Transport HTTP/2
- 🌍 Region Ashburn, US (America/New_York)
- 🖥 Client a bot on an unknown OS
What guards all this: Security Center
Network adapter
- IP address
- 2600:1f28:365:80b0:b2d8:c007:49fc:9498
- ISP / ASN
- Amazon Data Services Northern Virginia (AS14618)
- Country
- US (NA)
- Region
- Virginia
- City
- Ashburn (20147)
- Timezone
- America/New_York
- Approx. coords
- 39.04372, -77.48749 (see on map)
- Cloudflare colo
- MIA (nearest CF data center serving you)
- TCP round-trip
- 31 ms
- QUIC round-trip
- 0 ms (only set on HTTP/3, so it and the TCP row never both appear)
- Delivery rate
- 542740 B/s (most recent edge estimate for this connection)
Transport and security
- HTTP version
- HTTP/2
- TLS version
- TLSv1.3
- TLS cipher
- AEAD-AES128-GCM-SHA256
- Accept-Encoding
- gzip, br
- Stream priority
- weight=16;exclusive=0;group=0;group-weight=0
- TLS extensions
- UXP1PNxegsMtXJUzMiOjvfZRcsE= (SHA-1 of the extension list)
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 this section is
the one part of the page your browser fetches 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…
Computer
- Best guess
- a bot on an unknown OS
- User agent
- CCBot/2.0 (https://commoncrawl.org/faq/)
- Languages
- en-US,en;q=0.5
- Do-not-track
- not set
This session
- Received at
- 2026-09-09T18:18:53.330Z
- Referrer
- (none)
- Cookies sent
- none
- Cloudflare ray
- a38832b34a13a101 (the edge's id for this one request)
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 Cloudflare edge renders it. Your
browser never speaks to a third party. There are exactly two outbound
calls: one server-side RDAP lookup to your IP's registry, which the edge
caches for 24h so visitors from the same block don't re-hit ARIN, and the
Edge Trace section's fetch 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.
/cdn-cgi/trace, which your own
browser makes to this same origin because those seven fields are the ones
the worker is never told. 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.
