GET /cdn-cgi/trace on any hostname the CDN serves, on port 80 or 443, answers with one
key=value line per field, in the same format and order as Cloudflare’s, so tools that read it
work unchanged:
curl https://www.example.com/cdn-cgi/tracefl=atl1
h=www.example.com
ip=203.0.113.7
ts=1762560000.123
visit_scheme=https
uag=curl/8.7.1
colo=ATL
sliver=none
http=http/2
loc=US
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519| Key | Value |
|---|---|
fl |
The server that answered, such as atl1 |
h |
The request’s Host |
ip |
Your address as the CDN saw it (an X-Forwarded-For you send is ignored) |
ts |
Unix time with milliseconds |
visit_scheme |
https or http |
uag |
Your User-Agent |
colo |
The location that answered: SJC (San Jose), ATL (Atlanta), LHR (London), NRT (Tokyo) or SIN (Singapore) |
sliver |
none |
http |
http/2 or http/1.1 |
loc |
Your country (ISO 3166-1 alpha-2), XX when unknown |
tls |
TLSv1.3, TLSv1.2, or off on port 80 |
sni |
plaintext on port 443, off on port 80 |
warp, gateway, rbi |
off |
kex |
The TLS key exchange, such as X25519; not on port 80 |
- The answer is
text/plainwithCache-Control: no-storeandAccess-Control-Allow-Origin: *, so a script on any site can read it. - It’s answered for a disabled distribution too, never reaches your origin, and isn’t counted as data served.
- Every path under
/cdn-cgi/is the CDN’s: it never reaches your origin, and one the CDN doesn’t answer is404.