Security Report Summary
|23 Feb 2024 16:28:26 UTC
|Grade capped at A, please see warnings below.
|This policy contains 'unsafe-inline' which is dangerous in the script-src directive. This policy contains 'unsafe-eval' which is dangerous in the script-src directive.
|michelin-crm.sid=s%3AxlggRxnA2xwwkEJKux_2IY0CWYAeUo8I.Uwtz%2BmHavy38jELP59qGjRcN1Ia1ANZzn34Fsw3JX10; Path=/; Expires=Sat, 24 Feb 2024 16:28:26 GMT; HttpOnly; Secure
|default-src *; style-src 'unsafe-inline' *; script-src 'unsafe-inline' 'unsafe-eval' *; font-src *; frame-src 'self' *; connect-src *; img-src * data: blob:; object-src *; worker-src 'self' data: blob:
|Fri, 23 Feb 2024 16:28:26 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.
|X-Powered-By can usually be seen with values like "PHP/5.5.9-1ubuntu4.5" or "ASP.NET". Trying to minimise the amount of information you give out about your server is a good idea. This header should be removed or the value changed.
|The 'httpOnly' flag is not set on this cookie. The 'secure' flag is not set on this cookie. There is no Cookie Prefix on this cookie. This is not a SameSite Cookie.
|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.
|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.
|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".
|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.
|This is a very lax CORS policy. Such a policy should only be used on a public CDN.
|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.