HTTP Headers Analyzer

5 / 10
https://jycgvvcgsd.wordpress.com
WordPress โ†’ Nginx โ†’ Browser
9 missing headers, 1 warnings, 2 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 sat, 24 oct 2026 18:44: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.
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, content-type, cookie 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.
x-hacker want root? visit join.a8c.com/hacker and mention this header. An Easter egg header used by GitHub. It typically contains a witty message or recruitment information.
host-header wordpress.com The Host-Header is a non-standard header often used in setups with a reverse proxy or CDN. It typically preserves the original Host header sent by the client, while the standard Host header may be modified to route the request to the correct backend server. This allows the backend to know the original hostname requested by the client, which can be crucial for proper request handling in multi-domain environments.
link <https://public-api.wordpress.com/wp-json/?rest_route=/sites/jycgvvcgsd.wordpress.com>; rel="https://api.w.org/" rel="https://api.w.org/" is where you can learn more about WordPress' REST API. Applications can interact with this WordPress site by sending and receiving JSON objects.
link <https://wp.me/gvjm2>; rel=shortlink rel="shortlink" specifies a shorter URL for the current page, to be used in space-constrained interfaces or for manual entry.
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-ac 1.dca _dca stale
x-remembering eric binnion <https://friendsofericbinnion.wordpress.com/>
alt-svc clear 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.
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.
server-timing a8c-cdn, dc;desc=dca, cache;desc=stale;dur=3.0 Exposes server-side performance metrics (e.g. database query time, cache lookups, total processing time) to the browser. These metrics appear in the browser's DevTools Network tab, making it easier to diagnose slow responses without needing server-side log access.
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.