← SSL.com cases
Bugzilla #2057919
Ca Certificate Compliance
Problem Reporting Failure
Incident
Externally Reported Incident
Information Request
SSL.com failure to provide a preliminary response to a Certificate Problem Report within 24 hours
ASSIGNED
SSL.com
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update.
Always refer to the official Bugzilla thread as the authoritative source.
If you spot an inaccuracy, let me know via the contact form.
AI Summary
SSL.com reported that it received a follow-up email from a third-party reporter about a Certificate Problem Report that had been submitted two days earlier through its revoke form. The bug states that SSL.com had not heard back from the CA and is investigating the root cause. SSL.com cites TLS Baseline Requirements v2.2.8, Section 4.9.5, which requires a preliminary report within 24 hours after receiving a Certificate Problem Report. The incident was disclosed as a third-party-reported issue, not a self-disclosure by SSL.com. SSL.com said it would post a full incident report on or before 2026-08-07.
Chronology
- A Certificate Problem Report was submitted to SSL.com through its revoke form and did not receive a response within 24 hours.
- SSL.com received a follow-up email from a third-party reporter about the unanswered Certificate Problem Report.
- SSL.com stated it would post a full incident report by this date.
Thread Activity
- SSL.com — SSL.com filed a preliminary incident report saying it had received a third-party follow-up about an unanswered Certificate Problem Report and was investigating the root cause.
Participants
SSL.com
External References
Similar Local Cases
CFCA: Delayed response to CPR related with bug 2058918
SSL.com: Invalid Subject stateOrProvince Values
NETLOCK: Failure to Respond to a Certificate Problem Report Within 24 Hours
Google Trust Services: CPS Missing root program attestation
IdenTrust: Delayed disclosure of Intermediate CA in CCADB
DigiCert: Delayed response to problem report related to Bug 2055539
FNMT: Delay in incident disclosure reporting for Bug 2049012
Asseco DS / Certum: Delayed publication of Full Incident Report for Bug 2055775