When trying to browse https://stackoverflow.com I receive an error that the certificate is not valid. The reason is that *.stackoverflow.com comes with a certificate for *.stackexchange.com at the moment.

More details:

SHA-1 fingerprint of the cert:


Issued by: DigiCert High Assurance CA-3

  • Same problem: tried to reach stackoverflow.com but the server name is *.stackexchange.com on Chrome 33.0.1750.154 m, Windows Seven Enterprise
    – Nk SP
    Apr 8, 2014 at 14:00
  • 4
    Well, they are in the process of re-issuing certificates after fixing a critical bug, guess this will go away by itself when the process will be done. :) Apr 8, 2014 at 14:02
  • 4
    QUICK EVERYBODY EXPLOIT TH— oh. Apr 8, 2014 at 14:04

1 Answer 1


This is a race condition as we upgraded certs immediately but DNS took a bit to catch up. You should now be seeing a valid cert which we'll be updating again as soon as we receive a new combined wildcard for that particular certificate.

Most CAs are a bit busy today which is understandable.

  • 2
    Why are they particularly busy today? Apr 8, 2014 at 15:37
  • 9
    @Duncan In case that wasn't sarcasm here is a link to the reason CAs are busy today. Apr 8, 2014 at 15:42
  • 2
    @MatthewGreen It wasn't sarcasm, thanks for the link. Apr 8, 2014 at 15:43
  • What about per-site-metas? I see the same warning when opening any of them directly using HTTPS.
    – asheeshr
    Apr 8, 2014 at 16:56
  • @AsheeshR we do not support SSL on per-site metas and won't at their current URLs at all. Note: we don't link you to them over https:// either. Apr 8, 2014 at 16:57
  • The "sign in" link does point to https:// Apr 13, 2014 at 18:15
  • @ThiefMaster The "sign in" link doesn't point to the child meta. It would (appropriately) throw an invalid cert warning in almost every browser if it did. Apr 14, 2014 at 3:35
  • I went to meta.arduino.stackexchange.com and clicked "sign up" (sorry, not "sign in"). I ended up in meta.arduino.stackexchange.com/users/… which does not have a valid certificate. Apr 14, 2014 at 7:52
  • @ThiefMaster that's definitely a bug, it'll be fixed in the next build. Apr 14, 2014 at 10:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .