Unverified50% confidenceFactExact time
When a CA exits the business, if the CRL/OCSP services go offline early, clients will be unable to confirm certificate status, and some strict-mode browsers or systems may report errors directly.
1
Sources
50%
Confidence
Long-term
Relevance
10/22/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSite operators should confirm whether their own certificate chain includes the affected intermediate CA, and monitor trust store update announcements from the CA/Browser Forum and mainstream browser vendors to replace affected certificates in a timely manner.67% similarUnverifiedCommon certificate revocation mechanisms include certificate revocation lists (CRLs) and the Online Certificate Status Protocol (OCSP); browsers usually have built-in revocation checks or rapidly update root certificate lists, but system-level trust stores are updated less frequently, and many command-line tools do not perform real-time revocation queries by default.66% similarUnverifiedCommercial CAs typically do not issue certificates to arbitrary individuals that can be used for interception of arbitrary domains; enterprises must apply in an organizational capacity and accept usage constraints, and the acquisition process requires additional account and approval steps.65% similarUnverifiedApplications that ignore the system certificate store will throw errors such as UNABLE_TO_VERIFY_LEAF_SIGNATURE or self signed certificate in managed network environments.65% similarUnverifiedSince Android 7.0, the system no longer trusts CA certificates installed by users by default.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1086343API
curl https://kongchang.com/api/v1/knowledge/claims/1086343MCP
get_claim(id=1086343)