HTTPS / SSL access to feeds throws a certificate warning / security exception

[fsspnad.com...@gmail.com]

To whom it may concern,

The wildcard SSL certificate you use for Feedburner isn't set up for Feedburner domains, so it throws a security exception.

feeds.feedburner.com uses an invalid security certificate. The certificate is only valid for the following names: *.google.com, *.android.com, *.appengine.google.com, *.cloud.google.com, *.google-analytics.com, *.google.ca, *.google.cl, *.google.co.in, *.google.co.jp, *.google.co.uk, *.google.com.ar, *.google.com.au, *.google.com.br, *.google.com.co, *.google.com.mx, *.google.com.tr, *.google.com.vn, *.google.de, *.google.es, *.google.fr, *.google.hu, *.google.it, *.google.nl, *.google.pl, *.google.pt, *.googleadapis.com, *.googleapis.cn, *.googlecommerce.com, *.googlevideo.com, *.gstatic.cn, *.gstatic.com, *.gvt1.com, *.gvt2.com, *.urchin.com, *.url.google.com, *.youtube-nocookie.com, *.youtube.com, *.youtubeeducation.com, *.ytimg.com, android.com, g.co, goo.gl, google-analytics.com, google.com, googlecommerce.com, urchin.com, youtu.be, youtube.com, youtubeeducation.com (Error code: ssl_error_bad_cert_domain)

Given Google is now using https as a ranking single, maybe Matt Cutts should have told the rest of the company to update their certificates?  Should not there be a security audit to make sure ALL Google domains can be accessed securely, without throwing exceptions?  Please post a comment to this thread when you fix it, so we know it is fixed.

We are trying to secure all the assets on our domain, since it appears Google demoted our site between August 8-12 due to a lack of being accessible via HTTPS, even though we don't allow subscribers and we don't sell anything or have any data that would need to be posted to the site securely.

We appreciate Google imposing what amounts to a $100/year SSL certificate tax, in order to try to recoup the 60% traffic loss and poor rankings we have suffered.