HTTP Headers Analyzer
6 / 10
https://www.reddit.com
Website → Varnish → Browser7 missing headers, 1 warnings, 2 notices
Header
Value
Explanation
retry-after
0
The
Retry-After
header indicates how long the user agent should wait before making a follow-up request. It's commonly used with 503 (Service Unavailable) responses or for rate limiting. The value can be either a number of seconds to wait or an HTTP-date after which to retry. This header helps in managing traffic and server load by instructing clients when to retry their requests.cache-control
private, no-store
private
means the response can only be stored by the browser's cache, but not by CDNs, proxies, or any other shared caches.Warning
no-store
means the response may not be stored in any cache, including the browser's cache.Notice
no-store
is set, so it does not make sense to set private
as well.accept-ranges
bytes
Used by the server to advertise its support of partial HTTP requests. The browser can ask for a range or subset of the response body. It's a feature that allows a browser to resume an interrupted download.
bytes
is the only range unit currently supported. none
means that the server does not support range requests.date
sat, 29 mar 2025 11:03:34 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
.via
1.1 varnish
The
Via
header tracks how a page is forwarded from proxy to proxy. Beware, not all proxies append themselves to the Via
header.strict-transport-security
max-age=31536000; includesubdomains
The
Strict-Transport-Security
header (HSTS) instructs browsers to only use HTTPS for future connections to this domain, enhancing security by preventing downgrade attacks and cookie hijacking.max-age
specifies the time, in seconds, that the browser should remember to use HTTPS only for this domain.includesubdomains
instructs the browser that all subdomains are HTTPS-only as well.x-content-type-options
nosniff
The
The value
X-Content-Type-Options
header, when set to nosniff
, prevents MIME type sniffing. This enhances security by ensuring browsers respect the declared Content-Type of the response, mitigating MIME confusion attacks.The value
nosniff
is correctly set, providing protection against MIME type sniffing attacks.x-frame-options
sameorigin
X-Frame-Options
prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks.sameorigin
means that this page can be displayed in a iframe
, but only on the currrent origin. It can't be displayed on another domain. Consider setting this to deny
for added security.x-xss-protection
1; mode=block
This header enables the browser's built-in XSS protection. However, it's considered legacy and modern browsers may ignore it.
Notice While this header provides some protection, it's recommended to use
1
enables the browser's cross-site scripting (XSS) filtering.mode=block
instructs the browser to block the response if a XSS attack is detected, instead of sanitizing the page.Notice While this header provides some protection, it's recommended to use
Content-Security-Policy
instead, as it offers more comprehensive and flexible protection against XSS and other injection attacks.server
snooserv
report-to
{"group": "w3-reporting-nel", "max_age": 14400, "include_subdomains": true, "endpoints": [{ "url": "https://w3-reporting-nel.reddit.com/reports" }]}, {"group": "w3-reporting", "max_age": 14400, "include_subdomains": true, "endpoints": [{ "url": "https://w3-reporting.reddit.com/reports" }]}, {"group": "w3-reporting-csp", "max_age": 14400, "include_subdomains": true, "endpoints": [{ "url": "https://w3-reporting-csp.reddit.com/reports" }]}
This header is part of the Reporting API specification. They are used to configure the reporting of network errors and other issues to a specified endpoint.
The
The
Report-To
header specifies where reports should be sent.group
defines the reporting group. Groups allow reports to be grouped logically; e.g. there could be a group for network errors and a second group for browser feature deprecation reports.max_age
defines the number of seconds the browser should remember these settings. Prevents the browser from having to parse the JSON on each request.endpoints
defines one or more URLs where the reports need to be send to. Multiple URLs can be specified for failover and load-balancing. Endpoints can be assigned a weight
to distribute load, with each endpoint receiving a specified fraction of the reporting traffic. Endpoints can also be assigned a priority
to set up fallback collectors.include_subdomains
is a boolean that enables or disables NEL reporting for subdomains of the origin.nel
{"report_to": "w3-reporting-nel", "max_age": 14400, "include_subdomains": false, "success_fraction": 1.0, "failure_fraction": 1.0}
This header is part of the Reporting API specification. They are used to configure the reporting of network errors and other issues to a specified endpoint.
The
The
NEL
(Network Error Logging) header configures the reporting of network errors.report_to
defines the reporting group that reports for this NEL policy will be sent to. The reporting group details are specified in the Report-To
header.max_age
defines the number of seconds the browser should remember these settings. Prevents the browser from having to parse the JSON on each request.include_subdomains
is a boolean that enables or disables NEL reporting for subdomains of the origin.success_fraction
defines the sampling rate that should be applied to reports about successful network requests. Its value must be a number between 0.0 and 1.0: 0 means no successful requests should be reported, and 1 means that every successful request should be reported.failure_fraction
defines the sampling rate that should be applied to reports about failed network requests. Its value must be a number between 0.0 and 1.0: 0 means no failed requests should be reported, and 1 means that every failed request should be reported.content-length
1485
The size of the message body, in bytes.
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
to specify how this page can be loaded by cross-origin resources.cross-origin-opener-policy
missing Add a
Cross-Origin-Opener-Policy
header to opt-in into better browser isolation.cross-origin-resource-policy
missing Add a
Cross-Origin-Resource-Policy
header to specify who can load this page.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.Questions or feedback? Email dries@buytaert.net.