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
19 86.4%
1 4.5%
Invalid
1 4.5%
1 4.5%
SASL mechanisms 13 results
Mechanism
# times offered before TLS
# times offered after TLS
PLAIN
2 15.4%
12 92.3%
SCRAM-SHA-1
2 15.4%
10 76.9%
SCRAM-SHA-1-PLUS
0 0%
6 46.2%
DIGEST-MD5
1 7.7%
2 15.4%
SCRAM-SHA-256
0 0%
1 7.7%
SCRAM-SHA-256-PLUS
0 0%
1 7.7%
SCRAM-SHA-512
0 0%
1 7.7%
SCRAM-SHA-512-PLUS
0 0%
1 7.7%
ANONYMOUS
1 7.7%
1 7.7%
X-OAUTH2
0 0%
1 7.7%
CISCO-VTG-TOKEN
0 0%
1 7.7%
CRAM-MD5
1 7.7%
1 7.7%
OAUTHBEARER
0 0%
1 7.7%
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 0 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.