This is what your browser gives away.

What it reveals.

1. That address resolves to Columbus, OH. Nobody asked you and nothing prompted: an address is what a connection is made of, so every server you reach gets this much whether or not it does anything with it. This page is telling you because most of them do not.

   request · moderate confidence

   A city here is where your provider registered the address, which is their equipment rather than you. Measured on 31 July 2026 against a fixed home line: this named a town roughly an hour's drive from the machine making the request, and the same person on a German connection is routinely placed in a neighbouring village. The difference is the provider's block assignment, not the lookup getting cleverer, so the error is worth anywhere from a street to a region depending on who sells you the connection. On a mobile network one gateway can carry a whole region, and behind a VPN it is the exit node. Read from this request and never written, the same as the address above.

2. Your request arrived from 216.73.217.135. The CDN in front of this page tagged it US.

   request · high confidence

   Read from the request headers on the server and returned in this one response. It is not written to any table, and there is no column for it in the schema. Act 7 shows that schema.

See the evidence.

Try a privacy defence.

These switches model changes against this corpus. They do not change your browser settings.

Waiting for your component counts…

What gets stored.

Separate salted component counts. No raw readings or stored joint fingerprint.

• Timestamps can link readings. That is how the return check works.
• A cookie limits repeat submissions. Recognition does not use it.
• The rate limiter hashes your IP. Those rows expire after ten minutes.