The biggest benefit of using Let's Encrypt is that it delivers reliable, robust, trusted HTTPS encryption without extortionate fees or constant upselling of premium support contracts. Rather than bogging users down in the hairy process of generating and submitting a signing request, it works smoothly with virtual private servers and modern hosting control panels such as cPanel, either through plugins or via straightforward API requests. The fact that Let's Encrypt is endorsed by open-web evangelists like the EFF, Mozilla, and Google gives me strong assurance that it’s committed to supporting a more secure web environment for years to come. And because certificates can be issued swiftly and reliably, both ordinary internet users and corporations can set up private key encryption for one or more domains and meet browser security requirements quickly. Review collected by and hosted on G2.com.

The biggest inconvenience is the 90-day certificate lifespan. While that’s good for security, it means I have to renew certificates every three months if my hosting provider doesn’t offer cron-based auto-renewal scripts. It’s also disappointing that they only provide domain validation certificates; for extended validation, organization validation, or code-signing certificates, I’d have to turn to a commercial CA instead. Auto install is also missing

I also wish hosting providers were more transparent about the options available to their clients. In some cases, they make it impossible for me to use an alternative certificate supplier and effectively push me into buying their expensive add-on for SSL certificate renewal. Review collected by and hosted on G2.com.