We wrote recently about how Chrome and Firefox have started showing a “Not Secure” warning on webpages that don’t use HTTPS (SSL). And starting in October, Chrome will make this warning much more noticeable.
Welcome to the Banyan Theory blog, where we write about anything and everything related to insurance websites, including design, search engine optimization, and tips to improve your own site.
Blog Articles
This is part of our Why HTTPS series.
Simply supporting SSL on your website isn’t quite enough. However, there are two easy and free things you can do to make your setup much more secure: require HTTPS, and enable HSTS. What do these mean? Read on to find out in this second post in the series.
This is part of our Why HTTPS series.
You may have noticed a strong uptick recently in the number of websites you visit that use HTTPS. Or you may have noticed that many companies, like Google and Safeco, have begun encouraging website owners to support HTTPS on their own websites. If you’re curious about the reasons behind this, and the reasons you should add HTTPS support to your website, you’re in the right place. This is the first of a series of blog posts I’ll be writing on the topic.
Web browsers have changed the way they handle non-HTTPS websites, and more changes are on the way. If you already have our Whole-Site SSL add-on, you’re covered. Otherwise, read on to see how these changes affect your website, and what to do about it.