← DigiCert cases
Bugzilla #2069766 Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure

DigiCert CPR about subject.countryName and ISO 3166-1 alpha-2 codes

RESOLVED INVALID 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 concerns a third-party Certificate Problem Report sent to DigiCert about the use of certain countryName values in certificates. The reporter argued that some CA-issued country codes did not meet the Baseline Requirements definition of “Country” and asked for revocation and a Bugzilla case. DigiCert responded that the issue was a standards-interpretation question, not a compliance incident, and said no certificates had been misissued. GoDaddy and Hongkong Post said they reviewed the same report and agreed with DigiCert’s interpretation. CCADB incident-reporting later said closure as INVALID appeared appropriate on the limited basis that use of an appropriately assigned ISO 3166-1 alpha-2 code in subject countryName does not by itself constitute misissuance. The bug was resolved INVALID.

Model: gpt-5.4-mini Generated: 2026-10-20 17:37 UTC Confidence: 0.97 6 comments
Chronology
  1. DigiCert received a third-party Certificate Problem Report about subject.countryName values and ISO 3166-1 alpha-2 country codes.
  2. CCADB incident-reporting said closure as INVALID appeared appropriate on the limited basis described in its comment.
  3. The bug was slated to be closed as INVALID if there were no contrary comments.
Thread Activity
  1. DigiCert — DigiCert opened the bug with a preliminary incident report, said it did not consider the issue a compliance incident, and requested closure as INVALID.
  2. DigiCert — DigiCert added a link to the ISO 3166 country codes page.
  3. GoDaddy — GoDaddy said it received the same CPR and agreed with DigiCert’s interpretation and conclusion.
  4. Certizen representative — Hongkong Post said it also received the same CPR and agreed that use of C=HK did not constitute misissuance.
  5. DigiCert — DigiCert reiterated that the issue was best addressed through CA/Browser Forum discussion and again requested INVALID.
  6. CCADB representative — CCADB said closure as INVALID appeared appropriate on the limited basis stated and noted that the forum might need to clarify the requirements.
Participants
DigiCert GoDaddy Certizen representative CCADB representative
Similar Local Cases
#2056663 RESOLVED Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure Certificate Misissuance Opened 2026-07-21 · Closed 2026-08-10 · 99% similar
DigiCert: EVG CA profile compliance
#2032485 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2026-04-16 · Closed 2026-05-04 · 88% similar
DigiCert: Misissuance detected by PKIMetal
#2007219 RESOLVED Ca Certificate Compliance Opened 2025-12-20 · Closed 2026-02-17 · 85% similar
DigiCert: Some certificates issued with CRLDPs that don’t exactly match CCADB disclosures
#2015186 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2026-02-06 · Closed 2026-03-23 · 85% similar
DigiCert: Subject Serial Numbers for Non-Commercial Entities
#2070071 RESOLVED Ca Certificate Compliance Externally Reported Incident Incident Self Reported Incident Opened 2026-09-08 · Closed 2026-10-02 · 82% similar
Sectigo: Issuance of certificates including a Subject:countryName not corresponding to a Country
#2069774 RESOLVED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Historical Reference Opened 2026-09-07 · Closed 2026-09-23 · 81% similar
TWCA: CPR subject.countryName
#2076193 ASSIGNED Ca Certificate Compliance Externally Reported Incident Ccadb Disclosure Issue Problem Reporting Failure Opened 2026-09-28 Still Open · 80% similar
D-Trust: Incorrect CPS URLs in CCADB for six S/MIME CA certificate records
#2057318 RESOLVED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Revocation Issue Opened 2026-07-23 · Closed 2026-09-14 · 79% similar
GlobalSign: Unicode replacement character issue in Subject

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

⚠

Confirm action