title: Is self-signed and/or expired HTTPS certificates worse than just using HTTP?
body: <p>Despite the fact that you get a <strong>big red threatening</strong> warning telling you that the certificate  has not been verified by one of those certificate authorities or has expired, what is bad with it in comparison to just using HTTP? Is it worse or not?</p>
  
  <p>According to Google Chrome (<a href="http://www.sslshopper.com/assets/images/chrome-beta-ssl-2.png" rel="noreferrer">http://www.sslshopper.com/assets/images/chrome-beta-ssl-2.png</a>) « an attacker may be trying to intercept yours communication ». What makes this browser and almost all others raising this warning in the case of a self-signed/expired certificate (and I did not write a certificate explicitly verified as invalid) and not in the case of browsing with HTTP? Again, is it less secure than browsing with HTTP?</p>
  
  <p>It is clearly more threatening to browse a website with self-signed HTTPS certificate than browsing the exact same website with HTTP so, are those modern browser behaviors a scam to make honest companies buy SSL certificate that they <strong>may</strong> not need?</p>