HTTP Headers Checker

Inspect the real HTTP response headers sent by any URL, with key security headers highlighted.

Input

Results

Highlighted Headers

HeaderValue

All Response Headers

HeaderValue

Overview

The HTTP Headers Checker shows the response headers a web server sends for a URL. Headers carry the instructions that control caching, content type, redirects, cookies, and many browser security features, so reading them is a core step in diagnosing web problems.

It highlights the commonly useful headers, notes which of five common security headers are absent, and lists everything else the server returned. For a graded review of the security headers, continue to the Security Headers Checker.

How It Works

This site's server requests your URL, follows redirects manually (up to five hops, checking each destination), and returns the headers from the final response. A header is a name and value pair such as Cache-Control: max-age=3600. Header names are case-insensitive and are displayed in lower case.

Highlighted headers are those most often needed in practice: Content-Type, Content-Length, Cache-Control, Server, Location, Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. The tool also reports which of the five security-related ones in that list are missing. To keep responses bounded, it returns at most 100 headers and truncates very long values.

How to Use the HTTP Headers Checker

  1. Enter a URL such as https://example.com.
  2. Press Calculate.
  3. Check the highlighted headers first, then the full list.
  4. Copy the results into a ticket when reporting a caching or security-header issue.

Worked Example

Why is an updated page not showing?

A deployment is live but visitors still see the old page. The headers below are an illustrative sample.

Input

URL: https://www.example.com/

Illustrative output

Highlighted Headers
content-type                 text/html; charset=utf-8
cache-control               public, max-age=86400
server                      cloudflare
strict-transport-security   max-age=31536000; includeSubDomains
x-content-type-options      nosniff

Missing common security headers: content-security-policy, referrer-policy, permissions-policy

This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.

Cache-Control: public, max-age=86400 lets browsers and shared caches reuse the page for 24 hours without asking the server again. That is why an update does not appear: the old copy is considered fresh. Lowering max-age, or using no-cache (revalidate before use), changes that behavior.

The security list shows two protections present and three absent. Missing is a finding to evaluate, not automatically a flaw; the Security Headers Checker explains what each one does.

Interpreting Results

Content-Type
The media type and character set. A wrong value (for example HTML served as text/plain) makes browsers display raw markup.
Cache-Control
Caching rules: max-age sets freshness in seconds, no-store forbids storing, no-cache requires revalidation, and public/private say whether shared caches may keep it.
Location
Present on redirects; the target URL. The tool already follows these, so you normally see the final response.
Server
Software or proxy name, often a CDN. It may be generic or deliberately changed and should not be treated as a reliable fingerprint.
Strict-Transport-Security
Tells browsers to use HTTPS only for the domain for a given time.
Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
Browser-enforced protections and privacy controls. Their absence is reported, not judged, here.

Troubleshooting

The headers differ from what my browser shows.
Servers and CDNs vary responses by user agent, location, language, and cookies. This tool makes a plain request from this site's servers, so you may see a different variant than a logged-in browser. Use your browser's developer tools (Network tab) for the exact browser view.
Several Set-Cookie headers but only one shows.
The underlying response collapses repeated headers of this kind, so only one value is displayed. Use curl -I or browser developer tools to see them all.
"Too many redirects" or "redirect chain led to a target that cannot be checked".
A loop, or a redirect toward an internal address, which the tool refuses to follow. Run the HTTP Status Checker to see the chain.

Limitations and Accuracy

  • Headers reflect a single request from this site's servers at one moment; they may not match what another client or location receives.
  • Intermediaries (CDNs, proxies) may add, modify, or remove headers.
  • Only the final response after redirects is shown, with at most 100 headers; very long values are truncated.
  • Only http:// and https:// URLs for public hosts are supported.

Data Handling

Uses server-side requests. The URL you enter is sent to this site's server function, which requests it from the target server.
Sent to: The web server you named. That server sees a request from this site's infrastructure.

Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.

Frequently Asked Questions

Is "missing" a security header a vulnerability?

Not automatically. Whether a header matters depends on the application. The tool reports facts; the Security Headers Checker adds explanations.

What is a HEAD request and does this use one?

HEAD asks for headers only. This tool uses a normal GET and reads only the headers, because some servers handle HEAD differently.

How do I get the same view on the command line?

Run curl -I https://example.com (add -L to follow redirects).