HTTP Header Checker

The HTTP Header Checker shows the response status and headers that a web server returns for any URL.

Enter an address and see the status code, the full header list, and any redirects it went through.

How to check HTTP headers

1. Enter a URL. A bare domain or a full address both work.
2. Check headers. Our server fetches it safely and returns the response.
3. Read the results. Status code, redirect count, and every response header.

Why headers matter

HTTP headers control caching, security, cookies, and how content is delivered. Inspecting them helps diagnose why a page is slow, not caching, or being blocked.

Because browsers cannot read another site's headers directly, the fetch happens on our server — safely, with private addresses blocked.

• Full headers: server, caching, security, and content type.
• Status & redirects: the exact code and the chain followed.
• SSRF-safe: internal and private hosts are refused.
• Not stored: the URL is fetched, not saved.

Related webmaster tools

Headers and redirects go together. To see the full hop-by-hop path of a redirecting URL, the Redirect Checker traces every step.

To inspect a site's TLS certificate details, the SSL Certificate Checker reads its expiry and issuer. And for the DNS records behind a domain, the DNS Lookup lists them.

Frequently Asked Questions

How does the checker fetch the URL?

Browsers block cross-site requests, so our server fetches the URL on your behalf and returns the headers. The request is SSRF-protected, and requests to private or internal addresses are refused.

Is the URL I check stored?

No. The URL is fetched to read its headers and is not saved or logged as content. Only basic rate-limiting counters are kept to prevent abuse.

What do the headers tell me?

They reveal the web server, caching rules (Cache-Control, ETag), content type, cookies, and security policies like Content-Security-Policy and Strict-Transport-Security.

Does it follow redirects?

Yes. It follows the redirect chain up to ten hops and shows the final status and headers, noting how many redirects were followed.

What does a status code mean?

200 means the page loaded, 301 and 302 are redirects, 404 means not found, and 500-range codes are server errors. The code is shown prominently with a colour cue.