← DigiCert cases
Bugzilla #1914911 Ca Certificate Compliance

DigiCert: Unclear Disclosure of CAA Issuer Domain Names

RESOLVED FIXED DigiCert
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

DigiCert opened this case following a report regarding unclear language in their Certificate Policy/Certification Practice Statement (CP/CPS) related to CAA Issuer Domain Names. An investigation revealed that the language suggested the use of domains of the form 'digicert.XX', which was not implemented in their systems. Additionally, it was found that 'symantec.com' had been inadvertently omitted from the list of approved CAA domains, leading to the issuance of 185 misissued certificates. DigiCert revoked these certificates within the required timeframe and updated their CPS to correct the omissions. They have also implemented additional technical reviews and automated checks to prevent similar issues in the future.

Model: gpt-4o-mini Generated: 2026-06-13 11:45 UTC Revised: 2026-06-16 19:17 UTC Confidence: 0.85 28 comments
Chronology
  1. DigiCert receives a report about unclear CAA Issuer Domain Names in their CPS.
  2. All misissued certificates relying on the omitted CAA domain are revoked.
  3. DigiCert posts a closing summary detailing the incident and remediation steps.
Thread Activity
  1. Mm representative — Reported unclear language in DigiCert's CPS regarding CAA Issuer Domain Names.
  2. DigiCert — Confirmed that 185 certificates were misissued due to the omission of 'symantec.com' from the CPS.
  3. DigiCert — Posted a closing summary detailing the incident and remediation actions.
Participants
Mm representative DigiCert
External References
Similar Local Cases
#1927506 RESOLVED Ca Certificate Compliance Opened 2024-10-28 · Closed 2025-01-24 · 88% similar
DigiCert: Incorrect OrgID in S/MIME certificates for one customer
#1937210 RESOLVED Ca Certificate Compliance Opened 2024-12-13 · Closed 2025-02-28 · 87% similar
DigiCert: Late incident report for bug 1925106
#1397963 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-09-07 · Closed 2023-02-22 · 82% similar
DigiCert / Wells Fargo: Invalid DNS names
#1335132 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-01-30 · Closed 2023-02-22 · 81% similar
DigiCert: Verizon mis-issued test certificates
#1618256 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2020-02-26 · Closed 2023-02-22 · 80% similar
DigiCert: Failure to properly encode Subject name
#1624527 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2020-03-24 · Closed 2023-02-22 · 80% similar
DigiCert: Issuance of Cert with Compromised Key
#1397961 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-09-07 · Closed 2023-02-22 · 80% similar
DigiCert / Justica: Invalid DNS names
#1794050 RESOLVED Ca Certificate Compliance Certificate Misissuance Revocation Issue Opened 2022-10-06 · Closed 2023-02-22 · 79% similar
DigiCert: Org information issue in new validation workflow

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action