Security Report Summary
|20 Feb 2024 23:10:14 UTC
|Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.
|Mon, 24 Aug 2020 18:02:56 GMT
|Tue, 20 Feb 2024 23:10:12 GMT
|pin-sha256="BcGdwcLlTO7h+oLaLH7ZTl/yvuQremaJNJxCVBLgLsU="; pin-sha256="YLh1dUR9y6Kja30RrAn7JKnbQG/uEtLMkBgFF2Fuihg="; pin-sha256="Vjs8r4z+80wjNcr1YKepWQboSIRi63WsWXhIMN+eWys="; max-age=2592000
|h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
|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".
|Feature Policy has been renamed to Permissions Policy, see the details here.
|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.
|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. Analyse this policy in more detail. You can sign up for a free account on Report URI to collect reports about problems on your site.
|X Content Security Policy is required for CSP support in IE 10 and IE 11. For other modern browsers the Content-Security-Policy header should be used.
|X-Webkit-CSP is required for CSP support in older Chrome, Safari and other Webkit based browsers. For other modern browsers the Content-Security-Policy header should be used.
|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-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.
|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.
|HTTP Public Key Pinning protects your site from MiTM attacks using rogue X.509 certificates. By whitelisting only the identities that the browser should trust, your users are protected in the event a certificate authority is compromised. Analyse this policy in more detail.