Website HTTP Header Checker

Use a public HTTP or HTTPS website URL; HTTPS is the default. Do not enter URLs containing login credentials or private access tokens. This checks one public response, not the whole website. Missing headers do not prove a compromise; present headers do not guarantee security.

What does an HTTP Header Checker show?

Response headers are server instructions that do not appear in the page body. This tool helps you review security policies, caching and connection status as a starting point for website troubleshooting.

1. Security headers

  • Content-Security-Policy (CSP):Limits allowed resource and script sources to mitigate some XSS risks. Review the policy itself; Report-Only reports violations without blocking them.
  • Strict-Transport-Security (HSTS):Instructs browsers to use HTTPS for a defined period. It must arrive over HTTPS with a positive max-age; review certificates and subdomains before enabling it.
  • X-Frame-Options:Restricts embedding in frames to help prevent clickjacking. This tool also checks the CSP frame-ancestors directive.
  • X-Content-Type-Options:The nosniff value tells browsers to respect Content-Type rather than guess MIME types. The server must still send the correct content type.

2. Performance and caching

  • Cache-Control:Read the cache policy in the header details: max-age sets freshness, private restricts shared caching, no-store disallows storage, and no-cache requires validation before reuse.
  • Content-Encoding:Look for gzip or br (Brotli) in this response. Compression can reduce text transfer size; an absent header does not prove that the entire site lacks compression or is slow.
  • CF-Cache-Status:HIT means Cloudflare served this response from cache. MISS, DYNAMIC and BYPASS are not necessarily errors; personalized login and cart content should usually avoid shared caches.

3. Server and connection status

  • HTTP status:200 generally means success, 3xx a redirect, 4xx a request or access issue, and 5xx a server-side error. The redirect path shows the final destination.
  • Set-Cookie:For login cookies, review Secure, HttpOnly and SameSite for HTTPS transmission, script access and cross-site sending. This tool hides Set-Cookie values; inspect complete attributes in browser developer tools.
  • Server / X-Server:If supplied, these headers may show names such as cloudflare or nginx. A CDN or proxy can add or rewrite them, so they do not reliably identify the origin server or data center.

What should I do with the results?

Check the final URL and status code first, then review compression, caching and security headers. Share the URL, time and report with your maintainer to identify what belongs to hosting, the CDN or application before testing changes. If you are considering a move, share the results with ServerZoo to discuss hosting needs. This tool is not a full-site performance test or vulnerability scanner.

HTTP headers and caching FAQ

Review eligibility, usage and responsibilities before taking the next step.

Do missing security headers mean the site has been hacked?

No. This tool examines one public HTTP response. Missing headers are configuration prompts to assess, not evidence of compromise; complete headers do not prove the whole site is secure.

Test forms, plugins and third-party resources before changing CSP or HSTS to avoid breaking normal functions.

Are Cloudflare MISS, DYNAMIC or BYPASS states errors?

Not necessarily. HIT means this response came from cache. Other states can reflect a first request, a dynamic page or configured cache bypass.

Login, carts and personalized content generally should not use shared caching. Assess the page and headers rather than forcing a HIT.

What should I share with my maintainer after checking headers?

Provide the original and final URLs, status code, time and relevant headers to distinguish server, CDN and application settings.

This is not a complete performance test or vulnerability scan; one response does not represent every page on the site.

Discuss your needs with support

Are Cache-Control no-cache and no-store the same?

No. no-cache allows storage but requires validation before reuse; no-store instructs caches not to store the response. no-cache alone is not evidence of a caching fault. Consider personalized or logged-in content and CDN rules when assessing the policy.

Is HTTP to HTTPS followed by a www redirect a fault?

Not necessarily. Redirects may normalize URLs. Check whether the final page is correct and whether there are loops or unnecessary steps. Share the full redirect chain with the maintainer to locate overlapping rules in the host, CDN or application.

Does a Report-Only CSP block unsafe content?

No. Content-Security-Policy-Report-Only observes violations without enforcing that policy. Review reports and test normal functionality before deploying an appropriate enforced CSP. The mere presence of a header name does not establish effective protection.

Why do old headers appear after I changed the server?

Confirm the exact URL, then check whether a CDN, proxy or cache still serves the old response. This tool may also use brief caching. Different layers can set or override headers; compare the origin and public endpoint rather than assuming one configuration change reaches both.

Why can the checker get 403 when my browser opens the page?

The public checker uses a different connection and does not share your browser’s login state. Access controls or protection rules may respond differently. A 403 does not prove a site-wide outage. Give the maintainer the URL, time and result; do not disable protections merely to pass the check.

Topics HTTP headers, redirects and security checks

Choosing and using this service

Start with status codes and redirects

Check the HTTP status, Location and redirect chain for the actual URL. Keep HTTP-to-HTTPS and www settings consistent; investigate website and proxy settings if a loop or error appears.

Assess caching and security headers separately

Cache-Control helps explain caching, while security headers depend on site functionality. A single response is not a full security audit; distinguish CDN or proxy settings from origin-server settings.

↑