HTTP Headers Analyzer

1 / 10

https://ssd-2106.blogspot.com

Website → Browser
11 missing headers, 3 warnings, 7 notices
JSON API

Header	Value	Explanation
date	fri, 16 oct 2026 22:59:51 gmt	The date and time at which the request was made. A browser uses it for age calculations rather than using its own internal date and time; e.g. when comparing against `Max-Age` or `Expires`.
pragma	no-cache	Notice `Pragma: no-cache` forces revalidation with the origin server on every request. `Pragma` is a legacy HTTP/1.0 directive, superseded by `Cache-Control`. Remove `Pragma` to save bandwidth and processing power.
expires	fri, 01 jan 1990 00:00:00 gmt	This `Expires` date is in the past: the page is considered stale and will be removed from all caches. Notice The `Cache-Control` header, introduced in HTTP/1.1, supersedes the `Expires` header. Use a `Cache-Control` header with a `max-age` directive instead of `Expires`. `Cache-Control` is more powerful, but also more efficient in that it avoids roundtrips to the origin server.
cache-control	no-store, no-cache, must-revalidate	`no-cache` means the response can be stored by any cache, but the stored response must be validated with the origin server before each reuse. If the origin confirms that the response hasn't changed, downloading of the full response body can be skipped. Warning `no-cache` will cause a revalidation request to the origin server for every use of the cached response. Consider using `public` with appropriate `max-age` to improve caching efficiency. Warning `no-store` means the response may not be stored in any cache, including the browser's cache. Every request will hit the origin server. If this page can be cached, consider using `public` with an appropriate `max-age`. `must-revalidate` indicates that once a page becomes stale, both shared caches and browser caches must not use their stale copy without validating it with the origin server first. Notice `must-revalidate` has no effect with `no-store` since nothing is cached. Remove `must-revalidate`. Notice `must-revalidate` is redundant with `no-cache` since `no-cache` already requires revalidation. Remove `must-revalidate`. Notice `no-cache` is redundant when `no-store` is set, though some sites keep both for compatibility with older caches.
content-type	text/html	The type of the message body, specified as a MIME type.
server	scaffolding on httpserver2	Identifies the software used by the origin server to handle the request (e.g. Apache, Nginx, Cloudflare). Notice Consider removing or minimizing the `Server` header. Even without a version number, it reveals the server software, which aids reconnaissance.
content-length	3185	The size of the message body, in bytes.
x-xss-protection	0	A legacy header that enables the browser's built-in cross-site scripting (XSS) filter. Modern browsers ignore it in favor of `Content-Security-Policy`. Warning `0` disables XSS filtering. Remove this header or set the value to `1`. Notice Add a `Content-Security-Policy` header for more comprehensive protection.
alt-svc	h3=":443"; ma=2592000,h3-29=":443"; ma=2592000	The `alt-svc` header tells the browser that the same content is available over a different protocol. This allows the browser to upgrade to a faster protocol (e.g. HTTP/3 over QUIC) on subsequent requests without a separate negotiation step. `h3` indicates that HTTP/3 is supported. HTTP/3 uses the QUIC protocol (UDP-based) instead of TCP, which eliminates the TCP handshake delay and performs better on lossy networks. Variants like `h3-29` refer to specific drafts of the HTTP/3 protocol. `ma=2592000` specifies that the alternative service information is fresh for 2592000 seconds. `ma=2592000` specifies that the alternative service information is fresh for 2592000 seconds.
strict-transport-security		missing Add a `Strict-Transport-Security` header. The `Strict-Transport-Security` header or HSTS header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication.
content-security-policy		missing Add a `Content-Security-Policy` header. The `Content-Security-Policy` header helps browsers prevent cross site scripting (XSS) and data injection attacks.
referrer-policy		missing Add a `Referrer-Policy` header. When a visitor navigates from one page to another, browsers often pass along referrer information. The `Referrer-Policy` header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the path or query string and passed onto an external destination.
permissions-policy		missing Add a `Permissions-Policy` header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.
cross-origin-embedder-policy		missing Add a `Cross-Origin-Embedder-Policy` header. It requires cross-origin resources to explicitly consent before this page can load them, protecting those resources from being exposed to Spectre-style timing attacks. Together with `Cross-Origin-Opener-Policy`, it enables cross-origin isolation and access to `SharedArrayBuffer`.
cross-origin-opener-policy		missing Add a `Cross-Origin-Opener-Policy` header. It prevents other sites from retaining a `window` reference to this page when opened via `window.open()` or navigation, blocking script-based attacks through shared browsing contexts.
cross-origin-resource-policy		missing Add a `Cross-Origin-Resource-Policy` header. It controls which origins can embed or load this page's resources (images, scripts, etc.), preventing hotlinking and cross-origin data leaks.
x-frame-options		missing Add a `X-Frame-Options` header. The `X-Frame-Options` header prevents this URL from being embedded in an `iframe`. This protects against clickjacking attacks. Alternatively, set a `Content-Security-Policy` header with a `frame-ancestors` directive.
x-content-type-options		missing Add an `X-Content-Type-Options: nosniff` header to prevent browsers from MIME type sniffing. Without it, browsers may interpret files as a different content type than intended, which can lead to security vulnerabilities.
x-permitted-cross-domain-policies		missing Add a `X-Permitted-Cross-Domain-Policies` header to prevent Flash, Adobe Reader and other clients from sharing data across domains.
content-encoding		missing No `Content-Encoding` header found. Enable compression such as `gzip` or `br` (Brotli) to reduce transfer sizes. Brotli typically achieves 15–20% better compression than gzip and is supported by all modern browsers.