To do authenticated encryption, a certificate needs to be both trusted and valid. Trusted means it is issued by a well-known CA and valid means it is valid for the domain we want to connect to.
Trusted
Untrusted
Valid
114 82.6%
15 10.9%
Invalid
3 2.2%
6 4.3%
SASL mechanisms 89 results
Mechanism
# times offered before TLS
# times offered after TLS
PLAIN
13 14.6%
86 96.6%
SCRAM-SHA-1
13 14.6%
70 78.7%
SCRAM-SHA-1-PLUS
0 0%
46 51.7%
X-OAUTH2
1 1.1%
25 28.1%
DIGEST-MD5
8 9%
16 18%
CRAM-MD5
5 5.6%
6 6.7%
SCRAM-SHA-512-PLUS
0 0%
5 5.6%
SCRAM-SHA-512
0 0%
5 5.6%
SCRAM-SHA-256-PLUS
0 0%
4 4.5%
SCRAM-SHA-256
0 0%
4 4.5%
ANONYMOUS
2 2.2%
2 2.2%
JIVE-SHAREDSECRET
1 1.1%
1 1.1%
OFCHAT
1 1.1%
1 1.1%
LOGIN
0 0%
1 1.1%
Servers supporting SSL 3, but not TLS 1.0 0 results
SSL 3 and TLS 1.0 are very similar, but TLS 1.0 has some small improvements. This table is meant to help judge whether SSL 3 can be disabled by listing the servers that do support SSL 3, but not TLS 1.0.
Target
Type
When
Servers supporting SSL 2 1 results
SSL 2 is broken and insecure. It is not required for compatibility and servers should disable it.
Servers using <2048-bit RSA certificates which expires after 01-01-2014 0 results
As described in the CA/Browser Forum Baseline Requirements, certificates with RSA keys with less than 2048 bits should not be issued with an notAfter date after 31-12-2013. This list lists all certificates which violate that rule.