HTTP Headers Analyzer
6 / 10
https://www.dreamden.ai
Website → Google Cloud → Browser8 missing headers, 1 warnings, 1 notices
Header
Value
Explanation
link
<https://static.parastorage.com/>; rel=preconnect; crossorigin;,<https://static.parastorage.com/>; rel=preconnect;,<https://static.wixstatic.com/>; rel=preconnect; crossorigin;,<https://static.wixstatic.com/>; rel=preconnect;,<https://siteassets.parastorage.com>; rel=preconnect; crossorigin;,
rel="preconnect" informs the browser that the page intends to establish a connection to the specified server. To reduce latency and optimize performance, the browser is encouraged to establish an HTTP connection as soon as possible. Preconnecting is used when the hostname is known, but the exact URL not yet.x-wix-request-id
1735293321.91058062179222921097
html-cacheable
true
etag
w/"835a51acbbd72585f7782d2adb9a09e4"
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. This particular Etag value starts with w/ which means that it is a weak identifier; while unlikely, multiple pages might have the same identifier. Weak identifiers are used because strong identifiers can be difficult and costly to generate.content-language
en
Specifies the page's intended audience. For example,
en-US means that the document is intended for English language speakers in the United States. The language tags are defined in RFC 5646.strict-transport-security
max-age=86400
The
Notice For optimal security, consider increasing
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.cache-control
public,max-age=0,must-revalidate
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.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.Warning Because
max-age is set to 0 seconds, nothing will ever be cached in shared caches or browsers. Caching is effectively disabled!server
pepyaka
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.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.age
0
The time in seconds that the page has been in the shared proxy cache. The maximum age is set by
max-age or s-maxage in the Cache-Control header.date
fri, 27 dec 2024 09:55:22 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-kjyo7100058-iad
Fastly's shield and edge servers that were queried for the request.
x-cache
miss
The page was not served from a cache.
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.server-timing
cache;desc=miss, varnish;desc=miss_miss, dc;desc=fastly_virginia-pub_g
Communicates one or more metrics for a given request-response cycle. Can includes metrics for CPU time, database read/writes, file system access, etc.
set-cookie
ssr-caching=cache#desc=miss#varnish=miss_miss#dc#desc=fastly_virginia-pub_g; max-age=20
A cookie that was sent from the server to the browser.
max-age= sets the maximum lifetime of the cookie in seconds.x-seen-by
yvsunuo/8ld62ehjr5b7ka==,pmhzlb45npy7b1vbaukqrewfbs+7quvaqsix00yi78k=,m0j2eekngivuw/liy8bllo+sk2wyeny+fb/shwtpui8tfznrrnvyqoekpetnb+u3,2d58ifebgbosy5xc+fralq+7oom4pdmuophnfltbyaj6c4cpvwuhlhin9p4zl2nup339+bpvpqx8jpglmvjmaw==,2unv7koq4ogja5+pksx47fetfey/opb65dw7gsrw9u5bgooyga1mplugppjg4/tb,/b3vgdticcndwqoewfzmmmehdnzrkufitmvj3kreyga=,9y9ychcovzdngbmpbn9neukfqpmbagbdyas9nzk2ku4j6r0azamucqm4c7kwbeya9jkiz/lcov7mazpnsq6/xa==,/b3vgdticcndwqoewfzmmiaplnfeumuejjmcf7m2vdm=,louk8/sagamoxzwtpubo2g3stx+bfq7r6frrzrah4hu15iuyuv0rjn3rflgwilruq18gbomzx7gwbqbx4/inwlpvreabu6qel8hmruonlgi=,/b3vgdticcndwqoewfzmmoo4jhaw2gloyfuxmdlh5eg=,bambrvwsln/v1ztiwxgeomhbgbpn8w66hnurlz+ijse3bsqqcynszaardg+twyc4er693x9pmo07u4lllk13hg==
via
1.1 google
The
Via header tracks how a page is forwarded from proxy to proxy. Beware, not all proxies append themselves to the Via header.glb-x-seen-by
bs8wrlgzu0hc+wryuhb8qig44yfcdcmjrkboq1h6vjc=
alt-svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
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=2592000 specifies that the alternative service information is fresh for 2592000 seconds.ma=2592000 specifies that the alternative service information is fresh for 2592000 seconds.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.