4 ms·

> Certificate error pages have been redesigned for a better user experience. If you'd like to test: https://badssl.com/ https://badssl.com/

by judge2020 5y ago

javajosh 5y ago
Oooh. That's a really nice tool. Thanks! EDIT: I also like http://neverssl.com http://neverssl.com which has no TLS defined which is handy to trigger finicky network login screens.
- acdha 5y ago
  I especially like the dashboard feature: https://badssl.com/dashboard/ https://badssl.com/dashboard/ That's your first point of troubleshooting anytime you're on a new network and aren't certain whether a problem you're seeing is due to some kind of tampering proxy or configuration policy.
- daveslash 5y ago
  Ooh! Yes! Nice tool indeed! New to me. My only critique - I kind of wish it was badtls, not badssl.
- shantara 5y ago
  I usually use old good http://example.com http://example.com for such cases
milliams 5y ago
I wish Firefox would improve their release notes pages. This is exactly the sort of thing I'd like to see a screen shot of.
kgwxd 5y ago
Awww, I actually enjoyed feeling like I just fired up a new game of Adventure when visiting an unsecured site. Accepting the risk and continuing was my modern day key to the yellow castle.
capybara_2020 5y ago
It might be a personal opinion, but I do not like this at all. A cert error now looks way too similar to other connection errors. Other errors you cannot bypass, but cert errors you can. This change means I am going to go cert error blind and assume the site is just inaccessible. The older loud yellow alert made things easy to differentiate. https://imgur.com/a/jF37m8G https://imgur.com/a/jF37m8G
- aeturnum 5y ago
  I think that, for most users in most situations, the best thing is to approach a certificate error as a connection failure.
- zaarn 5y ago
  In 99% of connections, a certificate error should be connection failure. In the 1% where it's the sysadmin forgetting to renew or a dev using a self-signed cert, you can still bypass.

> Certificate error pages have been redesigned for a better user experience. If you'd like to test: https://badssl.com/ https://badssl.com/

javajosh 5y ago

Oooh. That's a really nice tool. Thanks! EDIT: I also like http://neverssl.com http://neverssl.com which has no TLS defined which is handy to trigger finicky network login screens.

acdha 5y ago
I especially like the dashboard feature: https://badssl.com/dashboard/ https://badssl.com/dashboard/ That's your first point of troubleshooting anytime you're on a new network and aren't certain whether a problem you're seeing is due to some kind of tampering proxy or configuration policy.
daveslash 5y ago
Ooh! Yes! Nice tool indeed! New to me. My only critique - I kind of wish it was badtls, not badssl.
shantara 5y ago
I usually use old good http://example.com http://example.com for such cases

milliams 5y ago

I wish Firefox would improve their release notes pages. This is exactly the sort of thing I'd like to see a screen shot of.

kgwxd 5y ago

Awww, I actually enjoyed feeling like I just fired up a new game of Adventure when visiting an unsecured site. Accepting the risk and continuing was my modern day key to the yellow castle.

capybara_2020 5y ago

It might be a personal opinion, but I do not like this at all. A cert error now looks way too similar to other connection errors. Other errors you cannot bypass, but cert errors you can. This change means I am going to go cert error blind and assume the site is just inaccessible. The older loud yellow alert made things easy to differentiate. https://imgur.com/a/jF37m8G https://imgur.com/a/jF37m8G

aeturnum 5y ago
I think that, for most users in most situations, the best thing is to approach a certificate error as a connection failure.
zaarn 5y ago
In 99% of connections, a certificate error should be connection failure. In the 1% where it's the sysadmin forgetting to renew or a dev using a self-signed cert, you can still bypass.