Free carbon-neutral shipping over $99 · 60-day trail trial Direct to origin · no Cloudflare in path

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

hostorigin-trailforge.nasimlab.com
user-agentMozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
cf-ray— not present —
cf-ipcountry— not present —
cf-connecting-ip— not present —
cf-visitor— not present —
x-forwarded-for216.73.217.138
x-forwarded-protohttps
accept-encodinggzip, br, zstd, deflate
cookie— not present —
cf-bot-score— not present —
cf-verified-bot— not present —
cdn-loop— not present —

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.