My HTTP request headers
Every request your browser sends carries HTTP headers — metadata describing what you accept, your language, and your browser. Below are the exact headers we received from you. Cookie and authorization headers are deliberately hidden.
8 headers received
Accept: */*
Accept-Encoding: gzip, br, zstd, deflate
Host: myipis.sh
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Via: 2.0 Caddy
X-Forwarded-Host: myipis.sh
X-Original-For: 127.0.0.1:59436
X-Original-Proto: httpHeader by header
- Accept
- */*
- Accept-Encoding
- gzip, br, zstd, deflate
- Host
- myipis.sh
- User-Agent
- Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
- Via
- 2.0 Caddy
- X-Forwarded-Host
- myipis.sh
- X-Original-For
- 127.0.0.1:59436
- X-Original-Proto
- http
What are HTTP request headers?
HTTP headers are key–value lines your browser attaches to every request. They tell the server what kind of response you can handle and give context about your client. The server reads them and replies with its own set of response headers.
Some headers you'll usually see:
- Host — the domain you're requesting.
- User-Agent — your browser and OS (see what your user agent reveals).
- Accept / Accept-Language / Accept-Encoding — the content types, languages and compression you prefer.
- Sec-CH-UA — modern "client hints" that describe your browser brand and platform.
- X-Forwarded-For — added by proxies to record the original client IP.
Headers can be part of browser fingerprinting, but they don't include your name or account unless you're signed in and a cookie is sent — which we never display here. Want the same data as JSON for scripting? Use the developer API.