Back to Tools HTTP & OWASP

HTTP Header Checker & OWASP Security Auditor

Inspect raw HTTP/1.1 & HTTP/2 response headers, trace multi-hop 301/302 redirect chains with per-hop latency, and audit OWASP security headers (HSTS, CSP, X-Frame-Options) in real time.

Live Test Targets:
Final HTTP Status
200 OK
HTTP/2 · TLS 1.3
OWASP Security Grade
A (85/100)
HSTS + CSP + XFO Active
Redirect Chain
1 Hop (0 Redirects)
IP: 104.16.132.229
Response Latency
38.4 ms
TTFB: 34.1 ms
Server & Edge CDN
cloudflare
HTTP/3 (h3=":443") Ready

📋 Final HTTP Response Headers

https://www.cloudflare.com (11 headers received)

Header Field Header Value
dateMon, 16 Nov 2026 00:32:59 GMT
content-typetext/html; charset=utf-8
strict-transport-securitymax-age=31536000; includeSubDomains; preload
content-security-policyframe-ancestors 'self'; report-uri /cdn-cgi/csp
x-content-type-optionsnosniff
x-frame-optionsSAMEORIGIN
referrer-policystrict-origin-when-cross-origin
cache-controlpublic, max-age=14400, must-revalidate
alt-svch3=":443"; ma=86400
servercloudflare

🛡️ OWASP Security Header Audit & Hop Chain

Automated evaluation against OWASP Secure Headers Project & redirect trace:

Hop #1 · HTTP/2 200 38.4 ms · IP: 104.16.132.229
https://www.cloudflare.com
Strict-Transport-Security+25 PASS
max-age=31536000; includeSubDomains; preload
Content-Security-Policy+25 PASS
frame-ancestors 'self'; report-uri /cdn-cgi/csp
X-Content-Type-Options+15 PASS
nosniff
X-Frame-Options+15 PASS
SAMEORIGIN
Referrer-Policy+10 PASS
strict-origin-when-cross-origin
Permissions-Policy0/10 INFO
Missing (Restrict camera, microphone, geolocation)

RFC 9110 & OWASP HTTP Response Header Reference Matrix

Essential security, caching, protocol negotiation, and redirection headers every production web server should configure:

HTTP Header Name Category Recommended Production Value Engineering Purpose & Security Impact
Strict-Transport-Security Security (OWASP) max-age=31536000; includeSubDomains; preload Forces browsers to connect strictly over HTTPS/TLS, preventing SSL-stripping and MITM downgrade attacks.
Content-Security-Policy Security (OWASP) default-src 'self'; object-src 'none' Whitelists trusted script, style, and frame origins to mitigate Cross-Site Scripting (XSS) and data exfiltration.
X-Content-Type-Options Security (OWASP) nosniff Prevents browsers from MIME-sniffing a response away from the declared Content-Type.
X-Frame-Options Security (OWASP) SAMEORIGIN / DENY Blocks unauthorized third-party sites from embedding the page in an <iframe> (Clickjacking defense).
Cache-Control Caching & CDN public, max-age=3600, stale-while-revalidate=60 Dictates browser and CDN edge caching TTL, revalidation policies, and immutability.
Alt-Svc Protocol (QUIC) h3=":443"; ma=86400 Advertises HTTP/3 (QUIC over UDP) support on port 443 for zero-RTT multiplexed connections.
Location Redirection (3xx) https://www.example.com/new-path Specifies the target destination URI during 301 Permanent, 302 Found, 307, or 308 redirects.

What This HTTP Header Checker and OWASP Auditor Does

This tool connects to any public HTTP or HTTPS URL (on ports 80, 443, 8080, or 8443) to inspect raw server response headers, trace multi-hop redirect chains, and grade OWASP security headers:

  • Request Method & User-Agent Selection: Sends either a HEAD or GET request using one of four selectable User-Agent profiles (ToolGiga Auditor, Chrome Desktop, Googlebot Smartphone, or cURL CLI) to detect crawler-specific headers or conditional redirects.
  • Multi-Hop Redirect Chain Tracer (Up to 6 Hops): Follows 301, 302, 307, and 308 Location redirects step by step, displaying each hop's HTTP status line, resolved public IPv4/IPv6 address, Time to First Byte (TTFB), total response time in milliseconds, parsed key-value table, and raw header block with one-click copy.
  • OWASP Security Header Scorecard (0–100 Points, Grade A+ to F): Audits the final response against six OWASP Secure Headers criteria: Strict-Transport-Security (25 pts), Content-Security-Policy (25 pts), X-Content-Type-Options: nosniff (15 pts), X-Frame-Options / frame-ancestors (15 pts), Referrer-Policy (10 pts), and Permissions-Policy (10 pts).

Understanding HTTP Response Headers: The Invisible Control Plane of the Web

Every time a browser, mobile app, or search engine crawler requests a URL, an invisible negotiation occurs before a single byte of HTML or CSS is rendered. Governed by IETF RFC 9110 (HTTP Semantics), RFC 9113 (HTTP/2), and RFC 9114 (HTTP/3 over QUIC), the server replies with a status line (such as HTTP/2 200 or HTTP/1.1 301 Moved Permanently) followed by a block of HTTP response headers.

While ordinary users only see the visual webpage, DevOps engineers, cybersecurity auditors, and technical SEO specialists know that HTTP response headers dictate the security, speed, and indexability of a domain. In HTTP/1.1, headers are transmitted as plain ASCII key-value lines terminated by CRLF (\r\n). In HTTP/2 and HTTP/3, headers are binary-encoded and compressed using HPACK (RFC 7541) or QPACK (RFC 9204) to eliminate redundant metadata overhead across multiplexed streams—yet their semantic names (always lowercase in HTTP/2+) remain identical.

The OWASP Secure Headers Checklist: Hardening HSTS, CSP, and Framing Defenses

Misconfigured or missing HTTP security headers leave web applications exposed to protocol downgrade attacks, Cross-Site Scripting (XSS), MIME-type confusion, and UI redressing (Clickjacking). Our workstation grades every inspected endpoint against the six foundational pillars of the OWASP Secure Headers Project:

  • Strict-Transport-Security (HSTS — RFC 6797): Instructs browsers to never load the site over unencrypted HTTP and to automatically convert all http:// links to https:// before sending a network packet. A production-grade header looks like:
    Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
    This enforces HTTPS for 1 full year (31,536,000 seconds), protects all subdomains, and qualifies the domain for hardcoding into Chrome, Firefox, and Safari HSTS Preload lists.
  • Content-Security-Policy (CSP Level 3): The single most powerful defense against Cross-Site Scripting (XSS) and unauthorized card-skimming scripts (Magecart). By defining explicit source directives such as default-src 'self'; script-src 'self' 'nonce-...'; object-src 'none'; frame-ancestors 'self', CSP stops browsers from executing injected inline scripts or exfiltrating data to rogue domains.
  • X-Content-Type-Options: nosniff: Prevents browsers from performing "MIME sniffing"—a dangerous legacy behavior where a browser guesses that a user-uploaded .jpg or .txt file contains executable HTML/JavaScript and runs it in the site’s origin context.
  • X-Frame-Options & CSP frame-ancestors: Setting X-Frame-Options: DENY or SAMEORIGIN (alongside Content-Security-Policy: frame-ancestors 'self') prevents malicious websites from loading your login or checkout page inside an invisible <iframe> to hijack user clicks.
  • Referrer-Policy & Permissions-Policy: Setting Referrer-Policy: strict-origin-when-cross-origin strips sensitive URL paths and query tokens from the Referer header when users click external links, while Permissions-Policy: camera=(), microphone=(), geolocation=() disables sensitive browser hardware APIs for third-party embeds.

Tracing Multi-Hop Redirect Chains (301, 302, 307, 308) and TTFB Latency

When migrating domains, enforcing www canonicalization, or upgrading from http:// to https://, websites frequently create accidental multi-hop redirect chains—for example:
http://example.com 301→ https://example.com 301→ https://www.example.com 302→ https://www.example.com/en/.

Each redirect hop forces the client to parse the Location header, potentially perform a new DNS lookup, complete a new TCP 3-way handshake and TLS 1.3 negotiation, and wait for another Time to First Byte (TTFB). On mobile networks, a 3-hop redirect chain can add 300 ms to 900 ms of dead latency before the browser even begins downloading the target HTML document, severely degrading Core Web Vitals (LCP). Furthermore, Googlebot only follows up to 5 redirect hops in a single crawl session; chains mixing permanent (301 / 308) and temporary (302 / 307) status codes dilute canonical signals and waste crawl budget. Our hop-by-hop tracer exposes every intermediate status code, IP address, and millisecond delay so you can collapse multi-step redirects into a single direct 301 hop.

Decoding CDN Edge Caching, ETag Revalidation, and HTTP/3 Alt-Svc Telemetry

Beyond security and redirects, HTTP response headers provide deep visibility into your Content Delivery Network (CDN) and origin caching architecture:

  • Cache-Control & Age: Directives like public, max-age=3600, s-maxage=86400, stale-while-revalidate=60 independently govern browser cache lifetime (max-age) and shared CDN edge cache lifetime (s-maxage). The Age header reveals how many seconds the object has already resided in the edge proxy cache.
  • Conditional Requests (ETag & Last-Modified): Allow browsers to send If-None-Match revalidation headers; if the resource has not changed, the server returns an ultra-fast 304 Not Modified response with zero body bytes.
  • Edge Provider Signatures (CF-Cache-Status, X-Cache, Server-Timing): Headers such as cf-cache-status: HIT (Cloudflare), x-cache: Hit from cloudfront (AWS), or x-served-by (Fastly) confirm whether your static and dynamic assets are being served from a nearby Anycast PoP or hitting your origin database on every request.

Frequently Asked Questions About HTTP Response Headers & Security Auditing

What are HTTP response headers and why do they matter for SEO and security?

HTTP response headers are key-value metadata lines transmitted by a web server before the HTML body (defined in IETF RFC 9110). They control critical browser behaviors: search engine indexing (X-Robots-Tag, Canonical Link), redirect status codes (301 vs 302 Location), edge caching speed (Cache-Control, Age, ETag), protocol upgrades (Alt-Svc for HTTP/3 QUIC), and defense against XSS and Clickjacking (CSP, HSTS, X-Frame-Options).

What is the difference between a 301, 302, 307, and 308 HTTP redirect?

A 301 Moved Permanently passes full SEO link equity to the new Location URL and caches the redirect indefinitely, though historic browsers sometimes changed POST requests to GET. A 308 Permanent Redirect is the strict RFC 9110 equivalent of 301 that guarantees the HTTP method (POST/HEAD) never changes. Conversely, 302 Found and 307 Temporary Redirect indicate temporary moves that do not transfer permanent canonical authority.

How is the OWASP Security Header Grade (A+ to F) calculated?

Our auditor scores your final HTTPS response out of 100 points based on the OWASP Secure Headers Project: Strict-Transport-Security / HSTS (+25 pts), Content-Security-Policy / CSP (+25 pts), X-Content-Type-Options: nosniff (+15 pts), X-Frame-Options or CSP frame-ancestors (+15 pts), Referrer-Policy (+10 pts), and Permissions-Policy (+10 pts). Scores of 90+ earn an A+, 80–89 earn an A, and missing core HSTS/CSP headers drop the grade below C.

Why should I test HTTP headers using different User-Agent profiles like Googlebot?

Many CDNs, Web Application Firewalls (WAFs), and origin servers return different HTTP headers depending on the client User-Agent. Inspecting your URL with the Googlebot Smartphone profile reveals whether your server accidentally injects an X-Robots-Tag: noindex header, serves different Vary/Cache-Control rules, or triggers an unintended 302 country redirect for search crawlers.

What does the Alt-Svc: h3=":443" header mean?

The Alt-Svc (Alternative Services, RFC 7838) header informs browsers that the server supports HTTP/3 over QUIC (UDP port 443) in addition to standard TCP/TLS HTTP/2. When a browser sees h3=":443"; ma=86400, it seamlessly upgrades subsequent requests to multiplexed 0-RTT QUIC connections.

How does this tool protect against Server-Side Request Forgery (SSRF)?

Before initiating any cURL socket connection, our backend resolves the hostname via DNS and validates every returned IPv4/IPv6 address against PHP FILTER_FLAG_NO_PRIV_RANGE and FILTER_FLAG_NO_RES_RANGE. Loopback (127.0.0.0/8, ::1), RFC 1918 private LANs (10.x, 172.16-31.x, 192.168.x), and cloud metadata endpoints (169.254.169.254) are strictly blocked, and the verified public IP is pinned via CURLOPT_RESOLVE to prevent DNS rebinding.