Security Headers Report

• Fail

  Strict-Transport-Security HSTS

  0/15 0/15

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

  Not set
  • HSTS is not set. All modern sites should redirect to HTTPS and set this header with a long max-age.
  Recommended

  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

• Fail

  X-Frame-Options XFO

  0/8 0/8

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

  Not set
  • X-Frame-Options is missing. Other sites may be able to embed your pages in iframes, which enables clickjacking.
  Recommended

  X-Frame-Options: SAMEORIGIN

• Fail

  X-Content-Type-Options XCTO

  0/8 0/8

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

  Not set
  • X-Content-Type-Options is missing. Browsers may MIME-sniff responses, which can enable drive-by download attacks.
  Recommended

  X-Content-Type-Options: nosniff

• 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

• Fail

  Referrer-Policy RP

  0/8 0/8

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

  Not set
  • Referrer-Policy is missing. Browsers may send the full URL to third-party sites as the referrer.
  Recommended

  Referrer-Policy: strict-origin-when-cross-origin

• 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=()

• Warning

  X-XSS-Protection XXP

  3/5 3/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.

  Not set
  • X-XSS-Protection is not set. Modern browsers ignore it, but setting it to 0 is still recommended to avoid bugs in older browsers.
  Recommended

  X-XSS-Protection: 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

  AkamaiGHost

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