← DigiCert cases
Bugzilla #2078824 Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Revocation Issue

DigiCert: Certificates issued for sanctioned entities

ASSIGNED 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 bug to disclose a sanctions-compliance incident involving three DV certificates issued to domains associated with entities on sanctions or denied-party lists. In its preliminary report, DigiCert said a third party submitted reports identifying the certificates, that two had already been revoked during internal sanctions reviews, and that the third was revoked after the follow-up report. DigiCert stated that issuance for the affected domains was halted by adding the domains to its blocklist. The report cites TLS Baseline Requirements section 9.15 and DigiCert Public Trust CP/CPS section 4.1.1. The bug remains assigned to DigiCert and the investigation was described as continuing in the preliminary report.

Model: gpt-5.4-mini Generated: 2026-10-20 17:38 UTC Confidence: 0.96 3 comments
Chronology
  1. Two DV certificates for ylfelectronics.com were issued.
  2. A DV certificate for api.iraytek.com was issued.
  3. A CPR was received for ylfelectronics.com, both certificates were revoked, and the domain was added to the blocklist.
  4. A follow-up CPR identified api.iraytek.com.
  5. The api.iraytek.com certificate was revoked.
Thread Activity
  1. DigiCert — DigiCert filed a preliminary incident report saying a third party reported three DV certificates issued to sanctioned-entity domains, two had already been revoked, and the third was revoked.
  2. DigiCert — DigiCert attached a sanctions-entities dossier CSV and then posted a full incident report with timeline, impact, and root-cause analysis.
Participants
DigiCert
Related Bugzilla IDs Mentioned
Similar Local Cases
#2083502 UNCONFIRMED Ca Certificate Compliance Incident Self Reported Incident Linting Quality Issue Opened 2026-10-18 Still Open · 89% similar
DigiCert: cRLNumber not increasing within one CRL scope
#1910322 RESOLVED Certificate Misissuance Revocation Issue Opened 2024-07-29 · Closed 2025-06-18 · 88% similar
DigiCert: Random value in CNAME without underscore prefix
#2009491 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2026-01-09 · Closed 2026-02-17 · 87% similar
DigiCert: Several non-functioning AIA URLs
#2033170 RESOLVED Ca Security Vulnerability Incident Self Reported Incident Revocation Issue Opened 2026-04-18 · Closed 2026-07-20 · 87% similar
DigiCert: Misissued code signing certificates
#1950144 RESOLVED Incident Self Reported Incident Opened 2025-02-24 · Closed 2026-06-11 · 86% 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 · 86% similar
DigiCert: DCV logging issue
#1894560 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-05-01 · Closed 2024-07-03 · 81% similar
DigiCert: Incorrect case in Business Category
#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

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

⚠

Confirm action