HTTP Header Viewer
Last updated:
See exactly what a server sends back. Inspect the full HTTP response headers for any URL, including status code, caching, content type, and security headers, with missing protections flagged.
Enter a URL to view its HTTP headers:
Referral reward
Know a business that needs a website or SEO?
Introduce them and earn a referral reward. They work with us directly, and we handle the proposal, delivery and support.
Know a business that needs a website or SEO?
Introduce them and earn a referral reward. They work with us directly, and we handle the proposal, delivery and support.
Projects: 10%, at least $100
Monthly services: 10% for the first six months
A $1,999 website earns you about $200. A $999 a month SEO plan earns about $600 over six months.
Your introduction message
This reference credits the introduction to you:
Email me the referral details
More options Send us this result or get a copy by email
Know a business that needs a website or SEO?
Introduce them and earn a referral reward. They work with us directly.
- Projects: 10%, at least $100
- Monthly services: 10% for the first six months
Your introduction message
This reference credits the introduction to you:
Email me the referral details
How the Header Viewer Works
- Safe fetch, the host is validated before our server requests the URL.
- Follow redirects, each hop is validated and the final URL is reported.
- Read headers, the complete response header set is captured.
- Audit security, key security headers are checked as present or missing.
Why Headers Matter
- Security, headers like HSTS and CSP defend against common attacks.
- Performance, cache and compression headers control speed and cost.
- Correct content, content type and charset ensure proper rendering.
- Debugging, status codes and redirects reveal what is really happening.
If your Cache-Control and compression headers are missing or misconfigured, our website speed and performance optimization service sets them up correctly so repeat visits load instantly. For broader technical fixes across headers, redirects, and crawlability, see our SEO services.
Common HTTP Response Headers Reference
A reference of the response headers you'll see most often, what each one does, and a typical or recommended value. Use it to read the output above and spot missing protections.
| Header | Purpose | Typical / recommended value |
|---|---|---|
| Content-Type | Declares the media type and character set of the response body. | text/html; charset=UTF-8 |
| Cache-Control | Controls how browsers and CDNs cache and revalidate the response. | public, max-age=31536000, immutable for static assets |
| Strict-Transport-Security | Forces browsers to use HTTPS for future requests (HSTS). | max-age=31536000; includeSubDomains |
| Content-Security-Policy | Restricts which sources can load scripts, styles, and other content to limit XSS. | default-src 'self' (tighten per site) |
| X-Content-Type-Options | Stops browsers from MIME-sniffing a response away from its declared type. | nosniff |
| ETag | A content fingerprint used to validate cached copies and return 304s. | "33a64df5..." (server-generated) |
| Content-Encoding | Indicates the compression applied to the response body. | br (Brotli) or gzip |
| Server | Names the web server software handling the request. | nginx (often hidden for security) |
| Set-Cookie | Sets a cookie on the client for sessions or preferences. | id=...; Secure; HttpOnly; SameSite=Lax |
Next steps
HTTP Header Viewer related tools and articles
Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.