Dries Buytaert

HTTP Headers Analyzer

5 / 10
WordPress → LiteSpeed → CloudFlare → Browser
9 missing headers, 2 warnings, 0 notices
sat, 25 mar 2023 04:52:15 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 compairing against Max-Age or Expires.
text/html; charset=utf-8
The type of the message body, specified as a MIME type.
Specifies whether the network connection stays open after the current request. keep-alive specifies that the browser would like to keep the connection open, while close indicates that the browser wants to close the connection.
Some of the software used to generate or serve this page.
Warning Sharing too many details about a server or web application makes it easier for hackers to target a website. Avoid specific version numbers such as 7.4.33, especially when running software that is end-of-life and/or has known security bugs. Consider removing this header. At a miminum, remove any version number.
Instructs Internet Explorer what compatibility mode to use to render this page. For example, ie=9 specifies that the page should be rendered as if the user was using Internet Explorer 9, even if they use Internet Explorer 11 or later. It's basically a hack for working around compatability issues between different versions of Internet Explorer.
A list of request headers that need to be taken into account to determine whether a cached response can be used rather than making a new request with the origin server. The headers specified by Vary must match with those of the cached response.
The page was served from LiteSpeed's cache.
Warning dynamic means that Cloudflare did not cache the HTML page. It's equivalent to a cache miss. Cloudflare's dynamic cache setting only caches static assets like images, videos, CSS files, JavaScript files and more. HTML pages will never be cached and will always be requested from the origin web server. This can be expensive for dynamically generated HTML. To cache HTML files in Cloudflare, change the 'Cache level' setting from dynamic to everything.
The Report-To header instructs the browser where to send "Network Error Logging" (NEL) reports to.
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.
The "Network Error Logging" (NEL) header is used to configure network request logging; enables websites and applications to receive reports about failed network fetches from supporting browsers.
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.
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.
Some of the software used to generate or serve this page.
A unique request ID generated by Cloudflare. Cloudflare's customer support can use this identifier to trace a request through its network.
h3=":443"; ma=86400, h3-29=":443"; ma=86400
Used to promote alternative services through which the same resource can be retrieved.
h3 stands for HTTP/3. The number after the dash indicates the draft; e.g. h3-27 would be draft 27 of the HTTP/3 protocol.
ma is the number of seconds the alternative service is considered fresh.
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.
missing Add a Content-Security-Policy header. The Content-Security-Policy header helps browsers prevent cross site scripting (XSS) and data injection attacks.
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.
missing Add a Permissions-Policy header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.
missing Add a Cross-Origin-Embedder-Policy to specify how this page can be loaded by cross-origin resources.
missing Add a Cross-Origin-Opener-Policy header to opt-in into better browser isolation.
missing Add a Cross-Origin-Resource-Policy header to specify who can load this page.
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-ancestor directive.
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.