The https://bing.com has a wildcard certificate that does not include the non-www domain. https://www.bing.com has a certificate for Akamai.
Apparently this has been affecting Bing for at least two hours now. This is pretty embarrassing that the Google-killer would misconfigured their SSL certificates. I guess not enough people use SSL search on Bing to warrant a critical response? Of course non-SSL Bing is unaffected. In contrast Google.com has had SSL by default since 2011.
So is it Microsoft or Akamai that is misconfiguring the SSL certificate?
If you do access Bing through SSL it only redirects you to non-SSL anyway. Pretty sure this certificate issue has been around months anyway.
this issue has been around for years. it’s a known problem at Akamai and as listed in other sites, affects many other of their customers.
I see similar error some times on my friends old/currupted PC. After some time I realise that PC’s clock is set to 2004 or something. After I correct/update the clock the problem resolves.
But in case with Bing, yes the problem still exists reg. https
Its fixed for the US site now. Internationally, we still get broken certificates. bing.no does not match bing.com, go figure.
Google have never had this kind of long-lasting amateurish issues with their certificates.) Bing have 4 % marketshare in Norway. I guess it does not take much to take a chunk of the local market.