HTTP Headers Analyzer

0 / 10

https://9roe4wokvct.typeform.com/to/sbvVGFtU

Website → Browser
8 missing headers, 5 warnings, 7 notices
JSON API

Header	Value	Explanation
date	sat, 18 jul 2026 20:52:57 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.
set-cookie	awsalbtg=3fdwzj6lyc9bouuwrnyxzcgoanbxlxmwodbzko2kgcubdjdnywy0vyxppg+in9l2vv2hm0baptrecgxhklrlfmexjdrpyegbfdeflaexz/iqjezcp1q834clefuw/1122q3fs+u/6er3wtspzm7jujllxmkqsgq76vroxvehzlpg; expires=sat, 25 jul 2026 20:52:57 gmt; path=/	A cookie that was sent from the server to the browser. `expires=` sets the maximum lifetime of the cookie using a specific date. `path=` indicates the path that must exist in the requested URL for the browser to send the cookie. Warning This cookie is missing the `secure` flag. Without it, the cookie can be sent over unencrypted HTTP connections, making it vulnerable to interception. Notice This cookie is missing the `httponly` flag. Without it, JavaScript can access the cookie, increasing the risk of cross-site scripting (XSS) attacks. Notice This cookie does not set an explicit `samesite` attribute. Browsers default to `lax`, but setting it explicitly is recommended for clarity and cross-browser consistency.
set-cookie	awsalbtgcors=3fdwzj6lyc9bouuwrnyxzcgoanbxlxmwodbzko2kgcubdjdnywy0vyxppg+in9l2vv2hm0baptrecgxhklrlfmexjdrpyegbfdeflaexz/iqjezcp1q834clefuw/1122q3fs+u/6er3wtspzm7jujllxmkqsgq76vroxvehzlpg; expires=sat, 25 jul 2026 20:52:57 gmt; path=/; samesite=none; secure	A cookie that was sent from the server to the browser. `expires=` sets the maximum lifetime of the cookie using a specific date. `path=` indicates the path that must exist in the requested URL for the browser to send the cookie. Warning `samesite=none` instructs the browser to send the cookie to all cross-site requests, such as on requests to load images or frames from other sites. This enables third-party sites to log cookie data. This could lead to data leaks and cross-site request forgery attacks. To improve security, set to `samesite=strict` or `samesite=lax`. `secure` instructs the browser to only send the cookie back when HTTPS requests are used, making it more resistant to man-in-the-middle attacks. Notice This cookie is missing the `httponly` flag. Without it, JavaScript can access the cookie, increasing the risk of cross-site scripting (XSS) attacks.
traceparent	00-7c5c16d6ab6453b2c5c56225d82a776d-195913000e3b50e3-01	A W3C Trace Context header for distributed tracing. Contains a trace ID, span ID, and trace flags that allow requests to be tracked across multiple services and systems.
cache-control	private no-cache no-store max-age=0 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. `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. Every request will hit the origin server. If this page can be cached, consider using `public` with an appropriate `max-age`. `max-age=0` with `must-revalidate` means caching is disabled and all requests must be validated with the origin server. Notice `must-revalidate` has no effect with `no-store` since nothing is cached. Remove `must-revalidate`. Notice `must-revalidate` is redundant with `no-cache` since `no-cache` already requires revalidation. Remove `must-revalidate`. Notice `no-cache` is redundant when `no-store` is set, though some sites keep both for compatibility with older caches. Notice `private` has no effect when `no-store` is set since nothing will be cached. It can be safely removed.
pragma	no-cache	Notice `Pragma: no-cache` forces revalidation with the origin server on every request. `Pragma` is a legacy HTTP/1.0 directive, superseded by `Cache-Control`. Remove `Pragma` to save bandwidth and processing power.
x-cache	hit	The page was served from a cache.
x-cache-lookup	hit	The page was served from a cache.
x-powered-by	29508500838-11.6.3	Some of the software used to generate or serve this page. Warning Sharing too many details about a server or web application makes it easier for hackers to target a website. Avoid specific version numbers such as 11.6.3, especially when running software that is end-of-life and/or has known security bugs. Consider removing this header. At a minimum, remove any version number.
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.
content-encoding	br	Specifies how the resource is compressed. Not to be confused with `Transfer-Encoding` which specifies how the data is transferred. `br` means that the data is compressed with `brotli`. Warning Add a `Content-Length` header. The Content-Length header is required, unless the message is transported using chunked encoding. Without a `Content-Length` header some servers will respond with 400 (bad request) or terminate connections early.
x-envoy-upstream-service-time	24	The time in milliseconds that the Envoy proxy spent waiting for the upstream service to respond. Envoy is used by many cloud platforms including Google Cloud, Istio, and AWS App Mesh.
server	istio-envoy	Identifies the software used by the origin server to handle the request (e.g. Apache, Nginx, Cloudflare). Notice Consider removing or minimizing the `Server` header. Even without a version number, it reveals the server software, which aids reconnaissance.
access-control-allow-methods	get, options, post, put, patch, delete	Part of CORS (Cross-Origin Resource Sharing). Sent in response to a preflight request to indicate which HTTP methods (e.g. `GET`, `POST`, `PUT`) the server allows for cross-origin requests.
access-control-allow-headers	x-typeform-key, content-type, authorization, typeform-version, typeform-app, x-requested-with, anonymousid, x-namespace	Part of CORS (Cross-Origin Resource Sharing). Sent in response to a preflight request to indicate which HTTP headers the server allows in the actual cross-origin request.
access-control-expose-headers	location, x-request-id	Specifies which headers can be exposed to the client in a CORS (Cross-Origin Resource Sharing) context.
strict-transport-security	max-age=63072000; 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. `includesubdomains` instructs the browser that all subdomains are HTTPS-only as well.
x-content-type-options	nosniff	The `X-Content-Type-Options` header prevents browsers from guessing a response's content type. Without it, browsers may interpret files differently than intended, which can lead to security vulnerabilities. The value `nosniff` is correctly set.
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` header. It requires cross-origin resources to explicitly consent before this page can load them, protecting those resources from being exposed to Spectre-style timing attacks. Together with `Cross-Origin-Opener-Policy`, it enables cross-origin isolation and access to `SharedArrayBuffer`.
cross-origin-opener-policy		missing Add a `Cross-Origin-Opener-Policy` header. It prevents other sites from retaining a `window` reference to this page when opened via `window.open()` or navigation, blocking script-based attacks through shared browsing contexts.
cross-origin-resource-policy		missing Add a `Cross-Origin-Resource-Policy` header. It controls which origins can embed or load this page's resources (images, scripts, etc.), preventing hotlinking and cross-origin data leaks.
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-ancestors` 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.