Root certificate · Sectigo

COMODO Certification Authority

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

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaIncluded IncludedNo—No
AppleIncluded IncludedYes—No
MicrosoftRemoved RemovedNo—No

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

Not included Chrome

Status
Not included

Included Mozilla

Status
Included
Trust bits
Email
EV policy OIDs
not EV-enabled
First included in
NSS 3.11.10 / Firefox 3.0.2
Inclusion bug
#401587

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Removed Microsoft

Status
Removed
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
0C2CD63DF7806FA399EDE809116B575BF87989F06518F9808C860503178BAF66
SHA-1 (Windows thumbprint)
6631BF9EF74F9EB6C9D5A60CBA6ABED1F7BDEF7B
SPKI SHA-256
006D7BE7555DD82026442C4F1A27A80E89A1989CB87B34448ED2194C18196D5E
Valid from
2006-12-01
Expires
2029-12-31
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
4E812D8A8265E00B02EE3E350246E53D
Country
GB
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
EV policy OIDs (CCADB)
2.23.140.1.1, 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
A000108
PEM
sectigo-comodo-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 27 intermediate CA certificates signed directly by COMODO Certification Authority: 4 currently valid, 23 expired and 0 revoked (revoked includes those whose parent was revoked). 4 of the valid ones run past the expiry date of the root itself (2029-12-31).

Showing 20 of 27: valid certificates first, newest first. Each name links to its crt.sh entry by SHA-256; an arrow marks a cross-certificate for another root on this site.

IntermediateOperated byExpiresStatus
Sectigo SHA-256 DV Secure Server CA 2 Sectigo2030-12-31Valid
Sectigo SHA-256 OV Secure Server CA 2 Sectigo2030-12-31Valid
Sectigo SHA-256 EV Secure Server CA 2 Sectigo2030-12-31Valid
COMODO SHA-256 Client Authentication and Secure Email CA 2 Sectigo2032-06-12Valid
TrustAsia EV SSL Server CA Sectigo2020-05-30Expired
SecureCore SHA-1 EV CA Sectigo2020-05-30Expired
EUNETIC - EuropeanSSL Extended Validation Server CA Sectigo2020-05-30Expired
CertAssure EV Secure Server Certification Authority Sectigo2020-05-30Expired
SSL.com Premium EV CA Sectigo2020-05-30Expired
PSW GROUP Extended Validation SSL CA Sectigo2020-05-30Expired
ReliaSite EV Server CA Sectigo2020-05-30Expired
SSL Blindado PRO EV Sectigo2020-05-30Expired
EUNETIC - EuropeanSSL Extended Validation Server CA Sectigo2020-05-30Expired
SSL Blindado EV Sectigo2020-05-30Expired
Formidable CA Services Extended Validation Sectigo2020-05-30Expired
SSL.com Premium EV CA Sectigo2020-05-30Expired
DOMENY.PL EV Certification Authority Sectigo2020-05-30Expired
TrustSign BR Certification Authority (EV) Sectigo2020-05-30Expired
GlobalTrust Extended Validation CA Sectigo2020-05-30Expired
GlobeSSL CA Sectigo2020-05-30Expired

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

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

Full CRL this CA publishes (CCADB)

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

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 4 valid intermediates signed by COMODO Certification Authority; the number in brackets is how many of them use each address.

  • CRL: http://crl.comodoca.com/COMODOCertificationAuthority.crl (4)
  • OCSP: http://ocsp.comodoca.com (4)

What happens when it expires

COMODO Certification Authority is valid until 2029-12-31, about 3.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. 4 of its valid intermediates expire later than the root, so their operators need another path, such as a cross-sign from a newer root, before 2029-12-31.

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: Included · Trusted for TLS)

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: 0C2CD63DF7806FA399EDE809116B575BF87989F06518F9808C860503178BAF66

Windows (Microsoft store: Removed)

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 6631BF9EF74F9EB6C9D5A60CBA6ABED1F7BDEF7B

Linux (ca-certificates follows Mozilla: 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 "0C:2C:D6:3D:F7:80:6F:A3:99:ED:E8:09:11:6B:57:5B:F8:79:89:F0:65:18:F9:80:8C:86:05:03:17:8B:AF:66"

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.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=0C:2C:D6:3D:F7:80:6F:A3:99:ED:E8:09:11:6B:57:5B:F8:79:89:F0:65:18:F9:80:8C:86:05:03:17:8B:AF:66

FAQ

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

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

When does COMODO Certification Authority expire?

On 2029-12-31, about 3.1 years after the 2026-11-10 data snapshot. 4 of the valid ones run past the expiry date of the root itself (2029-12-31).

How many intermediate certificates has COMODO Certification Authority issued?

The CCADB lists 27: 4 valid, 23 expired and 0 revoked. The newest valid one is Sectigo SHA-256 DV Secure Server CA 2, valid until 2030-12-31.

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