openssl VS sslyze

It is not just a theory. A special fork of OpenSSL, maintained by Pluralsight author Peter Mosmans, aims to have as many ciphers as possible. This fork is used and recommended by Mozilla Cipherscan, however, it can offer less than two hundred cipher suites, but there are more than three hundred in the different RFCs according to Cipher Suite Info. The majority of them are weak or insecure, which makes it particularly important to be part of the analysis. In addition, it is also true that there are cipher suites that are not on the Cipher Suite Info list, for instance, Russian standard (GOST) cipher suites. These are rarely used cipher suites, but there is an OpenSSL engine that implements them, so they should be checked.

For Internally and Externally accessible websites – Can use hostname or IP address Sslyze command line tool - https://github.com/nabla-c0d3/sslyze/releases - current version is 4.1.0

3) If you are technically skilled then there are programs/scripts you can run that will tell you exactly what TLS/SSL settings your router supports by scanning it. I have used https://github.com/nabla-c0d3/sslyze in the past but that was a long time ago so not sure it still works well

There are many notable open-source projects (SSLyze, CipherScan, testssl.sh, tls-scan, …) and several SaaS solutions (CryptCheck, CypherCraft, Hardenize, ImmuniWeb, Mozilla Observatory, SSL Labs, …) to do a security setting analysis, especially when we are talking about TLS, which is the most common and popular cryptographic protocol. However, most of these tools heavily depend on one or more versions of one or more cryptographic protocol libraries, like GnuTLS, OpenSSL, or wolfSSL. But why is this such a problem?

SSLyze - Fast and comprehensive TLS/SSL configuration analyzer to help identify security mis-configurations.