W3C home > Mailing lists > Public > www-tag@w3.org > December 2014

Re: Preparing to Publish HTTPS Finding

From: Anne van Kesteren <annevk@annevk.nl>
Date: Sun, 21 Dec 2014 19:06:04 +0100
Message-ID: <CADnb78iFJhNHHxvEK0h37oUue6nsXCsJgXLVDge1ePbR7Vd+0Q@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Chris Palmer <palmer@google.com>, Daniel Appelquist <appelquist@gmail.com>, TAG List <www-tag@w3.org>, Ian Jacobs <ij@w3.org>
On Sun, Dec 21, 2014 at 6:24 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> So what's the cost of a wildcard SSL certificate (someone quoted $100 in a
> previous)?  Is it affordable?

I'm not sure why a wildcard certificate is the benchmark, but you can
get unlimited wildcard certificates that last two years for personal
use for a yearly verification fee of USD 60 with StartSSL.

It's unclear whether Let's Encrypt will issue wildcard certificates,
but they will undoubtedly cover subdomains and since it's a protocol
that essentially comes down to the same thing, unless you reallly need
a wildcard subdomain for some kind of service. And that's completely
free.

Per https://blog.cloudflare.com/introducing-universal-ssl/ CloudFlare
also offers wildcard certificates for free.

Getting access to a certificate is not the problem. Ease of use is.
Mixed Content, HSTS, renewing certificates, etc. all pose additional
challenges to developers. They might be more of a challenge to
non-English speakers, as with the rest of the web, since all
development and documentation is primarily in the English language.
That's not a problem specific to HTTPS however.


-- 
https://annevankesteren.nl/
Received on Sunday, 21 December 2014 18:06:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:08 UTC