← GoDaddy cases
Bugzilla #1902868
Delayed Revocation
GoDaddy: CPR was not responded to in 24 hours
RESOLVED
FIXED
GoDaddy
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
GoDaddy failed to respond to a Certificate Problem Report (CPR) regarding mis-issued certificates within the required 24-hour timeframe. The issue arose after an email was sent to GoDaddy on June 14, 2024, highlighting concerns about the entropy in their serial number generation. GoDaddy acknowledged the oversight as a result of human error and confirmed that they did not meet the Baseline Requirements for timely CPR responses. Following internal reviews, GoDaddy has committed to additional training and process improvements to prevent future occurrences. The case has been resolved with a final response provided to the reporter on June 20, 2024.
Chronology
- GoDaddy received a Certificate Problem Report regarding serial number entropy.
- GoDaddy responded to the CPR with findings.
Thread Activity
- Community commenter — Reported lack of response from GoDaddy to the CPR within 24 hours.
- GoDaddy — Provided an incident report acknowledging the failure to respond in time.
- GoDaddy — Confirmed compliance with the Baseline Requirements after further investigation.
Participants
Community commenter
GoDaddy
Mozilla representative
External References
Similar Local Cases
GoDaddy: CPR responses greater than 24 hours
GoDaddy: Failure to Revoke Subscriber Certificates within 24 hours
GoDaddy: Failure to revoke 210 subscriber certificates within 24 hours
GoDaddy: Failure to revoke certificate with compromised key within 24 hours
GoDaddy: Failure to revoke key-compromised certificates within 24 hours
GoDaddy: Delayed CRL File Updates
GoDaddy: Delayed revocation
Entrust: CPR was not responded to in 24 hours