Author Topic: SSL certificate authorities - differences  (Read 6593 times)

caine

  • Newbie
  • *
  • Posts: 18
    • View Profile
    • Email
SSL certificate authorities - differences
« on: August 10, 2016, 04:54:40 PM »
Been looking into SSL certificates for a whole host of reasons. Seems no one would stand on a godaddy SSL even if it was to wipe the crap off the shoe; why are the same certificates but from different authorities so widely priced ? Currently looking at Komodo SSL EV which is a decent price in the UK, any reason not to rely on Komodo ?

Drastic

  • Need a bigger hammer...
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3087
  • Resident Redneck
    • View Profile
Re: SSL certificate authorities - differences
« Reply #1 on: August 10, 2016, 06:34:30 PM »
Just for seo boost?

Commodo ssl are fine. 9 bucks at namecheap.

Adam C

  • Inner Core
  • Hero Member
  • *
  • Posts: 622
    • View Profile
Re: SSL certificate authorities - differences
« Reply #2 on: August 10, 2016, 06:53:50 PM »
>>SEO boost

Are you seeing one from moving to SSL?

I'm staring down the barrel of an SSL migration with an expectation that the short term likely best case scenario is we don't f### our traffic levels, but no previous first hand experience.

bill

  • Devil's Avocado
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1286
  • Avast!
    • View Profile
    • Email
Re: SSL certificate authorities - differences
« Reply #3 on: August 11, 2016, 01:27:10 AM »
Comodo and Go Daddy certs are the same level in my book. I don't want to use either. There were a lot of Comodo issues in the past that swore me off of them (although I have a few remaining). DigiCert seems a lot more reputable in this market, although I'm seriously looking at Let's Encrypt certs for a lot of sites.

jetboy

  • Inner Core
  • Sr. Member
  • *
  • Posts: 433
  • Hens of warfare!
    • View Profile
    • Email
Re: SSL certificate authorities - differences
« Reply #4 on: August 11, 2016, 07:33:50 AM »
RapidSSL is a cheaper Geotrust, and preferable to Comodo.

caine

  • Newbie
  • *
  • Posts: 18
    • View Profile
    • Email
Re: SSL certificate authorities - differences
« Reply #5 on: August 11, 2016, 09:51:21 AM »
Thanks for the heads up on Komodo, we have bought them from PAIR but for remote vpn. Will look into the other suggestions. Does the EV level certificates really carry extra kudos ? Such as the green address bar and the extra vendor checks, etc. Noticed not alot of green url bars on many a site.

Many reasons for it. However one of our WP sites has managed to get about 5% of its pure http pages listed as https (which don't exist) on google. Effectively they resolve as an incorrect setup server page; which is definitely bad for ranking/business. Though I've added some rules to stop the indexing of https, I've been warned this could lead to bigger issues.

I'm thinking of taking advantage and redirecting the site to https on an EV level certificate to get a boost. So really its a technical solution and if there is any temporary seo boost great.

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 9293
    • View Profile
Re: SSL certificate authorities - differences
« Reply #6 on: August 11, 2016, 05:00:17 PM »
we don't f### our traffic levels

I can't say anything specific since in our case it's a new site on an existing domain and the switch to https was a small part of it.

Organic traffic did drop initially, but we changed every URL except the home page and redirected about 2/3 and let about 1/3 of the content just die. This resulted in an initial drop of about 7% in organic traffic (sessions) and now running about 4% down (with eight weeks of clean data). Meanwhile, revenue is up a lot b/c of boosts in conversion rate and average order value

Obviously too many factors to make any conclusion about the switch to https (my big worry was the URL changes and content removal), but I can say that we didn't f### our traffic levels and we saw revenue surge... don't want to say more than that on the outside.

Drastic

  • Need a bigger hammer...
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3087
  • Resident Redneck
    • View Profile
Re: SSL certificate authorities - differences
« Reply #7 on: August 11, 2016, 05:34:18 PM »
>>SEO boost

>Are you seeing one from moving to SSL?

I've not switched any yet, but will be soon. New sites get SSL and seem to respond more quickly. I've got anecdotal info from peers of it helping.

>don't want to say more than that on the outside.
same

>There were a lot of Comodo issues in the past that swore me off of them (although I have a few remaining).
Really...I've not had any problems, using on a few sites. What issues have you run into I may need to look out for?

>RapidSSL is a cheaper Geotrust, and preferable to Comodo.
What's preferable about it?

>Many reasons for it. However one of our WP sites has managed to get about 5% of its pure http pages listed as https (which don't exist) on google. Effectively they resolve as an incorrect setup server page; which is definitely bad for ranking/business. Though I've added some rules to stop the indexing of https, I've been warned this could lead to bigger issues.

I think you should have your entire site either SSL or not, and not doing so is causing you problems. If you want ssl, all your http should redirect to https.

My understanding is the boost is simply from properly set up SSL, nothing to do with type or level. EV level stuff is only for the verified business info and green bar, overkill for most sites.

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 9293
    • View Profile
Re: SSL certificate authorities - differences
« Reply #8 on: August 11, 2016, 08:03:16 PM »
I think you should have your entire site either SSL or not, and not doing so is causing you problems. If you want ssl, all your http should redirect to https.

Agreed. And check your redirect hops. Our devs originally set it up so that each redirect action, including http -> https was a hop. So if we had a URL that was used in print in the form

example.com/DealPage

That would get linked like
http://example.com/DealPage

And that would need these hops
http://example.com/DealPage
https://example.com/DealPage
https://www.example.com/DealPage
https://www.example.com/dealpage
https://www.example.com/newdealpage

There were a few special cases that would hit 5 hops (e.g. trailing slash), which Google says is their max they generally follow. It took me a while to explain to the devs that this is actually a problem, especially for users on 3G who will incur a 200ms to 400ms penalty for each hop (depending on whether it involves a new DNS lookup or not).

If you look around, it's pretty common when people switch over to https, they do so as an added hop, rather than going through their existing redirects and fixing them.

caine

  • Newbie
  • *
  • Posts: 18
    • View Profile
    • Email
Re: SSL certificate authorities - differences
« Reply #9 on: August 12, 2016, 02:37:33 PM »
I think you should have your entire site either SSL or not, and not doing so is causing you problems. If you want ssl, all your http should redirect to https.
Agreed. And check your redirect hops. Our devs originally set it up so that each redirect action, including http -> https was a hop. So if we had a URL that was used in print in the form
Very true gents. It was pure HTTP until a limited number of non existent HTTPS pages listed in the index. Checked all the 301's (all dating back to 2015) nothing obvious that would affect approx 4% of pages from a 3000 page site. Started about 3-4 weeks ago (when I noticed the issue). May have been when WC2.6 was released or a kin. Thinking about it a google analytics plugin went on the fritz around about then also. No idea where google is getting the https from, screamingfrog finds none. Hence why I'm thinking to buy a certificate and turn the entire site https; least the currently index https pages will resolve properly rather than pick up penalties. The EV cert was just trying to stand out a little. My logic is probably skewed on the matter.

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 9293
    • View Profile
Re: SSL certificate authorities - differences
« Reply #10 on: August 12, 2016, 05:40:05 PM »
I know I'm getting off topic, but one more thing I forgot to mention, which I *rarely* see mentioned when people talk about the SEO costs/benefits of https: referrer data.

If you are http and your referrer is https, no referrer data is passed.

Quote
A user agent MUST NOT send a Referer header field in an unsecured HTTP request if the referring page was received with a secure protocol.
https://tools.ietf.org/html/rfc7231#section-5.5.2

By far the biggest component of our referral traffic on some of our sites is from .gov domains. When the .gov sites switched en masse to https, Direct traffic shot up and referral traffic plummeted on our sites that are http only.

Being on http takes away a key analytical tool as more and more of the sites linking to you go https.

An example - here's referrer traffic as a referring site rolled out https



bill

  • Devil's Avocado
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1286
  • Avast!
    • View Profile
    • Email
Re: SSL certificate authorities - differences
« Reply #11 on: August 30, 2016, 04:24:30 AM »
>There were a lot of Comodo issues in the past that swore me off of them (although I have a few remaining).
Really...I've not had any problems, using on a few sites. What issues have you run into I may need to look out for?

I've not had specific issues with the certs themselves (my remaining ones are from Pair too), but rather the company as a whole. They have a pretty cavalier attitude toward security that hasn't improved over the years.

Some examples:
They'll issue a cert for just about anyone. Back in 2008 here's a story where someone got a Mozilla.com cert just for asking https://blog.startcom.org/?p=145
Then there was ComodoGate https://www.f-secure.com/weblog/archives/00002128.html in 2011 where they did essentially the same thing again.
On the side they release products that are themselves security threats, like their browser http://www.pcworld.com/article/3029435/security/custom-web-browser-from-comodo-poses-security-threat-researcher-says.html , and their 'security kit' http://www.theregister.co.uk/2016/02/18/comodo_flaw/
Most recently they were just being dicks trying to trademark "Let's Encrypt" https://letsencrypt.org/2016/06/23/defending-our-brand.html

There are more examples out there, but after years of this sort of news I actively try to stay away from their products.

Torben

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 305
    • View Profile
Re: SSL certificate authorities - differences
« Reply #12 on: August 30, 2016, 12:58:32 PM »
I've just used Let's Encrypt for the first time. It's free but it is also very easy to use: https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

Torben

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 305
    • View Profile
Re: SSL certificate authorities - differences
« Reply #13 on: October 20, 2016, 02:26:39 PM »
>>SEO boost
http://searchengineland.com/googles-https-algorithm-two-years-later-still-looks-url-give-ranking-boost-261156 - "Google’s HTTPS algorithm still only looks at the URL to give ranking boost"

They don't even care about mixed http/https