HTTP Headers Analyzer
3 / 10
https://qaumd.kabarkini.info/old/sample.html
Website → CloudFlare → Browser7 missing headers, 3 warnings, 7 notices
The site is using a CDN, but the HTML page is not cached.
Header
Value
Explanation
date
thu, 26 dec 2024 20:49:47 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
.content-length
15
The size of the message body, in bytes.
report-to
{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=zya6l5z0ygfbsrdn%2b%2bqrzuypcn5awnu8k3ob6anhglznm0tw2i4ijx2iv0xxal5khk%2bkxcizdf1%2fo9yqnl1vtfu14y%2bdthl4ubvocgny1lfkjkl8wyuq%2bw2wmrbyhlnkj2psivt%2btw%3d%3d"}],"group":"cf-nel","max_age":604800}
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.nel
{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
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.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.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.referrer-policy
same-origin
When a visitor navigates from one page to another page, browsers often pass along referrer information. The
Referrer-Policy
header controls how much referrer information a browser can share. This is important because private information can be embedded in the path or query string.same-origin
means that the protocol, host, port, path and query string are shared for same-site requests. For cross-site requests, nothing is shared.cache-control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
private
means the response can only be stored by the browser's cache, but not by CDNs, proxies, or any other shared caches.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.max-age
specifies the maximum amount of seconds a page is considered valid. The higher max-age
, the longer a page can be cached.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 It does not make sense to set
must-revalidate
with no-store
; when nothing is cached, there is nothing to revalidate.Notice It does not make sense to set
must-revalidate
with no-cache
; must-revalidate
is implied.Warning Because
max-age
is set to 0 seconds, nothing will ever be cached in shared caches or browsers. Caching is effectively disabled!Notice
no-store
is set, so it does not make sense to set no-cache
as well.Notice
no-store
is set, so it does not make sense to set private
as well.Notice
pre-check
is a legacy directive introduced by Internet Explorer 5 and is no longer supported. No other browser supports it. Including pre-check
is unnecessary, wastes bandwidth and processsing power.Notice
post-check
is a legacy directive introduced by Internet Explorer 5 and is no longer supported. No other browser supports it. Including post-check
is unnecessary, wastes bandwidth and processsing power.expires
thu, 01 jan 1970 00:00:01 gmt
This
Notice Because there is a
Expires
date is in the past: the page is considered stale and will be removed from all caches.Notice Because there is a
Cache-Control
header with a max-age
and/or s-maxage
directive, the Expires
header will be ignored. Consider removing Expires
to save bandwidth and processing power.server
cloudflare
cf-ray
8f83f07c8929241a-iad
The
cf-ray
header provides a unique identifier for each request through Cloudflare. It's useful for troubleshooting and tracking requests in Cloudflare logs.alt-svc
h3=":443"; ma=86400
The
alt-svc
header advertises alternative services for accessing the same resource, enabling protocol negotiation and potential performance improvements.h3
indicates that HTTP/3 is supported. Variants like h3-29
refer to specific drafts of the HTTP/3 protocol.ma=86400
specifies that the alternative service information is fresh for 86400 seconds.server-timing
cfl4;desc="?proto=tcp&rtt=2108&min_rtt=2103&rtt_var=601&sent=6&recv=10&lost=0&retrans=0&sent_bytes=3393&recv_bytes=832&delivery_rate=1361542&cwnd=251&unsent_bytes=0&cid=7c19192709f72104&ts=237&x=0"
Communicates one or more metrics for a given request-response cycle. Can includes metrics for CPU time, database read/writes, file system access, etc.
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.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.