← DigiCert cases
Bugzilla #1397963 Ca Certificate Compliance Self Reported Incident

DigiCert / Wells Fargo: Invalid DNS 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

This case involves DigiCert's disclosure of compliance issues related to invalid DNS names associated with certificates issued for Wells Fargo. The issues included a reserved domain name and a certificate with trailing whitespace. DigiCert became aware of these problems through a certificate problem report and subsequent discussions. They took corrective actions, including revoking the affected certificates within 24 hours and addressing OCSP response issues. The CA confirmed that they have ceased issuing certificates with these problems and have implemented measures to prevent recurrence. The case has been resolved with the issuing CA now revoked.

Model: gpt-4o-mini Generated: 2026-06-13 11:04 UTC Revised: 2026-06-16 18:44 UTC Confidence: 0.85 11 comments
Chronology
  1. Invalid DNS name submitted as a certificate problem report.
  2. Certificate was revoked within 24 hours of the report.
  3. Decision made to discontinue operating the Wells Fargo Sub CA.
  4. The issuing CA has now been revoked.
Thread Activity
  1. Mozilla representative — This bug has been separated out from Bug #1389172 to request an incident report specific to this subCA.
  2. DigiCert — The invalid DNS name issue was submitted as a cert problem report on Aug 14th, 2017.
  3. Community commenter — Important to understand why the OCSP responders were serving improper responses.
  4. DigiCert — A call was held on Sep 5 to discuss discontinuing the Wells Fargo Sub CA.
  5. DigiCert — The issuing CA has now been revoked. Can we close the bug?
Participants
Mozilla representative DigiCert Community commenter
Similar Local Cases
#1624527 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2020-03-24 · Closed 2023-02-22 · 100% similar
DigiCert: Issuance of Cert with Compromised Key
#1714439 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-03 · Closed 2023-02-22 · 100% similar
DigiCert: Incorrect RegNumber-Org Type combination
#1304895 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2016-09-22 · Closed 2023-02-22 · 100% similar
DigiCert: TI Trust Technologies Global CA issued certificate with no subject alternative name extension
#1335132 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-01-30 · Closed 2023-02-22 · 100% similar
DigiCert: Verizon mis-issued test certificates
#1389172 RESOLVED Ca Certificate Compliance Revocation Issue Opened 2017-08-10 · Closed 2023-02-22 · 100% similar
DigiCert: Certificate Issues Identified on the Mailing List
#1397960 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-09-07 · Closed 2023-02-22 · 100% similar
DigiCert / Telecom Italia: Several Problems
#1397969 RESOLVED Self Reported Incident Opened 2017-09-08 · Closed 2023-02-22 · 100% similar
DigiCert / Inteso San Paulo: Double dot characters
#1618256 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2020-02-26 · Closed 2023-02-22 · 99% similar
DigiCert: Failure to properly encode Subject name

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

Confirm action