Edge diagnostics
What the origin actually received, plus a live side-by-side of the proxied hostname against the grey-clouded origin hostname.
This request, as seen by the origin
| host | trailforge.nasimlab.com |
|---|---|
| user-agent | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected]) |
| cf-ray | a52d45eeb9305645-CMH |
| cf-ipcountry | US |
| cf-connecting-ip | 216.73.217.138 |
| cf-visitor | {"scheme":"https"} |
| x-forwarded-for | 216.73.217.138, 216.73.217.138 |
| x-forwarded-proto | https |
| accept-encoding | gzip, br |
| cookie | — not present — |
| cf-bot-score | — not present — |
| cf-verified-bot | — not present — |
| cdn-loop | cloudflare; loops=1 |
Cache behavior probe
Fetches the same asset twice and reports cf-cache-status and timing.
Idle.
Cloudflare vs. direct origin
Same origin server, two hostnames. One is proxied, one resolves straight to the droplet.
Idle.