Skip to content

HTTP Header Checker

Enter a URL to see the HTTP response headers it returns, such as Content-Type, Cache-Control, Content-Length and Last-Modified.

Runs in your browser Free, no sign-up
Loading tool workspace...

What is HTTP Header Checker?

HTTP Header Checker shows the response headers a URL returns. Response headers describe how a server answered: the content type and length, caching rules (Cache-Control, Expires, Last-Modified), and any custom headers the server chooses to expose. Checking them is a quick way to debug caching, content negotiation and API behavior.

Enter a URL and the tool sends a HEAD request (falling back to GET) from your browser, then lists the headers as JSON. Because the request comes from the browser, browser security rules decide which sites can be checked and which headers are visible; see the technical details below.

How to use HTTP Header Checker

  1. Enter the full URL, including https://.
  2. Run the check; the tool sends a HEAD request and falls back to GET if HEAD fails.
  3. Read the status line and the headers the browser is allowed to read.
  4. If the request is blocked, or you need headers the browser hides (such as Set-Cookie or Strict-Transport-Security), copy the curl command shown below the result and run it in a terminal.

Key features

  • Fetches response headers for any CORS-enabled URL
  • HEAD request first, with an automatic GET fallback
  • Status line and headers in the familiar curl -I format
  • Explains why the browser blocked a request (CORS, mixed content or an invalid URL)
  • Ready-to-copy curl command that shows every header from a terminal
  • Runs in your browser: no sign-up and no server-side logging

Common use cases

  • Checking Cache-Control, Expires and Last-Modified on your own API or CDN assets
  • Confirming the Content-Type returned for JSON, images or downloads
  • Verifying which headers your API exposes through Access-Control-Expose-Headers
  • Testing CORS configuration on an endpoint you control

Technical details & standards

The check uses the browser's fetch() API, so it is subject to CORS. The target server must send an Access-Control-Allow-Origin header that permits this site; most APIs with CORS enabled qualify, while many ordinary websites do not and will show an error.

Even when the request succeeds, the browser only reveals the CORS-safelisted response headers (Cache-Control, Content-Language, Content-Length, Content-Type, Expires, Last-Modified and Pragma) plus any the server lists in Access-Control-Expose-Headers. Security headers such as Strict-Transport-Security or Content-Security-Policy are usually hidden from scripts. For a complete view of any site, use curl -I https://example.com or the Network tab in your browser's developer tools.

Frequently asked questions

Why does checking some websites fail?

The request is made by your browser, and browsers block cross-origin responses unless the server allows them with an Access-Control-Allow-Origin header. Most websites do not, so use curl -I or your browser's developer tools (Network tab) to see their headers.

Why don't I see security headers such as HSTS or CSP?

Browsers only expose the CORS-safelisted headers (Content-Type, Cache-Control, Content-Length, Content-Language, Expires, Last-Modified, Pragma) and any listed in Access-Control-Expose-Headers. Other headers are present on the response but hidden from scripts.

How do I check HTTP headers from the command line?

Run curl -I https://example.com to send a HEAD request and print only the headers, or curl -sD - -o /dev/null https://example.com to see the headers of a normal GET request.

What is the difference between a HEAD and a GET request?

HEAD asks for the same headers as GET but without the body, so it is faster for checking headers. Some servers do not support HEAD, which is why this tool retries with GET.

Is my data safe?

When you request a URL, your browser sends the request directly to that destination. CodeUnpack does not proxy the request.

Does it work offline?

This tool needs an internet connection to request the target URL.

More web & network tools

View all