Security Headers Report

• Warning

  Strict-Transport-Security HSTS

  8/15 8/15

  Tells browsers to only use HTTPS for all future requests. Prevents protocol downgrade attacks and cookie hijacking.

  max-age=2592000; includeSubDomains
  • max-age is less than one year. Consider raising it to 31536000 (one year) or more.
  • The preload directive is missing. Consider adding it and submitting the site to the HSTS preload list.
  • includeSubDomains is set.
• Pass

  X-Frame-Options XFO

  8/8 8/8

  Protects against clickjacking by controlling whether the site can be embedded in iframes. Largely superseded by CSP frame-ancestors but still widely supported.

  DENY
  • DENY is the most restrictive setting. Pages can not be embedded anywhere.
• Pass

  X-Content-Type-Options XCTO

  8/8 8/8

  Prevents browsers from MIME-sniffing a response away from the declared content type, reducing exposure to drive-by download attacks.

  nosniff
  • nosniff is set correctly.
• Fail

  Content-Security-Policy CSP

  0/25 0/25

  The most powerful security header. It controls which resources the browser may load, which mitigates XSS, data injection and other code injection attacks.

  Not set
  • CSP is not set. It is the most important security header: it controls which resources can be loaded and mitigates XSS attacks.
  Recommended

  Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests

• Pass

  Referrer-Policy RP

  8/8 8/8

  Controls how much referrer information is sent with requests. Restricting it protects user privacy and avoids leaking sensitive URLs.

  no-referrer-when-downgrade
  • The policy is a safe choice.
• Fail

  Permissions-Policy PP

  0/8 0/8

  Controls access to browser features and APIs such as the camera, microphone and geolocation. Replaces the deprecated Feature-Policy header.

  Not set
  • Permissions-Policy is missing. Scripts may use browser features like the camera, microphone and geolocation without restriction.
  Recommended

  Permissions-Policy: accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()

• Fail

  X-XSS-Protection XXP

  2/5 2/5

  Legacy header for the XSS filter in older browsers. Modern browsers ignore it and a strong CSP is preferred. A wrong value can introduce vulnerabilities.

  1
  • "1" and "1; mode=block" can introduce vulnerabilities in some browsers. The recommended value is 0.
• Fail

  Cross-Origin-Embedder-Policy COEP

  0/7 0/7

  Prevents a document from loading cross-origin resources that do not explicitly grant permission. Required for cross-origin isolation.

  Not set
  • COEP is not set. It is required for cross-origin isolation, which enables features like SharedArrayBuffer.
  Recommended

  Cross-Origin-Embedder-Policy: require-corp

• Fail

  Cross-Origin-Opener-Policy COOP

  0/7 0/7

  Isolates the browsing context group, which protects against cross-origin attacks such as XS-Leaks and Spectre.

  Not set
  • COOP is not set. The browsing context is not isolated, which leaves the site open to XS-Leaks and Spectre-style attacks.
  Recommended

  Cross-Origin-Opener-Policy: same-origin

• Fail

  Cross-Origin-Resource-Policy CORP

  0/7 0/7

  Says whether other sites may include the resource, which protects against some cross-origin information leaks and side-channel attacks.

  Not set
  • CORP is not set. Other sites may be able to include your resources, which can enable information leaks.
  Recommended

  Cross-Origin-Resource-Policy: same-origin

These response headers may reveal details about the server software and technology stack, which helps attackers plan an attack.

• medium

  Server

  cloudflare

  Remove or mask the Server header so it does not disclose the web server software and version.

• high

  X-Powered-By

  PHP/8.5.12

  Remove the X-Powered-By header. It exposes your PHP version and other details of your stack.

• medium

  X-Generator

  Drupal 11 (https://www.drupal.org)

  Remove the X-Generator header so it does not disclose your CMS and its version.

• low

  X-Drupal-Cache

  HIT

  The X-Drupal-Cache header reveals that the site runs Drupal. Consider removing it in production.

• low

  X-Drupal-Dynamic-Cache

  HIT

  The X-Drupal-Dynamic-Cache header reveals Drupal's caching internals. Consider removing it in production.

• low

  Via

  1.1 varnish

  The Via header reveals proxy server information. Consider masking it in production.