HTTP Header Inspector — everything your browser just sent

Every HTTP header our edge received on this exact request, verbatim, with a plain explanation of what each one reveals about you.

Header	Value	What it reveals
accept	/	Content types the browser will take for this request type.
accept-encoding	gzip, br	Compression formats supported. Low entropy, but the exact ordering varies by client.
cf-connecting-ip	216.73.216.227	Added by Cloudflare. The real client address behind the proxy.
cf-ipcountry	US	Added by Cloudflare from its own geolocation of your address.
cf-ray	a2d284d868ee845c	Cloudflare request identifier, including the edge datacenter code.
cf-visitor	{"scheme":"https"}
connection	Keep-Alive
host	ipcanary.org
user-agent	Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)	Browser, engine and OS family. The single richest passive identifier you send.
x-forwarded-proto	https
x-real-ip	216.73.216.227

11 headers received. Headers prefixed cf- were added by Cloudflare's edge and were not sent by your browser.

Read: what your browser headers reveal Get as JSON

Frequently asked

Can I stop sending these headers?

Mostly no. Accept, Accept-Encoding and User-Agent are required for the request to work sensibly. You can reduce entropy by using a browser that freezes its user agent and limits Client Hints, but a browser that sends unusual headers is itself distinctive.

What is the most identifying header here?

User-Agent combined with Accept-Language. The pair narrows you to a small population before any script runs, and Accept-Language is the value most likely to contradict a VPN exit country.