Their SSL site still continues to simply not work: www.facebook.com uses an invalid security certificate. The certificate is only valid for the following

Their SSL site still continues to simply not work: www.facebook.com uses an invalid security certificate. The certificate is only valid for the following names: a248.e.akamai.net , *.akamaihd.net This is the biggest problem with the SSL PKI. It is partially responsible for the lackluster deployment of SSL. We need to switch to a TOFU model supplemented by a more nimble version of the current PKI for first connect acceptance. You would not believe how often I run into problems just trying to use SSL on major sites. If you can't trust a large organizations like facebook and akamai to mess up SSL support during problems, you simply will never get it deployed well on all the rest of the sites. SSL is simply a poor user experience. Twitter's SSL site often goes down more often than the main site too. SSL users get a second class experience and that is the most damming thing I can think of for a technology where deployment is so critical.