Your site is configured with extremely broad resource sharing permissions.
This can be dangerous, and is possibly not what was intended.
Wondering where to start?
Adding HTTPS protects your site's visitors from tracking, malware, and injected advertising.
Many services providers and certificate authorities now provide free HTTPS and digital certificates to make this as painless as possible!
We noticed that your site is accessible over HTTPS, but still defaults to HTTP.
Automatically redirecting from HTTP to HTTPS helps ensure that your users get served a secure version of your site.
Fantastic work using HTTPS! Did you know that you can ensure users never visit your site over HTTP accidentally?
HTTP Strict Transport Security tells web browsers to only access your site over HTTPS in the future, even if the user attempts to visit over HTTP or clicks an http://
link.
You're doing a great job with HTTPS and HTTP Strict Transport Security!
Since you’re now only allowing connections over HTTPS, consider using the Secure
flag to protect your cookies against their accidental transmission over HTTP. Furthermore, the use of HttpOnly
protects your session cookies from malicious JavaScript.
What’s a good next step?
The use of the X-Frame-Options
header and Content Security Policy’s frame-ancestors
directive are a simple and easy way to protect your site against clickjacking attacks.
You’re halfway finished! Nice job!
The X-Content-Type-Options
header tells browsers to stop automatically detecting the contents of files. This protects against attacks where they're tricked into incorrectly interpreting files as JavaScript.
You’re doing a wonderful job so far!
Did you know that a strong Content Security Policy (CSP) policy can help protect your website against malicious cross-site scripting attacks?
We’ve noticed you’re using other domains to host your JavaScript code.
Subresource Integrity guarantees that your site will stay safe even if one of those domains is compromised.
You’re on the home stretch!
The use of Referrer Policy can help protect the privacy of your users by restricting the information that browsers provide when accessing resources kept on other sites.
Almost there!
Your current CSP policy allows the use of 'unsafe-inline'
inside of style-src
. Moving style
attributes into external stylesheets not only makes you safer, but also makes your code easier to maintain.
🎉🎉🎉 We don't have any! 🎉🎉🎉
Make sure to check back occasionally to ensure that your website is keeping up with the latest in web security standards.
In the meantime, thanks for everything you're doing to keep the internet a safe, secure, and private place!
Once you've successfully completed your change, click Initiate Rescan for the next piece of advice.