← GoDaddy cases
Bugzilla #1439123
CA Inclusion Request
GoDaddy: Failure to respond to January 2018 CA Communication survey
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
The case concerns GoDaddy’s failure to respond to the January 2018 CA Communication survey by the stated deadline. The survey response deadline was February 9, and GoDaddy had not responded as of February 16. GoDaddy reported that it was unable to submit the response because it was using the wrong link and believed the survey was still in read-only mode; it also said it would seek ways to add a distribution group to its CCADB contact list. GoDaddy further stated that unfamiliarity with Mozilla request timelines led to the missed response and that it now understood the cadence and timelines. After no further questions were raised, the reporter resolved the bug. The bug is marked RESOLVED with resolution FIXED.
Chronology
- The January 2018 CA Communication survey response deadline passed without a GoDaddy response.
- GoDaddy had still not responded to the January 2018 CA Communication survey as of this date.
- GoDaddy submitted its explanation for the missed survey response and described changes to prevent recurrence.
- The reporter resolved the bug after no further questions.
Thread Activity
- Fastly representative — Reported that the January 2018 CA Communication survey deadline was Feb 9 and asked GoDaddy to respond with specific information, including why no response was received and how future deadlines would be met.
- GoDaddy — Said he could not edit/submit the report because the page appeared read-only and asked whether his account was set up correctly.
- Mozilla representative — Explained the survey due-date had been extended to Feb 17 and that the expiration date needed re-extension for submission.
- GoDaddy — Provided answers: the missed response was due to using the wrong link and misunderstanding read-only status; contact info looked correct; and it said monitoring of mozilla.dev.security.policy did not result in response due to unfamiliarity with timelines, with improved understanding going forward.
- Community commenter — Re-opened the bug, stating it is not up to the CA to decide when compliance bugs get closed.
- Fastly representative — Resolved the bug after seeing no further questions.
Participants
Fastly representative
GoDaddy
Mozilla representative
Community commenter
External References
Similar Local Cases
Disclosure of new GoDaddy Code Signing Subordinate CAs
Add Visa Information Delivery Root CA certificate
Request Valicert/Starfield/GoDaddy Root Certificates be enabled for EV
GoDaddy cross-signing two Certainly Intermediate Certificates
GoDaddy: Non-BR-Compliant Certificate Issuance
GoDaddy: Random Value Vulnerability in Domain Validation Method
GoDaddy: failure to revoke underscores
Add SwissSign SHA2 root certificate(s)