[ §007.ii — work ii · geo-forensics ]

What the edge already knows.

Every request that reaches Cloudflare's network gets tagged with server-side metadata before your code ever sees it. No JavaScript, no geolocation prompt, no tracking pixel — just the plain fact of which data center answered the TCP handshake.

This page reads request.cf on the edge and hands it back to the client. What appears below is what Cloudflare knows about you, right now.

[ subject_file ] — resolving —

source: Pages Functions → request.cf

[ notes ]

All fields below are resolved server-side in a Pages Function. Nothing is computed on the client.
CF data is inherent to Cloudflare's network — no browser geolocation permissions required.
Accuracy of city and latitude/longitude is coarse (~data center level, not street level).
The colo field is Cloudflare's 3-letter airport code for the data center that handled the request.