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
20 66.7%
4 13.3%
Invalid
3 10%
3 10%
SASL mechanisms 17 results
Mechanism
# times offered before TLS
# times offered after TLS
PLAIN
3 17.6%
16 94.1%
SCRAM-SHA-1
2 11.8%
13 76.5%
SCRAM-SHA-1-PLUS
0 0%
8 47.1%
X-OAUTH2
1 5.9%
4 23.5%
DIGEST-MD5
2 11.8%
4 23.5%
SCRAM-SHA-256
0 0%
2 11.8%
SCRAM-SHA-256-PLUS
0 0%
2 11.8%
SCRAM-SHA-512
0 0%
2 11.8%
SCRAM-SHA-512-PLUS
0 0%
2 11.8%
CRAM-MD5
1 5.9%
1 5.9%
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.