Home/Strumenti/HTTP Headers Checker

Strumenti sviluppatore strumento

HTTP Headers Checker

Inspect HTTP response status, redirect chain, and security headers for any public URL — including HSTS, CSP, and X-Frame-Options.

Free HTTP headers checker. See response status, full redirect chain, and security headers (HSTS, CSP, X-Frame-Options) for any public URL.

Perché le persone usano questo strumento

HTTP Headers Checker fetches a public URL from our server and shows the response status, full redirect chain, and every response header — with quick checks for the most important security headers like HSTS, CSP, X-Frame-Options, and Referrer-Policy.

  • Verify a redirect chain is short and lands on the expected canonical URL.
  • Confirm security headers (HSTS, CSP, X-Frame-Options) are set correctly on a production page.
  • Debug caching and CDN behavior by inspecting Cache-Control, ETag, and Vary headers.

Come usarlo

  1. 1Enter the full URL you want to inspect, including the protocol.
  2. 2Choose GET (sees real-page response) or HEAD (lighter request).
  3. 3Review the redirect chain, response status, security-header checklist, and full header list.

Best practices

  • Always test the full redirect chain — long chains slow down crawl and waste link equity.
  • Make sure HSTS, X-Content-Type-Options, and a CSP are set on production HTML pages.
  • Watch for cookies set with Set-Cookie on cross-site responses; missing SameSite=Lax can cause issues.
  • Re-check after CDN or hosting changes — a misconfigured cache can override your origin headers.

Common mistakes to avoid

  • Do not rely on a single check — staging headers and production headers often differ.
  • Do not assume redirects are 301 just because the URL changes; the tool shows the actual status.
  • Do not paste URLs containing secrets (tokens in query strings) into any third-party header checker.
  • Do not use HEAD when the server responds differently to HEAD vs GET (some apps do).

FAQ

Risposte utili

Is my URL stored?

No. The URL is sent through our server only to issue the request and return the response. We do not log or persist it.

Why does the response differ from my browser?

Some sites vary headers by User-Agent, geography, or cookies. The check is sent from a server with no cookies, so personalized responses will not match.

Why might private hosts be rejected?

For safety, the checker only follows http and https URLs that resolve to public hosts. Localhost, link-local, and RFC1918 ranges are rejected.