HTTP Headers Analyzer
7 / 10
  https://apt123.co.uk/line-bending
WordPress → LiteSpeed → Browser9 missing headers, 0 warnings, 0 notices
Header
    Value
    Explanation
  link
    <https://apt123.co.uk/wp-json/>; 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://apt123.co.uk/wp-json/wp/v2/pages/6454>; rel="alternate"; title="json"; type="application/json"
    Specifies a link that might be of interest to the browser.
  link
    <https://apt123.co.uk/?p=6454>; rel=shortlink
    rel="shortlink" specifies a shorter URL for the current page, to be used in space constrained interfaces and/or for manual entry.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.etag
    "8230-1762210618;;;"
    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.x-litespeed-cache
    hit
    The page was served from LiteSpeed's cache.
  date
    tue, 04 nov 2025 06:10:18 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.server
    litespeed
    
  strict-transport-security
    
    missing Add a 
  Strict-Transport-Security header. The Strict-Transport-Security header or HSTS header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication.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.