Skip to main content
wp-config.org

Website and domain checks

HTTP header checker with redirect chain

Check the public HTTP response headers and redirects of an address, with explanations of the HTTPS, cache and security settings you can see. This HTTP header checker follows the redirect chain for you.

  • Redirect chain
  • Security headers
  • Cache headers

Free, no sign-up. Lookups and results are not saved by this site.

This tool needs JavaScript. Turn JavaScript on and reload the page.

HTTP headers

What this check looks at

  • At most five HEAD requests: the first one and up to four redirects. Each address must be public and use a standard HTTP or HTTPS port.
  • A selected set of response headers, with plain notes on which security and caching headers were seen. Cookies and page bodies are left out.
  • HEAD can give a different answer from GET. If a site blocks HEAD or does not support it, you see its answer as it came, with no GET fallback.
  • Seeing a header does not mean the policy is right, that a page came from a cache, that the TLS setup is strong or that the site has no vulnerabilities.

What you can do

  • Header checks for public HTTP and HTTPS addresses

  • The redirect chain, up to four redirects

  • Notes on visible security headers

  • Cache-Control and content type context

  • A fresh security check before every request

How to check a website’s HTTP headers

  1. Enter the address

    Enter a public HTTP or HTTPS address without a username, password or other secrets.

  2. Run the check

    Start the check. A quick Cloudflare security check runs first, then this site requests the headers.

  3. Read each response

    Review each redirect and the final headers. Change the settings in your real application and check again after you deploy.

What the headers tell you, and what they do not

Response headers show how a server answers before any page content arrives: where it redirects, how long browsers and CDNs may cache the response and which security policies it sends. This check makes HEAD requests from this site's server, follows up to four redirects and explains the headers it finds.

Know the limits

Only standard public HTTP and HTTPS ports are checked, with at most five HEAD requests. Some servers answer HEAD differently from GET or block automated requests. Only selected headers are returned: no cookies, signed-in pages, page content, TLS grade or security audit. A header being present does not mean its policy is right.

For a full HSTS policy check, use the HSTS checker. To test protocols and compression, try the HTTP/2 test, the HTTP/3 test and the Brotli test. To write redirect rules, use the 301 redirect generator, and to understand a status code, see the error code guide.

Frequently asked questions

How do I check the HTTP headers of a website?

Enter the address here. On the command line, curl -I with the address shows the response headers of a HEAD request.

Which security headers should a website send?

Commonly Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, plus frame-ancestors or X-Frame-Options. The right values depend on your site, so test changes first.

Why can results differ from my browser?

This check makes HEAD requests from this site’s server. Some servers answer HEAD differently from GET, block automated requests or vary by location or cookies.

How many redirects are too many?

Aim for one hop from the old address to the final one. This checker follows up to four, and each extra hop slows the first visit.

Does it show cookies or page content?

No. Only selected headers are returned, never cookies or page content.

Related tools

  • SEO report

    Check one page’s SEO basics and PageSpeed, then download the report as a PDF.

  • Redirects

    Generate 301 and other redirects for Nginx or Apache from a CSV list.

  • Nginx

    Generate an Nginx config for WordPress with TLS, caching, HTTP/2 and HTTP/3.

  • DNS lookup

    Look up DNS records and check SPF, DMARC, DKIM and DNSSEC.