Root certificate · Sectigo

COMODO Certification Authority

COMODO Certification Authority is a root CA certificate operated by Sectigo (RSA 2048, valid until 2030-12-31, SHA-256 1A0D2044). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists EV policy OID 2.23.140.1.3, 1.3.6.1.4.1.6449.1.2.1.5.1 for this root, but Mozilla does not mark it as EV-enabled.

Removed Chrome

Status
Removed

Not included Mozilla

Status
Not included

Not included Apple

Status
Not included

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, Secure Email, Time Stamping

"Trusted for TLS" means the store includes the root with the server-authentication trust bit (Mozilla "Websites", Apple serverAuth, Microsoft Server Authentication EKU). Microsoft "NotBefore" means only certificates issued before a cutoff date are still trusted. "Constrained" means the store applies extra restrictions.

Details

CA owner
Sectigo
Subject
CN=COMODO Certification Authority,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
SHA-256
1A0D20445DE5BA1862D19EF880858CBCE50102B36E8F0A040C3C69E74522FE6E
SHA-1 (Windows thumbprint)
EE869387FFFD8349AB5AD14322588789A457B012
SPKI SHA-256
006D7BE7555DD82026442C4F1A27A80E89A1989CB87B34448ED2194C18196D5E
Valid from
2011-01-01
Expires
2030-12-31
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
20A4C47FDDDFE1C75363071388776012
Country
GB
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
EV policy OIDs (CCADB)
2.23.140.1.3, 1.3.6.1.4.1.6449.1.2.1.5.1 · TLS EV capable: Yes
Test websites
valid: https://comodocertificationauthority-ev.comodoca.com/ · expired: https://comodocertificationauthority-ev.comodoca.com:442/ · revoked: https://comodocertificationauthority-ev.comodoca.com:444/
CCADB record
A003637
PEM
sectigo-comodo-ca-1a0d2044.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists no intermediate CA certificate signed directly by COMODO Certification Authority.

Cross-signed versions

5 certificate(s) in the CCADB have the same subject and public key as COMODO Certification Authority but a different issuer. A server can send one of them so that clients which trust the issuing root, but not COMODO Certification Authority, can still build a chain.

Signed byCA ownerExpiresStatus
AddTrust External CA Root crt.sh Sectigo2020-05-30Expired
UTN-USERFirst-Hardware crt.sh Sectigo2020-05-30Expired
UTN-USERFirst-Hardware crt.sh Sectigo2020-05-30Expired
UTN - DATACorp SGC crt.sh Sectigo2020-05-30Revoked
AddTrust External CA Root crt.sh Sectigo2020-05-30Expired

CRL and OCSP addresses

In the root certificate

COMODO Certification Authority itself contains no CRL Distribution Points and no OCSP (Authority Information Access) extension. That is normal for a root: clients trust it directly and do not check its own revocation status.

Full CRL this CA publishes (CCADB)

  • http://crl.comodoca.com/COMODOCertificationAuthority.crl

What happens when it expires

COMODO Certification Authority is valid until 2030-12-31, about 4.1 years after this data snapshot (2026-11-10). From that day, browsers and operating systems that check trust-anchor expiry stop accepting chains that end at this root, so any certificate that can only chain to it fails validation. Android is a known exception: it does not enforce the expiry date of trust anchors.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up COMODO Certification Authority by common name (COMODO Certification Authority) or fingerprint. The store status in each heading comes from the CCADB snapshot; your device can differ if it is out of date or managed by an administrator.

macOS (Apple store: Not included)

Search the system roots keychain by common name. -Z prints the SHA-256 hash, which must match the fingerprint on the last line.

security find-certificate -a -c "COMODO Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 1A0D20445DE5BA1862D19EF880858CBCE50102B36E8F0A040C3C69E74522FE6E

Windows (Microsoft store: Included · Trusted for TLS)

Windows identifies roots by SHA-1 thumbprint. It installs third-party roots on demand through Automatic Root Certificates Update, so "not found" can also mean the root has not been needed yet; certutil -generateSSTFromWU roots.sst downloads Microsoft's full list.

certutil -verifystore Root EE869387FFFD8349AB5AD14322588789A457B012

Linux (ca-certificates follows Mozilla: Not included)

Debian, Ubuntu, Fedora and RHEL build their ca-certificates package from Mozilla's root store. Use trust list on p11-kit systems, or search the PEM bundle on Debian and Ubuntu.

# Fedora / RHEL / Arch (p11-kit)
trust list --filter=ca-anchors | grep -iF -A2 "COMODO Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "COMODO Certification Authority"

Java

Java ships its own cacerts keystore; JDK 9 and later accept -cacerts and the default store password is changeit. Search for the SHA-256 fingerprint in colon form.

keytool -list -cacerts -storepass changeit | grep -i "1A:0D:20:44:5D:E5:BA:18:62:D1:9E:F8:80:85:8C:BC:E5:01:02:B3:6E:8F:0A:04:0C:3C:69:E7:45:22:FE:6E"

Android

Android's system store is maintained by Google separately from the four CCADB stores above. Open Settings → Security & privacy → More security settings → Encryption & credentials → Trusted credentials → System (menu names vary by vendor and version) and look for COMODO CA Limited → COMODO Certification Authority.

Which root does my site chain to?

List the chain your server sends and compare the last issuer with this root; the fingerprint check confirms a local copy.

Download PEM

# show subject (s:) and issuer (i:) of every certificate the server sends
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
  | grep -E '^ *[0-9]+ s:|^ *i:'
# subject and SHA-256 fingerprint of the downloaded PEM file
openssl x509 -in sectigo-comodo-ca-1a0d2044.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=1A:0D:20:44:5D:E5:BA:18:62:D1:9E:F8:80:85:8C:BC:E5:01:02:B3:6E:8F:0A:04:0C:3C:69:E7:45:22:FE:6E

FAQ

Is COMODO Certification Authority trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does COMODO Certification Authority expire?

On 2030-12-31, about 4.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has COMODO Certification Authority issued?

The CCADB lists no intermediate certificate signed directly by COMODO Certification Authority.

Is COMODO Certification Authority cross-signed?

Yes. The CCADB has 5 cross-certificate(s) with its subject and key, signed by AddTrust External CA Root, UTN-USERFirst-Hardware, UTN - DATACorp SGC; 0 of them are still valid.

Other roots from Sectigo

Sources

  1. CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — Mozilla Included CA Certificate Report
  4. CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV