Website Building » Squarespace » Why Is My Squarespace Site Showing Not Secure?

Why Is My Squarespace Site Showing Not Secure?

Last updated on October 1, 2022 @ 4:02 am

If you’re seeing a “Not Secure” warning in your browser when visiting a Squarespace site, it’s likely due to one of the following:

Your site is in Development Mode. Any site in Development Mode will show the “Not Secure” warning. To remove the warning, simply launch your site.

Your site has an SSL Certificate, but visitors are accessing it over HTTP instead of HTTPS. To fix this, we recommend enabling SSL for your domain. Once you enable SSL, we’ll automatically redirect visitors from HTTP to HTTPS.

Your site has an SSL Certificate, but mixed content is blocking HTTPS connections. This means that some of the resources on your pages are being loaded over HTTP instead of HTTPS, preventing your page from loading securely. Learn more about mixed content and how to fix it.

Your site doesn’t have an SSL Certificate. We recommend enabling SSL for your domain to create a secure connection and avoid browser warnings.

Conclusion:

If you see a “Not Secure” warning in your browser when visiting a Squarespace site, it’s likely due to one of the following:

• Your site is in Development Mode. Any site in Development Mode will show the “Not Secure” warning. To remove the warning, simply launch your site.

PRO TIP: If you see the “Not Secure” warning in your browser, it means that your Squarespace site isn’t set up to use SSL. This warning appears in Chrome and Firefox when you try to view a page that isn’t served over SSL.

To fix this, you’ll need to enable SSL for your site.

• Your site has an SSL Certificate, but visitors are accessing it over HTTP instead of HTTPS. To fix this, we recommend enabling SSL for your domain.

Once you enable SSL, we’ll automatically redirect visitors from HTTP to HTTPS.

• Your site has an SSL Certificate, but mixed content is blocking HTTPS connections. This means that some of the resources on your pages are being loaded over HTTP instead of HTTPS, preventing your page from loading securely.

• Your site doesn’t have an SSL Certificate. We recommend enabling SSL for your domain to create a secure connection and avoid browser warnings.

Dale Leydon

Dale Leydon

Sysadmin turned Javascript developer. Owner of 20+ apps graveyard, and a couple of successful ones.