Security Report Summary
|04 Mar 2024 09:07:15 UTC
|Content Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets.
|X-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. Recommended value "X-Frame-Options: SAMEORIGIN".
|Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites.
|Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.
|The "max-age" directive is too small. The minimum recommended value is 2592000 (30 days).
|Sun, 03 Mar 2024 15:56:33 GMT
|Thu, 01 Jan 1970 00:00:00 GMT
|Cross-Origin Embedder Policy allows a site to prevent assets being loaded that do not grant permission to load them via CORS or CORP.
|Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser.
|Cross-Origin Resource Policy allows a resource owner to specify who can load the resource.
|Server value has been changed. Typically you will see values like "Microsoft-IIS/8.0" or "nginx 1.7.2".
|HTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS by getting the User Agent to enforce the use of HTTPS.
|X-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is "X-Content-Type-Options: nosniff".