Which ssl is best: go daddy vs comodo vs rapid etc?

which ssl is better in terms of price, browser recognisability, etc? Go Daddy seems to be used by many people. How well is it recognised by browsers? Is it really bad, what are best alternatives? My shared ssl seems too slow and causes warnings. Any suggestion? Thank you all.

I recommend the Comodo Instant SSL as being the best price for a quality certified SSL.

It is recognized by most browsers and the support is very good.

http://www.instantssl.com/

Secure Socket layer is misunderstood by the vast majority of consumers (much to the delight of Comodo, Thawte and others).

Why is the most expensive ssl cert about 20x the cost of the least expensive ssl cert? The answer can be found in just one word; marketing. If you believe that you are getting a better product, well then, you are.

A single root, 256-bit (which by the way is limited by the browser that you are using at the moment) 99+% recognized CA (Certificate of Authority) is going to run you the princely sum of just under 20 bucks.

You can pay Thawte 20 times that if you like, but you will not get more cert for the money.

Wander over to EV1servers dot com and go through them to get your 256 bit cert. They advertise it as RapidSSL, but you will end up with an Equifax cert. Cool. They were selling them last year for 9.95 (not a typo), then they jumped their prices by 50% this year. Wow!

Your pocketbook will thank you and your customers will think you are just wonderful.

As an addendum, a single root cert is one where there is just one hop from the issuing authority to your website.

Chained roots go through multiple layers of decreasing authorities to finally place their blessing on the encryption between your ip and the destination ip.

Both of my sites: http://roundwoodstudio.com/shop (I can't keep inventory in it)
and http://highlandweb.net are both covered by individual certs from Equifax.

If you visit using FireFox, and slip an 's' after the http, your browser will tell you that the encryption is 256 bit. Military grade. And the RSA key that locks the cert is 1024 bit. (unhackable by humans)

Cool stuff.

1. Do you need to be an EV1servers dot com client?

2. I didn't find Equifax. I found RapidSSL/GeoTrust (unless this is ultimately Equifax):

http://www.ev1servers.com/Dedicated/SSL/RapidSSL.aspx

3. Is the cert issued quickly? (I'm guessing so, but not sure)

Many thanks :-)

I always use Comodo from
http://www.completessl.com/complete_ssl.php
Excellent service with hand holding support, if you are unsure
how to install etc

@DogTags

EV1 will sell to anybody (within reason).

The entire purchase process through EV1 and RapidSSL takes about 10 minutes, including RapidSSL's phone verification.

1. Generate your RSA key.
2. Use that to generate your CSR.
3. Go to EV1 and purchase the cert, pasting the CSR where directed.
4. They email you a link to go in at RapidSSL under their (I'm assuming) account.
5. Verify the info they got from your CSR.
6. Go through their automated phone verification.
   7.RapidSSL emails you an Authorization link to finalize the order.
7. Presto. SSL hot and fresh, emailed to you direct from RapidSSL.

It is in fact an Equifax Secure cert. 256 bit. Just like mom used to make!

These are High Trust Certificates?

Depending on the web server software your hosting company has you hooked up on, there are several different scenarios that could take place during the dance of the SSL installation.

One of the linux flavors running Apache is probably the most surefooted way to publish web pages anyhow, but I digress.

I will go way out on a limb and assume that you might be hosted on a cPanel equipped server. If you are, well good. life is simple again.

Your RSA key and CSR are generated on your domain cPanel. After you have the cert in hand, forward Only the cert ONLY to your friendly support staff who will then set up the appropriate folders under your web root where the cert will reside. The whole process there takes, oh I don't know... maybe 5 minutes.

then you can https:// for another year. :-)

@Merlin

Oh, yes.
I think Douglas (the Head Surfer at EV1) bought a pile of certs a while back and got them at a very deep discount.

Prior to running ThePlanet, Erwin was heavily involved in security technology. He probably knew somebody that knew somebody....

Thanks, Mtnguy, for your suggestions. It is interesting completessl.com suggested by you offers 14.95 $ Rapid ssl which I think better than Go Daddy turbo ssl. Some people commented on the forum here that Go Daddy seal is cheesy. Besides my webhost offers Rapid ssl for 45 USD.

As Scottb suggested Comodo seems very good indeed and to me it looks smart with the floating corner logo.

As long as visitors are not spooked by warnings, it seems ok with either Comodo or Rapid SSL from completessl.com.

At what level sale would you recommend high assurance guys? Or does it depend on something else than sale amount?

As long as visitors are not spooked by warnings, it seems ok with either Comodo or Rapid SSL from completessl.com.
which warnings are you refering to?

warning that ssl does not belong to the domain name (mine for example)

make sure that you are using the EXACT domain name that you secured

https://yourdomain.com and
https://www.yourdomain.com are NOT the same,

Then is there a Comodo SSL module? In the download section, i did not see one. People seem to be talking a lot about the logo only. Or is it the job of the web server?

zenartman:

Thanks, Mtnguy, for your suggestions. It is interesting completessl.com suggested by you offers 14.95 $ Rapid ssl which I think better than Go Daddy turbo ssl. Some people commented on the forum here that Go Daddy seal is cheesy. Besides my webhost offers Rapid ssl for 45 USD.

As Scottb suggested Comodo seems very good indeed and to me it looks smart with the floating corner logo.

As long as visitors are not spooked by warnings, it seems ok with either Comodo or Rapid SSL from completessl.com.

At what level sale would you recommend high assurance guys? Or does it depend on something else than sale amount?

The sale amount has nothing to do with whether a warning is triggered on the server.
You could be selling cruise ships and it would not matter.

What does matter and it seems to pertain exactly to your set up, is that the ssl certificate needs to point exactly to the domain that is to be protected by encryption.

If you already purchase the certificate, there are no do-overs with ssl.
Find out what the exact domain is that you indicated the certificate to cover.

www does matter, so if your cert covers www.yourdomain.com , then your paths need to reflect that in your zen config files.
If the cert covers domain.com (no www) then your paths and URLs in your Zen config files need to reflect that.

I just looked your site, and ssl does not seem to be enabled at this point.

mtnguy :clap: thank you so much, this is just what I needed to hear! :flex: