Dries Buytaert

HTTP Headers Analyzer

6 / 10
https://s.id/bestlinkz
Website → Nginx → CloudFlare → Browser
8 missing headers, 0 warnings, 3 notices
Header
Value
Explanation
server
nginx
date
thu, 02 jan 2025 18:41:18 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-type
text/html; charset=utf-8
The type of the message body, specified as a MIME type.
vary
accept-encoding
The 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.
vary
accept-encoding
The 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.
vary
rsc, next-router-state-tree, next-router-prefetch, accept-encoding
The 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 This request has many Vary headers. More headers decrease the likelihood of a cache hit.
x-hit-at
1/3/2025, 01:41:18 gmt+7
cache-control
private, max-age=3600, must-revalidate
private means the response can only be stored by the browser's cache, but not by CDNs, proxies, or any other 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.
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.
strict-transport-security
max-age=15724800; 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.
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.
cf-cache-status
miss
The page was not served from Cloudflare's cache.
last-modified
thu, 02 jan 2025 18:41:18 gmt
The date and time at which the origin server believes the page was last modified.
Notice According to the Last-Modified header the site's content was changed less than ten minutes ago. If that is not the case, consider fixing your Last-Modified headers to improve caching.
report-to
{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=l6fcez8f3tej77wll9tqzbfvtk0najbrr%2b9eb0mv1fy3a7p6m2krvqzduwntxi3fwuzfdihyuk%2fho2sidvbkajyowc3fpa2yleywfyligcztiiaxmqblpjgjcw%2fhcyhtqw%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 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 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-content-type-options
nosniff
The 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.
cf-ray
8fbce1ea28da87bd-sin
The cf-ray header provides a unique identifier for each request through Cloudflare. It's useful for troubleshooting and tracking requests in Cloudflare logs.
server-timing
cfl4;desc="?proto=tcp&rtt=16256&min_rtt=15884&rtt_var=53&sent=3435&recv=1998&lost=0&retrans=0&sent_bytes=3617380&recv_bytes=142962&delivery_rate=3866729&cwnd=265&unsent_bytes=0&cid=0f44c4e5c00dde3f&ts=224919&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.
x-res-time
246596628
x-res-time-human
246.60135ms
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-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-ancestor directive.
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.