https://f000.backblazeb2.com/file/0011public/Photo-2025-09-1...
Might be EOL in some theoretical sense, but by turning it off they're ignoring reality. I know some organizations think this is the way to push standards forward. But to me it seems pretty irresponsible.
I would say "majority" rather than "not all" browsers perform revocation checking.
We're starting to see adoption for O(days) now but I imagine that the lifetime will continue to decrease to some minimum O(hours) in the years to come.
Compared to what? 12MB JavaScript bundles and autoplay videos? Do CDNs still exist?
There's a finite number of CAs and browsers can be expected to perform caching. Delta CRLs also exist and the CAs can decline to include expired leaf certs.
This sounds like a made up problem that was solved 25 years ago.
How so? Doesn't revocation have to be done by the same entity that issued the certificate?
However, this page, shows perfectly, so there must have been some differences between this and the domain I remember. Unfortunately, my domain has long since been reissued and I can't reproduce the block. The block also occurred in the latest Thunderbird for windows 7 interestingly.
This loads fine in Safari on iOS 26 lol.
I always thought Chrome didn't block them and that revocation was pretty much dead.
Dylan16807•1h ago