Dries Buytaert

HTTP Headers Analyzer

7 / 10
https://shinebros.ca
Website → Browser
8 missing headers, 0 warnings, 1 notices
Header
Value
Explanation
cache-control
max-age=3600
max-age specifies the maximum amount of seconds a page is considered valid. The higher max-age, the longer a page can be cached.
content-type
text/html; charset=utf-8
The type of the message body, specified as a MIME type.
etag
"f68132e5d57609b7c5a403d7aa4b52106ff5878eed75af64ca1ef1383bb153d1"
A unique identifier that changes every time a page at a given URL changes. It acts as a fingerprint. A cache can compare Etag values to see if the page has changed and became stale. For example, a browsers will send the ETag value of a cached page in an If-None-Match header. The web server compares the ETag value sent by the browser with the ETag value of the current version of the page. If both values are the same, the web server sends back a 304 Not Modified status and no body.
last-modified
mon, 26 may 2025 18:54:25 gmt
The date and time at which the origin server believes the page was last modified.
Notice Because there is an Etag header, Last-Modified is likely to be ignored. The ETag hash is more accurate than the date/time in Last-Modified. Consider removing Last-Modified to save bandwidth and processing power.
strict-transport-security
max-age=31556926
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.
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
sun, 08 jun 2025 01:37:49 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.
x-served-by
cache-iad-kcgs7200147-iad
Fastly's shield and edge servers that were queried for the request.
x-cache
hit
The page was served from a cache.
x-cache-hits
0
The number of times this page has been served from the Varnish cache. Higher numbers are better.
x-timer
s1749346670.692803,vs0,ve12
Provides timing information about the journey of a request through Fastly's network. Format: s<timestamp>,vs<seconds>,ve<seconds>, where s is the start time of the request, ve stands for Varnish start and ve stands for Varnish end. The length of the trip is ve - vs milliseconds.
vary
x-fh-requested-host, 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.
alt-svc
h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":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.
ma=86400 specifies that the alternative service information is fresh for 86400 seconds.
ma=86400 specifies that the alternative service information is fresh for 86400 seconds.
content-length
19474
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-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.