Just noticed that this is an unofficial google product, part of chromium github repository.
Bad SSL
91–93 of 93 posts
Re: Bad SSL
#92Earlier quoted context omitted.
Given what you say - what's the point of this website? After all, a safe client should connect to green things (but might not support everything, fine), and... should also connect to many red things (if they're actually safe). What's the point?
It helps you figure out what a client actually does, for differentiating browsers, or eg making sure that CLI tool verifies certs.
But then: why the color coding?
Re: Bad SSL
#93Earlier quoted context omitted.
Can you tell me which `red` is not insecure? (or not obsolete)
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).
Yeah I see, this one is more of a server-side problem since it still allow SSLv3 connections.