Security Report Summary
|20 Feb 2024 23:06:20 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".
|Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.
|Tue, 20 Feb 2024 23:06:19 GMT
|public, must-revalidate, max-age=30
|Wed, 07 Feb 2024 17:22:23 GMT
|max-age=10886400; includeSubDomains; preload
|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.
|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.
|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.
|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".
|X-XSS-Protection sets the configuration for the XSS Auditor built into older browsers. The recommended value was "X-XSS-Protection: 1; mode=block" but you should now look at Content Security Policy instead.