4 ms·
Although the color-coding is odd; red doesn't mean insecure or even "dubious", even though it does sometimes... So using the site even for testing TLS clients s
by emn13 10y ago
Although the color-coding is odd; red doesn't mean insecure or even "dubious", even though it does sometimes... So using the site even for testing TLS clients seems a little non-obvious.
At least if the idea was that your client should accept green and reject red connections, the site has definitely failed.
If the idea was just to let you see what happens, then why the color coding?
- baby 10y agoCan you tell me which `red` is not insecure? (or not obsolete)
- emn13 10y agohttps://mozilla-old.badssl.com/ https://mozilla-old.badssl.com/ negotiates to TLS1.2 ECDHE RSA AES128 GCM SHA256 for me (FF54) which is fine. There may well be obsolete stuff that server does support; but as negotiated, that's pretty much as good as it gets. It even has the new downgrade-prevention extensions on, so support for the old stuff shouldn't be a problem even if your client accepts it (which it need not).
- baby 10y agoYeah I see, this one is more of a server-side problem since it still allow SSLv3 connections.