mirror of
https://github.com/certbot/certbot.git
synced 2026-01-26 07:41:33 +03:00
remove webhosting, fold ciphersuite
This commit is contained in:
Noah Swartz
114
docs/ciphers.rst
114
docs/ciphers.rst
@@ -205,3 +205,117 @@ so far is redirecting HTTP requests to HTTPS in web servers, the
|
||||
"redirect" enhancement). The changes here would probably be either a new
|
||||
"ciphersuite" enhancement in each plugin that provides an installer,
|
||||
or a family of enhancements, one per selectable ciphersuite configuration.
|
||||
|
||||
Feedback
|
||||
----
|
||||
We recieve lots of feedback on the type of ciphersuites that Let's Encrypt supports and list some coallated feedback below. This section aims to track suggestions and references that people have offered or identified to improve the ciphersuites that Let's Encrypt enables when configuring TLS on servers.
|
||||
|
||||
Because of the Chatham House Rule applicable to some of the discussions, people are *not* individually credited for their suggestions, but most suggestions here were made or found by other people, and I thank them for their contributions.
|
||||
|
||||
Some people provided rationale information mostly having to do with compatibility of particular user-agents (especially UAs that don't support ECC, or that don't support DH groups > 1024 bits). Some ciphersuite configurations have been chosen to try to increase compatibility with older UAs while allowing newer UAs to negotiate stronger crypto. For example, some configurations forego forward secrecy entirely for connections from old UAs, like by offering ECDHE and RSA key exchange, but no DHE at all. (There are UAs that can fail the negotiation completely if a DHE ciphersuite with prime > 1024 bits is offered.)
|
||||
|
||||
## References ##
|
||||
|
||||
### RFC 7575 ###
|
||||
|
||||
IETF has published a BCP document, RFC 7525, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"
|
||||
|
||||
https://datatracker.ietf.org/doc/rfc7525/
|
||||
|
||||
### BetterCrypto.org ###
|
||||
|
||||
BetterCrypto.org, a collaboration of mostly European IT security experts, has published a draft paper, "Applied Crypto Hardening"
|
||||
|
||||
https://bettercrypto.org/static/applied-crypto-hardening.pdf
|
||||
|
||||
### FF-DHE Internet-Draft ###
|
||||
|
||||
Gillmor's Internet-Draft "Negotiated Discrete Log Diffie-Hellman Ephemeral Parameters for TLS" is being developed at the IETF TLS WG. It advocates using *standardized* DH groups in all cases, not individually-chosen ones (mostly because of the Triple Handshake attack which can involve maliciously choosing invalid DH groups). The draft provides a list of recommended groups, with primes beginning at 2048 bits and going up from there. It also has a new protocol mechanism for agreeing to use these groups, with the possibility of backwards compatibility (and use of weaker DH groups) for older clients and servers that don't know about this mechanism.
|
||||
|
||||
https://tools.ietf.org/html/draft-ietf-tls-negotiated-ff-dhe-10
|
||||
|
||||
### Mozilla ###
|
||||
|
||||
Mozilla's general server configuration guidance is available at https://wiki.mozilla.org/Security/Server_Side_TLS
|
||||
|
||||
Mozilla has also produced a configuration generator: https://mozilla.github.io/server-side-tls/ssl-config-generator/
|
||||
|
||||
### Dutch National Cyber Security Centre ###
|
||||
|
||||
The Dutch National Cyber Security Centre has published guidance on "ICT-beveiligingsrichtlijnen voor Transport Layer Security (TLS)" ("IT Security Guidelines for Transport Layer Security (TLS)"). These are available only in Dutch at
|
||||
|
||||
https://www.ncsc.nl/dienstverlening/expertise-advies/kennisdeling/whitepapers/ict-beveiligingsrichtlijnen-voor-transport-layer-security-tls.html
|
||||
|
||||
I have access to an English-language summary of the recommendations.
|
||||
|
||||
### Keylength.com ###
|
||||
|
||||
Damien Giry collects recommendations by academic researchers and standards organizations about keylengths for particular cryptoperiods, years, or security levels. The keylength recommendations of the various sources are summarized in a chart. This site has been updated over time and includes expert guidance from eight sources published between 2000 and 2015.
|
||||
|
||||
http://www.keylength.com/
|
||||
|
||||
### NIST ###
|
||||
NISA published its "NIST Special Publication 800-52 Revision 1: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations"
|
||||
|
||||
http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r1.pdf
|
||||
|
||||
and its "NIST Special Publication 800-57: Recommendation for Key Management – Part 1: General (Revision 3)"
|
||||
|
||||
http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57_part1_rev3_general.pdf
|
||||
|
||||
### ENISA ###
|
||||
|
||||
ENISA published its "Algorithms, Key Sizes and Parameters Report - 2013"
|
||||
|
||||
https://www.enisa.europa.eu/activities/identity-and-trust/library/deliverables/algorithms-key-sizes-and-parameters-report
|
||||
|
||||
## WeakDH/Logjam ##
|
||||
|
||||
The WeakDH/Logjam research has thrown into question the safety of some existing practice using DH ciphersuites, especially the use of standardized groups with a prime ≤ 1024 bits. The authors provided detailed guidance, including ciphersuite lists, at
|
||||
|
||||
https://weakdh.org/sysadmin.html
|
||||
|
||||
These lists may have been derived from Mozilla's recommendations.
|
||||
One of the authors clarified his view of the priorities for various changes as a result of the research at
|
||||
|
||||
https://www.ietf.org/mail-archive/web/tls/current/msg16496.html
|
||||
|
||||
In particular, he supports ECDHE and also supports the use of the standardized groups in the FF-DHE Internet-Draft mentioned above (which isn't clear from the group's original recommendations).
|
||||
|
||||
## Particular sites' opinions or configurations ##
|
||||
|
||||
### Amazon ELB ###
|
||||
|
||||
Amazon ELB explains its current ciphersuite choices at
|
||||
|
||||
https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-security-policy-table.html
|
||||
|
||||
### U.S. Government 18F ###
|
||||
|
||||
The 18F site (https://18f.gsa.gov/) is using
|
||||
|
||||
`ssl_ciphers 'kEECDH+ECDSA+AES128 kEECDH+ECDSA+AES256 kEECDH+AES128 kEECDH+AES256 kEDH+AES128 kEDH+AES256 DES-CBC3-SHA +SHA !aNULL !eNULL !LOW !MD5 !EXP !DSS !PSK !SRP !kECDH !CAMELLIA !RC4 !SEED';`
|
||||
|
||||
### Duraconf ###
|
||||
|
||||
The Duraconf project collects particular configuration files, with an apparent focus on avoiding the use of obsolete symmetric ciphers and hash functions, and favoring forward secrecy while not requiring it.
|
||||
|
||||
https://github.com/ioerror/duraconf
|
||||
|
||||
## Site scanning or rating tools ##
|
||||
|
||||
### Qualys SSL Labs ###
|
||||
|
||||
Qualys offers the best-known TLS security scanner, maintained by Ivan Ristić.
|
||||
|
||||
https://www.ssllabs.com/
|
||||
|
||||
### Dutch NCSC ###
|
||||
|
||||
The Dutch NCSC, mentioned above, has also made available its own site security scanner which indicates how well sites comply with the recommendations.
|
||||
|
||||
https://en.internet.nl/
|
||||
|
||||
## Java compatibility issue ##
|
||||
|
||||
A lot of backward-compatibility concerns have to do with Java hard-coding DHE primes to a 1024-bit limit, accepting DHE ciphersuites in negotiation, and then aborting the connection entirely if a prime > 1024 bits is presented. The simple summary is that servers offering a Java-compatible DHE ciphersuite in preference to other Java-compatible ciphersuites, and then presenting a DH group with a prime > 1024 bits, will be completely incompatible with clients running some versions of Java. (This may also be the case with very old MSIE versions...?) There are various strategies for dealing with this, and maybe we can document the options here.
|
||||
|
||||
@@ -1,113 +0,0 @@
|
||||
This page aims to track suggestions and references that people have offered or identified to improve the ciphersuites that Let's Encrypt enables when configuring TLS on servers.
|
||||
|
||||
Because of the Chatham House Rule applicable to some of the discussions, people are *not* individually credited for their suggestions, but most suggestions here were made or found by other people, and I thank them for their contributions.
|
||||
|
||||
Some people provided rationale information mostly having to do with compatibility of particular user-agents (especially UAs that don't support ECC, or that don't support DH groups > 1024 bits). Some ciphersuite configurations have been chosen to try to increase compatibility with older UAs while allowing newer UAs to negotiate stronger crypto. For example, some configurations forego forward secrecy entirely for connections from old UAs, like by offering ECDHE and RSA key exchange, but no DHE at all. (There are UAs that can fail the negotiation completely if a DHE ciphersuite with prime > 1024 bits is offered.)
|
||||
|
||||
## References ##
|
||||
|
||||
### RFC 7575 ###
|
||||
|
||||
IETF has published a BCP document, RFC 7525, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"
|
||||
|
||||
https://datatracker.ietf.org/doc/rfc7525/
|
||||
|
||||
### BetterCrypto.org ###
|
||||
|
||||
BetterCrypto.org, a collaboration of mostly European IT security experts, has published a draft paper, "Applied Crypto Hardening"
|
||||
|
||||
https://bettercrypto.org/static/applied-crypto-hardening.pdf
|
||||
|
||||
### FF-DHE Internet-Draft ###
|
||||
|
||||
Gillmor's Internet-Draft "Negotiated Discrete Log Diffie-Hellman Ephemeral Parameters for TLS" is being developed at the IETF TLS WG. It advocates using *standardized* DH groups in all cases, not individually-chosen ones (mostly because of the Triple Handshake attack which can involve maliciously choosing invalid DH groups). The draft provides a list of recommended groups, with primes beginning at 2048 bits and going up from there. It also has a new protocol mechanism for agreeing to use these groups, with the possibility of backwards compatibility (and use of weaker DH groups) for older clients and servers that don't know about this mechanism.
|
||||
|
||||
https://tools.ietf.org/html/draft-ietf-tls-negotiated-ff-dhe-10
|
||||
|
||||
### Mozilla ###
|
||||
|
||||
Mozilla's general server configuration guidance is available at https://wiki.mozilla.org/Security/Server_Side_TLS
|
||||
|
||||
Mozilla has also produced a configuration generator: https://mozilla.github.io/server-side-tls/ssl-config-generator/
|
||||
|
||||
### Dutch National Cyber Security Centre ###
|
||||
|
||||
The Dutch National Cyber Security Centre has published guidance on "ICT-beveiligingsrichtlijnen voor Transport Layer Security (TLS)" ("IT Security Guidelines for Transport Layer Security (TLS)"). These are available only in Dutch at
|
||||
|
||||
https://www.ncsc.nl/dienstverlening/expertise-advies/kennisdeling/whitepapers/ict-beveiligingsrichtlijnen-voor-transport-layer-security-tls.html
|
||||
|
||||
I have access to an English-language summary of the recommendations.
|
||||
|
||||
### Keylength.com ###
|
||||
|
||||
Damien Giry collects recommendations by academic researchers and standards organizations about keylengths for particular cryptoperiods, years, or security levels. The keylength recommendations of the various sources are summarized in a chart. This site has been updated over time and includes expert guidance from eight sources published between 2000 and 2015.
|
||||
|
||||
http://www.keylength.com/
|
||||
|
||||
### NIST ###
|
||||
|
||||
NISA published its "NIST Special Publication 800-52 Revision 1: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations"
|
||||
|
||||
http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r1.pdf
|
||||
|
||||
and its "NIST Special Publication 800-57: Recommendation for Key Management – Part 1: General (Revision 3)"
|
||||
|
||||
http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57_part1_rev3_general.pdf
|
||||
|
||||
### ENISA ###
|
||||
|
||||
ENISA published its "Algorithms, Key Sizes and Parameters Report - 2013"
|
||||
|
||||
https://www.enisa.europa.eu/activities/identity-and-trust/library/deliverables/algorithms-key-sizes-and-parameters-report
|
||||
|
||||
## WeakDH/Logjam ##
|
||||
|
||||
The WeakDH/Logjam research has thrown into question the safety of some existing practice using DH ciphersuites, especially the use of standardized groups with a prime ≤ 1024 bits. The authors provided detailed guidance, including ciphersuite lists, at
|
||||
|
||||
https://weakdh.org/sysadmin.html
|
||||
|
||||
These lists may have been derived from Mozilla's recommendations.
|
||||
|
||||
One of the authors clarified his view of the priorities for various changes as a result of the research at
|
||||
|
||||
https://www.ietf.org/mail-archive/web/tls/current/msg16496.html
|
||||
|
||||
In particular, he supports ECDHE and also supports the use of the standardized groups in the FF-DHE Internet-Draft mentioned above (which isn't clear from the group's original recommendations).
|
||||
|
||||
## Particular sites' opinions or configurations ##
|
||||
|
||||
### Amazon ELB ###
|
||||
|
||||
Amazon ELB explains its current ciphersuite choices at
|
||||
|
||||
https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-security-policy-table.html
|
||||
|
||||
### U.S. Government 18F ###
|
||||
|
||||
The 18F site (https://18f.gsa.gov/) is using
|
||||
|
||||
`ssl_ciphers 'kEECDH+ECDSA+AES128 kEECDH+ECDSA+AES256 kEECDH+AES128 kEECDH+AES256 kEDH+AES128 kEDH+AES256 DES-CBC3-SHA +SHA !aNULL !eNULL !LOW !MD5 !EXP !DSS !PSK !SRP !kECDH !CAMELLIA !RC4 !SEED';`
|
||||
|
||||
### Duraconf ###
|
||||
|
||||
The Duraconf project collects particular configuration files, with an apparent focus on avoiding the use of obsolete symmetric ciphers and hash functions, and favoring forward secrecy while not requiring it.
|
||||
|
||||
https://github.com/ioerror/duraconf
|
||||
|
||||
## Site scanning or rating tools ##
|
||||
|
||||
### Qualys SSL Labs ###
|
||||
|
||||
Qualys offers the best-known TLS security scanner, maintained by Ivan Ristić.
|
||||
|
||||
https://www.ssllabs.com/
|
||||
|
||||
### Dutch NCSC ###
|
||||
|
||||
The Dutch NCSC, mentioned above, has also made available its own site security scanner which indicates how well sites comply with the recommendations.
|
||||
|
||||
https://en.internet.nl/
|
||||
|
||||
## Java compatibility issue ##
|
||||
|
||||
A lot of backward-compatibility concerns have to do with Java hard-coding DHE primes to a 1024-bit limit, accepting DHE ciphersuites in negotiation, and then aborting the connection entirely if a prime > 1024 bits is presented. The simple summary is that servers offering a Java-compatible DHE ciphersuite in preference to other Java-compatible ciphersuites, and then presenting a DH group with a prime > 1024 bits, will be completely incompatible with clients running some versions of Java. (This may also be the case with very old MSIE versions...?) There are various strategies for dealing with this, and maybe we can document the options here.
|
||||
@@ -1,144 +0,0 @@
|
||||
# Web Hosting Providers Let's Encrypt Support Status
|
||||
|
||||
_This is a community maintained list and does not guarantee implementation._
|
||||
|
||||
## Web Hosting Providers with Let's Encrypt Support
|
||||
|
||||
* [34SP.com](https://www.34SP.com) ([Source](https://www.34sp.com/hosting-news/blog/lets-encrypt-free-ssl-certificates/))
|
||||
* [a2hosting.com](https://a2hosting.com) ([Source](https://www.a2hosting.com/kb/security/ssl/securing-your-site-with-a-lets-encrypt-ssl-certificate))
|
||||
* [Active24.co.uk](https://www.active24.co.uk) ([Source](https://translate.google.com/translate?hl=en&sl=auto&tl=en&u=https%3A%2F%2Fblog.active24.cz%2F2016%2F06%2Fduveryhodne-certifikaty-lets-encrypt-zdarma-ke-kazdemu-linux-hostingu-od-active-24%2F))
|
||||
* [Active24.cz](https://www.active24.cz) ([Source](https://blog.active24.cz/2016/06/duveryhodne-certifikaty-lets-encrypt-zdarma-ke-kazdemu-linux-hostingu-od-active-24/))
|
||||
* [all-inkl.com](http://all-inkl.com) ([Source](http://kasserver.com/news.php#111), [more detailed instructions](https://www.ra-networks.at/2015/12/07/lets-encrypt-mit-all-inkl-com-nutzen/#comment-279)) (*both in German*)
|
||||
* [Apis Networks](https://apisnetworks.com/)([Source](http://updates.apisnetworks.com/2016/02/lets-encrypt-is-here/))
|
||||
* [blueboard.cz](https://blueboard.cz) ([Source](https://blog.blueboard.cz/ssl-certifikaty-pro-vsechny-klienty-zdarma/))
|
||||
* [Brontobytes](https://www.brontobytes.com/) ([Source](https://www.brontobytes.com/announcements/39/Free-SSL-Certificate-for-everyone.html))
|
||||
* [Brownrice Internet](https://hosting.brownrice.com) ([Source](http://blog.brownrice.com/2016/server-stuff/letsencrypt-automated-fee-ssl/))
|
||||
* [Buyshared.net](http://buyshared.net/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/57))
|
||||
* [Certified Hosting](http://certifiedhosting.com/) ([Source](http://certifiedhosting.com/blog/tech-news/free-ssl-for-everyone/))
|
||||
* [checkdomain](https://www.checkdomain.de/) ([Source](https://www.checkdomain.de/ssl/zertifikat/ssl-free/))
|
||||
* [Cloudways](https://www.cloudways.com/) ([Source](http://www.cloudways.com/blog/lets-encrypt-free-ssl-on-cloud/))
|
||||
* [Configbox](https://www.configbox.com/) ([Source](http://www.cloudways.com/blog/lets-encrypt-free-ssl-on-cloud/))
|
||||
* [Cyon.ch](https://www.cyon.ch/) ([Source](https://www.cyon.ch/blog/Lets-Encrypt-ist-da-Kostenlose-SSL-Zertifikate-fuer-alle))
|
||||
* [Deep.ch](http://deep.ch/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/51))
|
||||
* [Digital Ocean](http://www.digitalocean.com/) ([Source](https://www.digitalocean.com/community/tutorials/how-to-set-up-let-s-encrypt-certificates-for-multiple-apache-virtual-hosts-on-ubuntu-14-04))
|
||||
* [Domain & Webspace Tremmel](https://www.domain-and-webspace.com/) ([Source](https://www.domain-and-webspace.com/en/webspace/2gb))
|
||||
* [Dreamhost.com](https://www.dreamhost.com/) ([Source](https://www.dreamhost.com/blog/2016/01/20/free-ssltls-certificates-at-dreamhost-with-lets-encrypt/))
|
||||
* [Dwe Gruppe](https://www.dwe-gruppe.eu) ([Source *in German*](https://www.dwe-gruppe.eu/news/18/news_single.html))
|
||||
* [EDIS.AT, Austria](http://www.edis.at/) ([Source](http://www.edis.at/de/hosting/letsencrypt-ssl-tls-zertifikate/))
|
||||
* [Eidolonhost.com](https://eidolonhost.com) ([Source](https://eidolonhost.com/forums/index.php/topic,2.0.html))
|
||||
* [ElbiaHosting.sk](http://www.elbiahosting.sk/) ([Source](https://www.facebook.com/elbiahosting/photos/a.591086047574269.148637.556646721018202/1221680761181458/))
|
||||
* [Espace2001.com](https://www.espace2001.com) ([Source](http://cp.espace2001.com/announcements.php?id=8))
|
||||
* [EvenNode.com](http://www.evennode.com) ([Source](http://blog.evennode.com/lets-encrypt-ssl-certificates-support/))
|
||||
* [FlockHosting](http://flockhosting.com/) ([Source](http://blog.flockhosting.com/tags/free-ssl/))
|
||||
* [fortrabbit](https://www.fortrabbit.com) ([Source](https://blog.fortrabbit.com/tls-free-launched))
|
||||
* [Funio.com](https://www.funio.com) ([Source](https://kb.funio.com/view/id/98912157/))
|
||||
* [Gandi](https://www.gandi.net) ([Source](https://www.gandi.net/news/en/2016-01-12/6677-free_tlsssl_certificates_with_lets_encrypt_and_gandi/))
|
||||
* [GeekGhost](http://geekghost.net) ([Source](http://geekghost.net/1479-2/))
|
||||
* [GoDaddy](https://www.godaddy.com/) ([Source](https://www.godaddy.com/help/install-a-lets-encrypt-ssl-apache-20245)) Limited on shared hosting
|
||||
* [Host4Geeks](https://host4geeks.com) ([Source](https://host4geeks.com/lets-encrypt-free-ssl-certificates/))
|
||||
* [Hosting4Real](http://hosting4real.net/)
|
||||
* [Hosting90 Systems](https://www.hosting90.cz/) ([Source](https://twitter.com/hosting90/status/711898647806533633))
|
||||
* [HostM.com](https://www.hostm.com) ([Source](https://www.hostm.com/free-ssl-certificates))
|
||||
* [hostNET.de](https://www.hostnet.de) ([Source](https://www.hostnet.de/faq/wie-kann-ich-letsencrypt-nutzen.html))
|
||||
* [Inertia Networks](https://inertianetworks.com) ([Source](https://secure.inertianetworks.com/inetsrv5/plugin/support_manager/knowledgebase/view/7/issuing-let-s-encrypt-ssl-certificates/2/))
|
||||
* [Infomaniak](https://infomaniak.com/) ([Source](https://news.infomaniak.com/en/certificats-ssl-gratuits-chez-infomaniak/))
|
||||
* [KeyCDN](https://www.keycdn.com) ([Source](https://www.keycdn.com/blog/free-ssl-certificates/))
|
||||
* [KingHost](http://www.kinghost.com.br/) ([Source in portuguese](http://www.kinghost.com.br/certificado-ssl))
|
||||
* [KLE-Hosting](https://www.kle-hosting.de) ([Source in Germany](https://www.kle-hosting.de/webhosting/))
|
||||
* [Krystal Hosting](https://krystal.co.uk/)([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/86))
|
||||
* [Level27](https://level27.be) ([Source](https://level27.be/blog/lets-encrypt))
|
||||
* [madRooster.com](http://www.madrooster.com/) ([Source](https://twitter.com/madRooster/status/721742100757393410))
|
||||
* [manitu](https://www.manitu.de) ([Source](https://www.manitu.de/webhosting/))
|
||||
* [MilesWeb](https://www.milesweb.com) ([Source](https://twitter.com/chinmaydingore/status/691988956565495808))
|
||||
* [MonsterMegs](https://www.monstermegs.com) ([Source](https://blog.monstermegs.com/free-lets-encrypt-ssl-certificates/))
|
||||
* [Mydevil.net](https://www.mydevil.net/) ([Source](https://wiki.mydevil.net/Let's_Encrypt))
|
||||
* [Mythic Beasts](https://www.mythic-beasts.com/) ([Source](http://blog.mythic-beasts.com/2016/01/29/free-ssl-certificates-for-hosting-accounts/))
|
||||
* [Neostrada.nl](https://www.neostrada.nl/) ([Source](https://www.neostrada.nl/letsencrypt-hosting.html)) (*both in Dutch*)
|
||||
* [Netcup.de] (https://www.netcup.de/) ([Source](http://www.netcup-news.de/2016/02/04/lets-encrypt-internetprovider-netcup-integriert-kostenlose-ssl-zertifikate-in-webhosting-angebote-2/))
|
||||
* [NewHostServers.net](http://newhostservers.com/)([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/85))
|
||||
* [Ngage Hosting](https://www.ngagehosting.uk/) ([Source](https://clients.ngagehosting.uk/knowledgebase.php?action=displayarticle&id=1))
|
||||
* [Novatrend.ch](https://www.novatrend.ch/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-letsencrypt-org/6920/18))
|
||||
* [Ntechit.de](https://ntechit.de/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/35))
|
||||
* [Nucleus.be](https://www.nucleus.be) ([Source](https://www.nucleus.be/en/blog/free-ssl-certificates-for-all-customers/))
|
||||
* [Online.net](https://www.online.net/) ([Source](https://community.letsencrypt.org/t/shared-hosting/384/11))
|
||||
* [Openminds.be](https://www.openminds.be/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-letsencrypt-org/6920/22))
|
||||
* [OVH.com](https://www.ovh.com) ([Source](https://www.ovh.com/fr/hebergement-web/ssl_mutualise.xml))
|
||||
* [Planethoster.net](https://www.planethoster.net/) ([Source](https://forums.planethoster.net/threads/exclusive-free-ssl-to-all-our-customers.4731/#post-17876))
|
||||
* [Pressjitsu.com](https://pressjitsu.com/) ([Source](https://pressjitsu.com/blog/ssl-wordpress-letsencrypt/))
|
||||
* [Progreso.pl](https://progreso.pl/) ([Source](https://progreso.pl/o_nas/newsroom/#news_78))
|
||||
* [PulseHeberg.com](http://pulseheberg.com/) ([Source](https://community.letsencrypt.org/t/shared-hosting/384/16))
|
||||
* [ResellerChoice](https://www.resellerchoice.com)
|
||||
* [Schokokeks.org](https://schokokeks.org/) ([Source](https://schokokeks.org/blog/https-f-r-alle-mit-lets-encrypt))
|
||||
* [Sensson](https://www.sensson.net) ([Source](https://www.sensson.net/2016/02/21/webhosting-met-ssl-certificaten-van-letsencrypt/))
|
||||
* [ServerPilot](https://serverpilot.io/) ([Source](https://serverpilot.io/blog/2016/03/09/free-ssl-certificates-from-lets-encrypt.html))
|
||||
* [Serversaurus](https://www.serversaurus.com.au/) ([Source](https://blog.serversaurus.com.au/free-ssl-with-lets-encrypt/))
|
||||
* [SiteGround.com](https://www.siteground.com/) ([Source](https://www.siteground.com/blog/lets-encrypt/))
|
||||
* [Squidix](https://squidix.com/) ([Source](https://squidix.com/blog/squidix-is-now-support-lets-encrypt-on-all-sharedresellersemi-plans/))
|
||||
* [Strony-Domeny.pl](https://strony-domeny.pl/) ([Source](https://strony-domeny.pl/blogtech/9/Lets-encrypt-darmowy-certyfikat-SSL.html))
|
||||
* [TD Web Services](https://tdwebservices.com/)
|
||||
* [Thisistap](https://thisistap.com/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/52))
|
||||
* [Tiger Technologies](https://www.tigertech.net/) ([Source](https://blog.tigertech.net/posts/lets-encrypt/))
|
||||
* [Top Host](https://www.tophost.gr/) ([Source](https://support.tophost.gr/kb/article.php?id=1410)) -- Greek
|
||||
* [TrafficPlanet Hosting](https://trafficplanethosting.com/) ([Source](https://trafficplanethosting.com/page/free-ssl-certificates/))
|
||||
* [Uberspace.de](https://uberspace.de/) ([Source](https://blog.uberspace.de/lets-encrypt-rollt-an/))
|
||||
* [UnoEuro](https://en.unoeuro.com/) ([Source](https://blog.unoeuro.com/2016/04/ny-feature-lets-encrypt-certifikater/) *– in Danish*)
|
||||
* [UnoEuro](https://www.unoeuro.com) ([Source *in Danish*](https://blog.unoeuro.com/2016/ny-feature-lets-encrypt-certifikater/))
|
||||
* [VentraIP Australia](https://ventraip.com.au/) ([Source](https://ventraip.com.au/blog/announcements/lets-encrypt-free-ssl-certificates-now-available/))
|
||||
* [Webfaction](https://webfaction.com/) ([some support](https://community.webfaction.com/questions/19722/is-the-letsencrypt-certificate-service-supported/19723) including [a third-party open-source utility to automate the process](https://github.com/will-in-wi/letsencrypt-webfaction), and [wider support depends on formal release of Let's Encrypt](https://community.webfaction.com/questions/18989/using-lets-encrypt-to-get-ssl-certificates/18990)
|
||||
* [webgo](https://www.webgo.de/) ([Source](https://www.webgo.de/blog/webgo-webhosting-jetzt-kostenlos-ssl-verschluesselung-nutzen-mit-lets-encrypt/))
|
||||
* [WebhostOne](https://www.webhostone.de/) ([Source](https://www.webhostone.de/lets-encrypt.html))
|
||||
* [Websupport.sk](https://websupport.sk/) ([Source *in Slovak*](https://www.websupport.sk/blog/2016/02/lets-encrypt-ssl-certifikat-zadarmo-pre-kazdeho/))
|
||||
* [Wetopi](https://wetopi.com/) ([Source](https://wetopi.com/wordpress-ssl))
|
||||
* [WordPress.com](https://wordpress.com/) ([Source](https://en.blog.wordpress.com/2016/04/08/https-everywhere-encryption-for-all-wordpress-com-sites/))
|
||||
* [World4You Internet Services GmbH](https://www.world4you.com/) ([Source *in German*] (https://www.world4you.at/de/webhosting/ssl.html/))
|
||||
* [wp-webhosting.de](https://www.wp-webhosting.de/) ([Source *in German*](https://www.internetwerk.de/blog/webhosting/2015/12/04/kostenlose-ssl-zertifikate-fuer-alle/))
|
||||
* [XiNiX](http://www.xinix.co/) ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/66))
|
||||
* [Zuver](https://zuver.net.au/) ([Source](https://forums.whirlpool.net.au/archive/2467065#r50573142))
|
||||
|
||||
***
|
||||
|
||||
## Planned:
|
||||
* [Kinsta](https://kinsta.com/)
|
||||
* [Pagely](https://pagely.com/)
|
||||
* [pair Networks](https://www.pair.com/) Ability to automate certificate installation is in long-term plans. (via support email)
|
||||
* [RAIDBOXES.de](https://raidboxes.de/) / [RAIDBOXES.eu](https://raidboxes.eu/)
|
||||
|
||||
***
|
||||
|
||||
## Waiting/Delayed
|
||||
|
||||
* [Hostgator] (https://www.hostgator.com/) Implementation of Let's Encrypt has been relayed internally for further consideration. ([Source](https://twitter.com/hgsupport/status/694292490485133313))
|
||||
* [Strato.de] (https://www.strato.de/) Waiting for Let's Encrypt beta to end to evaluate possible adoption for all customers. ([Source *in German*](https://blog.strato.de/verschluesselte-website-bald-standard/))
|
||||
* [Tsohost] (https://www.tsohost.com/) Not supported, but the team are looking into it. ([Source](https://twitter.com/tsohost/status/722448514228318208))
|
||||
|
||||
***
|
||||
|
||||
## Unconfirmed:
|
||||
|
||||
* [spolehlive-servery.cz](https://www.spolehlive-servery.cz) & [cesky-hosting.cz](https://www.cesky-hosting.cz) (information via support ticket; planned to ~ autumn 2016)
|
||||
|
||||
## Dedicated Hosting:
|
||||
|
||||
* All Dedicated hosting supports installation. This is not a link directory page.
|
||||
|
||||
## No Planned Support:
|
||||
|
||||
* 1and1.com ([Source](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/77))
|
||||
* 247-host.com (maybe anytime in the future, via support chat)
|
||||
* Amazili-communication (Not a hosting company)
|
||||
* df.eu (DomainFactory - no plans to support LE, [Source *in German*](https://www.df.eu/forum/threads/76119-Unterst%C3%BCtzung-von-Let-s-encrypt-Langfristiges-SSL-Konzept-von-Domainfactory/page3?p=499684#post499684))
|
||||
* Greengeeks.com (tech support said 'no plans and you can buy our SSL')
|
||||
* HostEurope.de (via email reply from customer support; LE can be installed manually)
|
||||
* Hostinger.com (no plans to support LE)
|
||||
* HostMonster.com ('no plans', via live chat)
|
||||
* Hostpapa.ca (tech support said 'no plans')
|
||||
* Hostripples.com (no plans, via live chat)
|
||||
* Inmotionhosting.com ([Source](https://twitter.com/inmotionhosting/status/678085107891240960))
|
||||
* Linode (doesn't offer shared hosting)
|
||||
* Namecheap.com ([Source](https://gist.github.com/stopspazzing/c871f935771f14933c63))
|
||||
* Netsons.com (no plans to support LE)
|
||||
* Site5.com (no plans to support at all, except unmanaged vps - via support chat)
|
||||
|
||||
## Remarks
|
||||
|
||||
Moved from [forums](https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920/).
|
||||
Reference in New Issue
Block a user