GoDaddy self-reported delayed revocation of impacted subscriber certificates
GoDaddy opened this case as a self-reported incident about delayed revocation of impacted subscriber certificates. The initial report says the issue was related to discrepancies between issued certificates and the subscriber certificate profiles documented in its Starfield CP/CPS, and it references Bug 2082703 as the related incident context. GoDaddy said it suspended issuance, corrected the CP/CPS errors, resumed issuance, and activated its Mass Revocation Plan for 404,607 impacted subscriber certificates. In the update on October 19, GoDaddy said it had revoked 227,422 certificates total, but had not completed revocation by the October 18, 23:45 UTC deadline. The thread remains open with GoDaddy continuing subscriber outreach and revocation work, and the next update was promised for October 22, 2026.
- GoDaddy began engaging subscribers to reissue and revoke impacted subscriber certificates.
- The revocation deadline for the impacted subscriber certificates passed without completion.
- GoDaddy reported that 227,422 of 404,607 impacted certificates had been revoked.
- GoDaddy — GoDaddy filed a preliminary incident report describing delayed revocation, saying it self-reported the issue, suspended issuance, corrected CP/CPS errors, and activated its Mass Revocation Plan.
- GoDaddy — GoDaddy said it still had not completed revocation by the deadline, reported 227,422 revoked certificates, and said the next update would come on October 22, 2026.