I browse a stupid number of sites a day. I was trying to browse soylentnews.org, and from the looks of it the SSL Cert Expired last night/this morning. And since they have HSTS enabled, the website is not browseable what so ever in firefox Mozilla Connect as they strickly follow the spec and don't allow user overrides, but I can browse it in Google Chrome go figure. I do not really like using Google Chrome, due to how much information it sends back to Google. Will save that rant for another day.
I do remember a time when most websites were not required to have SSL. SSL was very processor intensive on older computers didn't help matter either. Also geting an SSL cert was extremly painfully slow process to get a Certificate signed by one of the big SSL providers. So using SSL was reserved for portions of the website that required data entry, logins, shoping carts, and the rest of the website was unencrypted. But now it has been pushed to being a MUST have feature, and not an option. Here a list of reasons why CloudFlare says we should use SSL/HTTPS. There are now many free providers of SSL Certificates, the one I have used is LetsEncrypt, and use "Community Certificate Manger", which has worked fine up to recently. But looks like my main site is grandfathered in, but any sub site I create get stuck in DNSSEC hell aka the Bogus [BadRequest :: urn:ietf:params:acme:error:dns] error and simply can't figure out how to get past this.
I ended up using another free certifate proivder (Zero SSL), So I was able to get valid / working SSL on my subdomains.