Possible Duplicate:
Better HTTPS support for Stack Exchange sites
Google Chrome warning of an SSL problem with Stack Overflow

I tried to navigate to this Stack Overflow answer Hash algorithms - Fastest implementations | Stack Overflow from a website that was not part of Stack Exchange. The Google Chrome browser on Windows 7 returned the following:

Screen capture 21 Oct 2012 approx 3:00 Arizona Time

I am feeling some concern.

  • In my haste, I neglected to obscure all browser my bookmarks. Yes, I am an active Pinterest user.

marked as duplicate by ShaWiz, Bo Persson, Rory, animuson, Martijn Pieters Oct 21 '12 at 13:48

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 5
    Stack Overflow does not use SSL. – BoltClock's a Unicorn Oct 21 '12 at 10:16
  • 1
    You should alert the source of the link and have him put proper link instead. (using http:// rather than https://) – ShaWiz Oct 21 '12 at 11:14
  • Well, https://www.stackoverflow.com is simply a broken link. In my opinion it's no different than stackoverflaw.com or any other wrong/broken link. – ShaWiz Oct 21 '12 at 12:42

The SSL certificate is valid for stackexchange.com, and *.stackexchange.com, while you are visiting stackoverflow.com. That is the reason you are getting that error.

Firefox gives me a similar error. These are the details about the error:

stackoverflow.com uses an invalid security certificate.

The certificate is only valid for the following names: *.stackexchange.com , stackexchange.com


  • Why doesn't this happen with other StackExchange sites from non SE sites e.g. Security StackExchange, when I navigate here security.stackexchange.com/q/20461/12057 with the https? – Ellie Kesselman Oct 21 '12 at 10:25
  • "The SSL certificate is valid for stackexchange.com, and *.stackexchange.com", @Feral – Mat Oct 21 '12 at 10:28
  • Because they are *.stackexchange.com domains. – BoltClock's a Unicorn Oct 21 '12 at 10:28
  • Oh, sigh, sorry! I forgot that stackoverflow has its own domain, that the others are subdomains. And so does SuperUser (have its own domain)! Sorry! – Ellie Kesselman Oct 21 '12 at 10:29
  • So I'd have the same problem with both SuperUser and ServerFault, yes? – Ellie Kesselman Oct 21 '12 at 10:36
  • 1
    @FeralOink I get the same error for Super User. – kiamlaluno Oct 21 '12 at 10:39
  • 1
    @FeralOink The question you linked explains exactly why they are not going to use secure connections on the trilogy sites. As the status is status-deferred, there is the hope they can implement it in the future, but it is not something they can do in the next months. – kiamlaluno Oct 21 '12 at 10:49

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