The difficulty of making sure your website is broken

bullen wrote: post #3

Meanwhile HTTP keeps working just fine and is decentralized. Just "add your own crypto" on top, which is the ONLY thing a sane person would do. 3... 2... 1... banned?

Did you self-ban?

Re: The difficulty of making sure your website is broken

#5

Post by ipython » Fri, Apr 10, 2026, 5:57 PM UTC

Interesting. Chrome (146, macOS) shows no error messages on the revoked cert pages, but Firefox does (also macOS).

Re: The difficulty of making sure your website is broken

#6

Post by bullen » Fri, Apr 10, 2026, 6:02 PM UTC

xandrius wrote: post #4

bullen wrote: post #3

Meanwhile HTTP keeps working just fine and is decentralized. Just "add your own crypto" on top, which is the ONLY thing a sane person would do. 3... 2... 1... banned?

Did you self-ban?

XD Nope, more like self destruct! ;)

Re: The difficulty of making sure your website is broken

#7

Post by mcpherrinm » Fri, Apr 10, 2026, 6:02 PM UTC

ipython wrote: post #5

Interesting. Chrome (146, macOS) shows no error messages on the revoked cert pages, but Firefox does (also macOS).

Yeah, Chrome only partly supports revocation (Not sure exactly the criteria, but our test sites don't match it).

Re: The difficulty of making sure your website is broken

#8

Post by lifis » Fri, Apr 10, 2026, 6:15 PM UTC

Vanadium, Chrome and Firefox (all for Android) all accept all the revoked certificates... But revoked.badssl.com is considered revoked

Re: The difficulty of making sure your website is broken

#9

Post by moralestapia » Fri, Apr 10, 2026, 6:39 PM UTC

ipython wrote: post #5

Interesting. Chrome (146, macOS) shows no error messages on the revoked cert pages, but Firefox does (also macOS).

Same with Brave, so it is a Chromium thing.

Re: The difficulty of making sure your website is broken

#10

Post by RunningDroid » Fri, Apr 10, 2026, 6:47 PM UTC

lifis wrote: post #8

Vanadium, Chrome and Firefox (all for Android) all accept all the revoked certificates... But revoked.badssl.com is considered revoked

> Vanadium, Chrome and Firefox (all for Android) all accept all the revoked certificates... But revoked.badssl.com is considered revoked

Firefox Beta (150.0b7) is accepting all of the revoked certs on my device