

update: it is now working for me in tor browser again (it had stopped when i posted my previous comment; i’ve since relaunched it), but is revoked in another browser.
and yes they are seeing the same certificate (serial number 02:29:5E:6B:B2:57:17:C4:65:23:21:F4:ED:9D:2B:29, same as OP, with sha256 fingerprint D6:63:CA:4B:6A:48:54:D2:24:2B:E8:63:D7:37:CC:68:1B:B9:61:1A:86:81:55:F2:86:87:A9:DA:67:8A:4C:9A)
in that thread i posted (post-revocation) linking to a story on www.presstv.ir there are lots of comments and nobody there has mentioned it being revoked.
conclusions: (1) their CA definitely revoked their cert, (2) the revocation is not being evenly distributed.







































Their certificate was revoked (by their certificate authority, Actalis, part of the Aruba Group) on July 6. Presumably the CA was pressured to revoke it by the Italian and/or US government, and they will get a new certificate from someone else soon.
There is a hexbear thread here about it; afaict there doesn’t appear to yet be any reporting about it. But in the CRL you can see it was revoked July 6:
$ curl -s http://crl15.actalis.it/Repository/tls-subca-rsa-dv-2025/getLastCRL | openssl crl -noout -text |grep -A 4 02295E6BB25717C4652321F4ED9D2B29 Serial Number: 02295E6BB25717C4652321F4ED9D2B29 Revocation Date: Jul 6 13:54:09 2026 GMT CRL entry extensions: X509v3 CRL Reason Code: Privilege WithdrawnThe reason “Privilege Withdrawn” means it was the CA’s decision rather than their own.
Because certificate revocation has never worked very well, many people can still access it (until their browser fetches the certificate revocation list, or checks OCSP, does some newfangled proprietary other thing i don’t understand…).