HTTP Header Checker
Check the HTTP response headers of any URL — every header explained, a security-header checklist with recommended values, version-leaking headers flagged, and the full redirect chain. Fetch as a browser, Googlebot or Bingbot.
Input
Some servers answer HEAD differently from GET — try both if headers look incomplete.
Output
| Property | Value |
|---|---|
| No data yet | |
| Header | Value | Category | What it does |
|---|---|---|---|
| No data yet | |||
| Header | Status | Value / recommendation |
|---|---|---|
| No data yet | ||
| # | Status | URL |
|---|---|---|
| No data yet | ||
More ways to use this tool
REST API
curl -X POST https://api.iotools.cloud/v1/tool/http-header-checker \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com",
"method": "GET",
"userAgent": "browser",
"followRedirects": "true"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `http-header-checker` tool (HTTP Header Checker) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.
| Cost per API/MCP call | From 5 credits |
|---|---|
| Need more credits? | View pricing |
Also available with
Guides
Check the HTTP headers of any URL
Enter a URL and the HTTP Header Checker fetches it and lists every response header the server sends back: Content-Type, Cache-Control, Set-Cookie, Strict-Transport-Security, CDN and proxy headers, and anything custom. Each header comes with a plain-English note on what it does and which group it belongs to (security, caching, CORS or content). It's the same information curl -I prints, without needing a terminal.
The results come in five parts:
- Summary: the final URL, status code, number of redirects, response time and how many of the six core security headers are missing.
- Response headers: every header, its value and what it does. Copy it, or download it as a CSV.
- Security headers: a checklist of
Strict-Transport-Security,Content-Security-Policy,X-Content-Type-Options,X-Frame-Options,Referrer-PolicyandPermissions-Policy. Each one is marked present or missing, and missing ones get a recommended value. It also flags headers that advertise your server software, such asServer: nginx/1.18.0orX-Powered-By: PHP/8.1, because a version number tells attackers which exploits to try. - Redirect chain: every hop from the URL you entered to the page that answered.
- Raw headers: the response as plain
Name: valuelines, ready to paste into a ticket or deployment notes.
Options
- Request method: GET fetches the page the way a browser does. HEAD asks for headers only. Some servers and CDNs answer HEAD differently, so if a header seems to be missing, run both.
- User agent: check the response as a desktop browser, Googlebot (smartphone) or Bingbot. Sites sometimes send different caching,
X-Robots-Tagor redirect headers to crawlers, and this is how you catch it. - Follow redirects: on by default, up to 10 hops. Turn it off to see the headers of the redirect response itself, such as a
301'sLocationandCache-Control.
Why are the headers different from what my browser shows?
Headers can change with the user agent, cookies, the region of the requesting server and CDN caching. This tool sends a fresh request with no cookies from our server, which is what a first-time visitor or a crawler sees. Your browser's devtools show the headers of your own session.
Which security headers does a site need?
Every HTTPS site benefits from Strict-Transport-Security, X-Content-Type-Options: nosniff and a Referrer-Policy. A Content-Security-Policy is the strongest protection against cross-site scripting but needs tuning for each site. Treat the checklist as a review list rather than a pass/fail grade. API endpoints and static files don't need every header a page does.
Privacy and limits
The URL is fetched from our server, because browsers can't read another site's headers directly. Only public addresses can be checked: localhost, private IP ranges and internal hostnames are refused, including when a redirect points to one. Response bodies are never downloaded or stored.
Related tools
To audit the Content-Security-Policy this check finds, paste it into the CSP Evaluator. If you already have headers copied from devtools or curl, the HTTP Header Analyzer explains them without fetching anything. For a hop-by-hop look at redirects, including loops and HTTPS-to-HTTP downgrades, use the Redirect Checker.