HTTP Headers Analyzer
1 / 10
https://pokerdom-cq6.top
Website โ Nginx โ Browser9 missing headers, 4 warnings, 8 notices
JSON API
| Header | Value | Explanation |
|---|---|---|
| server | nginx | 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. |
| date | thu, 19 nov 2026 09:10:20 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. |
| set-cookie | aspro_5c15b6eb5d=le7de1vgeor2tpvrjrtvvor30e; path=/ | A cookie that was sent from the server to the browser.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. |
| expires | thu, 19 nov 1981 08:52:00 gmt | This Expires date is in the past: the page is considered stale and will be removed from all caches.Notice The Cache-Control header, introduced in HTTP/1.1, supersedes the Expires header. Use a Cache-Control header with a max-age directive instead of Expires. Cache-Control is more powerful, but also more efficient in that it avoids roundtrips to the origin server.PS: November 19th is my birthday! ๐ |
| cache-control | no-store, no-cache, must-revalidate | 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.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.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. |
| 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. |
| strict-transport-security | max-age=31536000 | 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. |
| alt-svc | quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-t050=":443"; h3-q050=":443";h3-q049=":443";h3-q048=":443"; h3-q046=":443"; h3-q043=":443" | The alt-svc header tells the browser that the same content is available over a different protocol. This allows the browser to upgrade to a faster protocol (e.g. HTTP/3 over QUIC) on subsequent requests without a separate negotiation step.quic indicates support for the QUIC protocol, often synonymous with HTTP/3. |
| content-encoding | gzip | Specifies how the resource is compressed. Not to be confused with Transfer-Encoding which specifies how the data is transferred.gzip means that the data is compressed with gzip.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. |
| 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-content-type-options | missing Add an X-Content-Type-Options: nosniff header to prevent browsers from MIME type sniffing. Without it, browsers may interpret files as a different content type than intended, which can lead to security vulnerabilities. |
|
| 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. |