Is it no longer correct to call it an 'SSL' certificate?

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
  • website

    Let's Encrypt Website and Documentation (by letsencrypt)

    But the SSL protocol is dead. TLS is the protocol used now... A colleague recently teased me saying I shouldn't call them that anymore. And indeed I took a look on and they call them TLS certificates now too. To me it seemed a bit pedantic to use the more 'technically correct' term instead of what I thought was the universally understood word for "website encryption" - especially when I'm talking to end users, management etc.

  • OpenSSL

    TLS/SSL and crypto library

    Which it apparently was actually called in 1998 and then changed just before release:

  • Scout APM

    Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts