Qualys SSL Labs fails to load the link you give me reason, "No secure ciphers supported." Which I think is a bug because I've gotten that twice today. When a b

Qualys SSL Labs fails to load the link you give me reason, "No secure ciphers supported." Which I think is a bug because I've gotten that twice today. When a browser and web server agree on a cipher suite its not necessarily the most 'secure', just the first they agree on. This is largely controlled by the client. Who basically iterates over their list (from lowest to smallest). Do you have 0x002F? (128bit AES DHE). No. And you continue to count upwards. By the time you reach more powerful suites that use SHA256/386 (~0x0080-0x0090) you've paste SHA-1 w/ AES256 using Diffe-Hellman exchange, and SHA-1 w/ RC4 using Diffe-Hellman. The two most common (and one is arguably secure) suites used (RC4 makes up a good 40% of all TLS traffic). Your only real option I think is to black list SHA-1 crypto which may cause issues. <pure speculation> Smart phones may disable SHA-256+ methods because of extra computing power needed. </pure speculation>