---
title: "Who are you"
description: "System Properties for the site: what a single request reveals, for agents and the curious."
path: "/whoareyou"
section: "identity"
kind: "page"
source: "https://aadhar.sh/whoareyou"
---

> Site index: https://aadhar.sh/llms.txt
> This is the Markdown twin of a page on aadhar.sh. The HTML at the source
> URL below is the original, and is hand-written and unminified on purpose.

# System Properties

A transparency page. It shows what a single HTTP request from your client
reveals to this site. None of it is logged, none of it is stored. Close the tab
and it is gone.

**The page is per-request by nature, so this twin describes it rather than
mirrors it.** The live page fills each section from your own connection; there
are no fixed values to publish here. For the machine-readable form of exactly
what your request revealed, request
<https://aadhar.sh/whoareyou.json>, which returns the same fields as JSON.

The page itself is identical for every visitor and is built once at deploy.
The values arrive in a second request, to
<https://aadhar.sh/whoareyou/values.html>, an HTML fragment the edge renders
for that request alone. So they describe the request that fetched them,
normally the same connection as the page. The referrer is the exception, and
the browser fills that row in from what it sent with the page.

## What the live page shows

- **Network adapter**: the IP that connected, its ASN and network operator, and
  the coarse geo the edge resolves it to. Enriched by one server-side RDAP
  lookup against your IP's registry.
- **Transport and security**: HTTP version, TLS version and cipher, and whether
  the connection was reused.
- **Edge Trace**: seven fields Cloudflare's edge knows about the connection that
  the Worker itself is never told. Your browser fetches these from
  `/cdn-cgi/trace` on this same origin.
- **Computer**: what the `User-Agent` and client hints claim about your device,
  operating system, and browser.
- **This session**: cookies, language hints, referrer, and `DNT`.

## What this site cannot see

- **Your DNS resolver or protocol.** Your resolver answers the name before the
  request reaches this site, so only the connecting IP is visible. HTTP/3 implies
  a modern network stack that probably speaks DoH, but that is an inference; the
  request never carries your resolver.
- **Your real identity**, unless you have said so. An IP is not a name.
- **The rest of your browsing.** One request is visible, nothing else.
- **The contents of any encrypted data outside this HTTP session.** TLS is doing
  its job.

## Making it leak less

- Use a VPN or Tor. Either changes your IP, ASN, and geo; Tor also anonymizes
  most fingerprintable details.
- Use a private browsing window. It drops cookies and language hints, somewhat.
- Send `DNT: 1`, or use a browser that does. Almost no servers honor it, but it
  is still a signal.
- Strip the user-agent. Some browsers and extensions let you fake or hide it,
  which shrinks your fingerprinting surface.

## About the page

The Cloudflare edge renders it, and your browser never speaks to a third party.
Two requests leave the page after it loads, both to this same origin: the
values, and the Edge Trace section's read of `/cdn-cgi/trace`. 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 lives for as long
as it takes to render, then nothing writes it to storage.

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. 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.

Source: https://aadhar.sh/whoareyou