Some proxies, iptables extensions, and OS-provided tools exist - there's almost certainly a combo that would work for them. What platform?

Unless it's for a custom physical device, then uh. idk. Probably something, proxying through another computer that is hosting a separate wifi network? But likely a lot harder.

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

Same with Brave, so it is a Chromium thing.

> 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

to actually tackle this (on the off chance you're serious, I'm assuming not) - this doesn't work.

The payload that implements your crypto cannot be delivered over http, because any intermediate party can just modify your implementation and trivially compromise it.

If you don't trust TLS, you have to pre-share something. In the case of TLS and modern browser security, the "pre-shared" part is the crypto implementation running in the browser, and the default trusted store of root CAs (which lives in the browser or OS, depending).

If you want to avoid trusting that, you've got to distribute your algorithm through an alternative channel you do trust.

Did you self-ban?