Request header checker.
Everything your browser or client sent to reach this page, exactly as the server received it. Use it to see your User-Agent and Accept headers, check what a proxy or CDN is adding, or confirm a custom header is really going out. Nothing is stored.
| Header | Value |
|---|---|
| Accept | */* |
| Accept-Encoding | gzip, br |
| Cdn-Loop | cloudflare; loops=1; subreqs=1 |
| Cf-Connecting-Ip | 216.73.216.231 |
| Cf-Ew-Via | 15 |
| Cf-Ipcountry | US |
| Cf-Ray | a502eb0939b2a40c-CMH |
| Cf-Visitor | {"scheme":"https"} |
| Cf-Worker | kirkdiamond.com |
| User-Agent | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +[email protected]) |
| X-Forwarded-For | 216.73.216.231, 104.23.243.162 |
| X-Forwarded-Proto | https |
| X-Real-Ip | 104.23.243.162 |
About this tool
Headers are shown in canonical form, sorted by name, with repeated headers on separate rows. Anything a proxy, CDN or load balancer added on the way (such as X-Forwarded-For, Via or CF-Ray) appears here too, which makes this a quick way to check what your infrastructure is really injecting. "Client" is the public address your request arrived from, as seen at the edge of this site.
Headers worth looking at
| Header | What it tells you |
|---|---|
| User-Agent | The browser or client identifying itself. Note that Chrome, Edge and others now send a reduced string and put the detail in Sec-CH-UA-* client hints. |
| Accept | The content types the client will take. text/html first means a browser; application/json or */* alone usually means a script. |
| Accept-Language | Preferred languages in order. What sites use to pick a locale before you have chosen one. |
| Accept-Encoding | Compression the client supports: gzip, br, zstd. If it is missing, responses arrive uncompressed. |
| Cookie | Every cookie for this domain. Empty here, since this site sets none. |
| Sec-Fetch-* | Browser-set metadata about the request: whether it is a navigation, same-origin, or triggered by a user. Cannot be spoofed by page scripts. |
| X-Forwarded-For, Via | Proxies on the path recording the original address and themselves. A chain of several entries means several hops. |
| DNT, Sec-GPC | Do Not Track and Global Privacy Control signals, if your browser sends them. |
Uses
- Debugging a proxy or CDN: confirm which headers it adds, strips or rewrites before requests reach your origin.
- Checking a custom header: send
X-Test: hellofrom your client and see whether it arrives intact, with the right case and value. - Content negotiation: see what
AcceptandAccept-Languagea given client sends before writing logic that depends on them. - Mobile apps and SDKs: point the app at this URL to see exactly what its HTTP library sends without a proxy tool.
From the command line
Plain text is the default for curl: curl -H "X-Test: hello" kirkdiamond.com/tools/headers. Also available as JSON for scripts. To see the headers a server sends back rather than the ones you send, use the HTTP response header checker.
Every parameter, the JSON field names, rate limits and ready-made CI checks are in the API and curl reference.