According to Qualy’s SSL Labs, this site’s SSL cert is for *.stackexchange.com, with the alternative names,

*.stackexchange.com stackexchange.com meta.stackexchange.com *.meta.stackexchange.com *.stackoverflow.com stackoverflow.com serverfault.com stackauth.com sstatic.net meta.serverfault.com superuser.com meta.superuser.com stackapps.com openid.stackauth.com

Wow, that’s a lot of alternative names.

You may notice some overlap. One name is meta.stackexchange.com and another is *.stackexchange.com. There doesn’t seem to be any reason to have a specific cert for meta. Is there?

  • 3
  • Unless, maybe, meta.stackexchange.com is needed to also allow for *.meta.stackexchange.com (but I doubt that)?
    – Arjan
    Feb 9 '14 at 21:16
  • @Arjan: Not *.meta.stackexchange.com, but meta.*.stackexchange.com. Programmers' meta site is meta.programmers.stackexchange.com
    – user102937
    Feb 9 '14 at 23:51
  • This is true, @Robert, but no meta.*.stackexchange.com certificate exists (nor would it be accepted if it did, as the link in rene's comment makes clear), however, a *.meta.stackexchange.com cert does exist, for whatever reason.
    – TRiG
    Feb 10 '14 at 0:28

You must log in to answer this question.

Browse other questions tagged .