HTTP Headers Analyzer
6 / 10
https://whatweather.today
WordPress → LiteSpeed → CloudFlare → Browser4 missing headers, 2 warnings, 4 notices
The site is using a CDN, but the HTML page is not cached.
Header
Value
Explanation
date
fri, 04 apr 2025 14:18:10 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
.cache-control
public, max-age=0
public
means the response may be stored by all caches, including browser caches, CDNs, and shared caches.max-age
specifies the maximum amount of seconds a page is considered valid. The higher max-age
, the longer a page can be cached.Warning Because
max-age
is set to 0 seconds and no s-maxage
is set, nothing will be cached in browsers or shared caches. Caching is effectively disabled!expires
fri, 04 apr 2025 14:18:09 gmt
The date and time after which the page should be considered stale and all caches should be refreshed.
Notice Because there is a
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.last-modified
thu, 03 apr 2025 19:08:46 gmt
The date and time at which the origin server believes the page was last modified.
vary
accept-encoding,user-agent,accept-encoding
The
Notice Varying on
Vary
header specifies a list of headers that must be considered when caching responses. For a cached response to be used, these headers must match between the cached response and the new request. This ensures that the appropriate version of a resource is served based on factors like language, encoding, or device type.Notice Varying on
user-agent
can lead to low cache efficiency due to the high number of unique user agents. Only use this if you're serving significantly different content based on user agent.platform
hostinger
Some of the software used to generate or serve this page.
panel
hpanel
content-security-policy
upgrade-insecure-requests
The Content Security Policy (CSP) header helps prevent cross-site scripting (XSS), clickjacking, and other code injection attacks by specifying which dynamic resources are allowed to load.
upgrade-insecure-requests
instructs browsers to replace insecure URLs (HTTP) with secure URLs (HTTPS).referrer-policy
strict-origin-when-cross-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.strict-origin-when-cross-origin
means that the protocol, host, port, path and query string are shared for same-site requests. For cross-site requests, protocol, host, and port are shared, but only when the protocol security level remains the same (HTTP → HTTP, HTTPS → HTTPS). For cross-site requests where the protocol becomes less secure (HTTPS → HTTP), nothing is shared.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.
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.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.strict-transport-security
max-age=15552000; includesubdomains; preload
The
Notice For optimal security, consider increasing
Notice In order to be eligible for preloading,
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.Notice For optimal security, consider increasing
max-age
to at least 31,536,000 seconds (1 year), especially if you're considering preloading.includesubdomains
instructs the browser that all subdomains are HTTPS-only as well.preload
recommends the domain for inclusion in browsers' preload lists. If accepted, the domain would get hardcoded into browsers as HTTPS-only.Notice In order to be eligible for preloading,
max-age
must be least 31,536,000 seconds (roughly 1 year).permissions-policy
midi=(),sync-xhr=(),accelerometer=(), gyroscope=(), magnetometer=(), camera=()
Instructs a browser to selectively allow or deny certain browser APIs and features. It helps improve security.
x-turbo-charged-by
litespeed
Some of the software used to generate or serve this page.
cf-cache-status
dynamic
Warning The
dynamic
status indicates that Cloudflare did not cache the requested HTML page, similar to a "cache miss". By default, Cloudflare caches static assets such as images, CSS, and JavaScript but excludes HTML due to its dynamic nature. To cache HTML content, change the 'Cache Level' setting from dynamic
to cache everything
in Cloudflare. This adjustment allows HTML pages to be cached, leveraging Cloudflare's global network for faster and more efficient content delivery.report-to
{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=pgthytvmriokxohmus2gaxj3h1l%2foz3h07g1bpz1vkzwunev6vzirknifrrfwpkv3zhp%2fdgh7z9qzjityrrrf7vcs1shylbtgbxt0vpwdj89odsxnqki8yiv42dpmvepfjl8pw%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.speculation-rules
"/cdn-cgi/speculation"
server
cloudflare
cf-ray
92b16ef939ffc984-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=1502&min_rtt=1491&rtt_var=441&sent=7&recv=10&lost=0&retrans=0&sent_bytes=3417&recv_bytes=816&delivery_rate=1929380&cwnd=233&unsent_bytes=0&cid=e47fae706558218e&ts=77&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.
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.