this browser
A live fingerprint of the device you're reading this in — geolocation, network and rendering signals any website can read without a single cookie. No login, no permission prompt.
Your browser can volunteer IPs over WebRTC — sometimes your real one, even behind a VPN.
scanning STUN…Everything above ran entirely in your browser. Nothing was stored, logged, or sent to any server.
Agents see this as /me.md
— same content negotiation as the IP pageAn agent fetching your trace gets a Markdown fingerprint report by default — the live signals above, inline and token-efficient. The browser-side signals stay client-only; the Markdown carries what the server can resolve about your connection.
# Browser trace — this connection - IP: 216.73.217.175 (Columbus, Ohio, United States) - Location: Columbus, Ohio, United States - Timezone: America/New_York (-04:00) - Network: AS16509 · Anthropic, Pbc - Rev DNS: — Browser-fingerprint signals (canvas, WebGL, audio, fonts, WebRTC) are client-only and not present in this server-rendered view. Ask for application/json and you get the structured record instead.
Try it: /me.md in your terminal or any agent.
Reduce your fingerprint.
A privacy-focused browser or anti-fingerprinting extension blunts most of these signals; a VPN covers the network ones above.