title: Is decent HTTPs implementation for medium public site always a paid solution?
body: <p>I'm aware that for adding HTTPs to a site, one can either:</p>
  
  <ol>
  <li>buy a overpriced SSL certificate from a reputed CA like
  VeriSign  </li>
  <li>or purchase a much lower priced certificate from several
  other companies  </li>
  <li>or one could even use his/her own self signed
  certificate i.e, for free.</li>
  </ol>
  
  <p>But for a decent HTTPs implementation that is:</p>
  
  <ol>
  <li>you want <strong>most of standard browsers recognize the certificate</strong>(there shouldn't be any warnings/ errors on standard browsers)</li>
  <li><strong>security is tight rather than just a false impression</strong> of secure site.</li>
  <li><strong>brand name of CA is not that really important</strong> to you.</li>
  <li>for a public site similar to LinkedIn but smaller in scale(no financial transactions, but users profile data).</li>
  <li><strong>economical pricing</strong></li>
  </ol>
  
  <p>Would implementing such an HTTPs always come at a price ? What is the cost effective way to implement it ? I don't want to spend hundred of dollars an year initially, when I have lower user base.</p>