← DigiCert cases
Bugzilla #1978163 Self Reported Incident

DigiCert self-reported WHOIS/DCV validation reuse after deprecation deadline affected 1,834 certificates

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 reported an internal compliance issue involving Domain Control Validation method 3.2.2.4.2, where WHOIS-based validation was still being reused after the CA/B Forum deprecation date of 2025-07-15. DigiCert said its internal review found that validations tied to an Authorization Domain Name reached through a CNAME alias were not blocked as intended, which allowed additional certificates to be issued after the deadline. The company stated that it corrected the issue, blocked the affected validations, and revoked all 1,834 affected certificates. The report also says issuance was not stopped because the fix was deployed quickly and the validation state was cleared to force re-validation. The thread then focused heavily on whether the BR text allowed CNAME-based Authorization Domain Name handling in this method, but DigiCert maintained that the bug itself was about the post-deprecation issuance and that the remaining action item was replacing the workflows with its open-source DCV library by 2025-09-30.

Model: gpt-5.4-mini Generated: 2026-06-13 11:47 UTC Revised: 2026-06-16 17:28 UTC Confidence: 0.95 76 comments
Chronology
  1. WHOIS-based DCV method 3.2.2.4.2 reached its deprecation date.
  2. DigiCert identified that certificates could still be issued using reused WHOIS-based validation for alias domains after the deprecation date.
  3. DigiCert revoked all 1,834 affected certificates and filed the bug report.
  4. DigiCert stated it was on track to replace the workflows with its open-source DCV library by this date.
Thread Activity
  1. DigiCert — DigiCert filed a preliminary incident report describing the WHOIS/DCV reuse issue, the affected 1,834 certificates, and that all had been revoked.
  2. DigiCert — DigiCert filed the full incident report and said it cleared validation state to prevent further reliance on the old WHOIS validations.
  3. DigiCert — DigiCert said it did not believe the certificates were misissued and said the complaint was based on a re-interpretation of the TLS BRs.
  4. Mozilla representative — Mozilla said the incident raised questions about ADN and CNAME-following and noted that section 3.2.2.4.2 did not appear to allow substitution via CNAME.
  5. DigiCert — DigiCert said the bug was about the 1,834 certificates issued after the deprecation date and asked that unrelated BR interpretation discussion move to the CA/B Forum.
  6. DigiCert — DigiCert said it was on track to replace the workflows with its open-source DCV library by 2025-09-30.
Participants
DigiCert Community commenter Sectigo Google representative Internet Security Research Group Mozilla representative Apple representative HARICA Opera representative Verbuecheln representative SwissSign AG
Related Bugzilla IDs Mentioned
Similar Local Cases
#1894560 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-05-01 · Closed 2024-07-03 · 100% similar
DigiCert: Incorrect case in Business Category
#1950144 RESOLVED Incident Self Reported Incident Opened 2025-02-24 · Closed 2026-06-11 · 100% similar
DigiCert: Threat of legal action to stifle Bugzilla discourse
#1974539 RESOLVED Self Reported Incident Revocation Issue Opened 2025-06-27 · Closed 2025-10-09 · 97% similar
DigiCert: DCV logging issue
#2017185 RESOLVED Self Reported Incident Opened 2026-02-16 · Closed 2026-04-15 · 96% similar
DigiCert: CAA processing during network disruption
#2009491 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2026-01-09 · Closed 2026-02-17 · 95% similar
DigiCert: Several non-functioning AIA URLs
#1654967 RESOLVED Self Reported Incident Revocation Issue Opened 2020-07-24 · Closed 2023-02-22 · 94% similar
DigiCert: Malformed ICA
#1710444 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-05-10 · Closed 2023-02-22 · 89% similar
DigiCert: Invalid stateOrProvinceName
#1714439 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-03 · Closed 2023-02-22 · 89% similar
DigiCert: Incorrect RegNumber-Org Type combination

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

Confirm action