Root certificate · Sectigo

COMODO RSA Certification Authority

COMODO RSA Certification Authority is a root CA certificate operated by Sectigo (RSA 4096, valid until 2038-01-18, SHA-256 52F0E1C4). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2026-09-30Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-30 (sct_not_after). Mozilla treats it as an EV root for policy OID 1.3.6.1.4.1.6449.1.2.1.5.1.

Included Chrome

Status
Included
Distrust for TLS after
2026-09-30

Included Mozilla

Status
Included
Trust bits
Websites, Email
EV policy OIDs
1.3.6.1.4.1.6449.1.2.1.5.1
First included in
NSS 3.17.3 / Firefox 36
Inclusion bug
#606947

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

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 RSA Certification Authority,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
SHA-256
52F0E1C4E58EC629291B60317F074671B85D7EA80D5B07273463534B32B40234
SHA-1 (Windows thumbprint)
AFE5D244A8D1194230FF479FE2F897BBCD7A8CB4
SPKI SHA-256
82B5F84DAF47A59C7AB521E4982AEFA40A53406A3AEC26039EFA6B2E0E7244C1
Valid from
2010-01-19
Expires
2038-01-18
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
4CAAF9CADB636FE01FF74ED85B03869D
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)
1.3.6.1.4.1.6449.1.2.1.5.1, 2.23.140.1.1, 2.23.140.1.3 · TLS EV capable: Yes
Test websites
valid: https://comodorsacertificationauthority-ev.comodoca.com/ · expired: https://comodorsacertificationauthority-ev.comodoca.com:442/ · revoked: https://comodorsacertificationauthority-ev.comodoca.com:444/
CCADB record
A000285
PEM
sectigo-comodo-rsa-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 42 intermediate CA certificates signed directly by COMODO RSA Certification Authority: 23 currently valid, 15 expired and 4 revoked (revoked includes those whose parent was revoked).

Showing 20 of 42: 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 Public Server Authentication Root R46 → Sectigo Public Server Authentication Root R46 Sectigo2038-01-18Valid
WebNIC Code Signing CA Sectigo2029-09-22Valid
WebNIC Assured ID CA Sectigo2029-09-22Valid
WebNIC RSA Domain Secure Site CA Sectigo2029-09-22Valid
WebNIC RSA Business Secure Site CA Sectigo2029-09-22Valid
WebNIC RSA Extended Validation Secure Site CA Sectigo2029-09-22Valid
WoTrus DV Server CA Sectigo2029-02-26Valid
Trustico RSA OV CA Sectigo2027-09-08Valid
Trustico RSA Client CA Sectigo2027-09-08Valid
Trustico RSA Codesigning CA Sectigo2027-09-08Valid
Trustico RSA EV CA Sectigo2027-09-08Valid
Trustico RSA DV CA Sectigo2027-09-08Valid
cPanel Extended Validation RSA Certification Authority Sectigo2026-12-13Valid
cPanel High Assurance RSA Certification Authority Sectigo2026-12-13Valid
UbiquiTLS™ DV RSA Server CA Sectigo2031-03-29Valid
COMODO RSA Extended Validation Code Signing CA Sectigo2029-12-02Valid
COMODO/HP Secure Email CA 2 Sectigo2029-11-25Valid
COMODO RSA Organization Validation Secure Server CA Sectigo2029-02-11Valid
COMODO RSA Domain Validation Secure Server CA Sectigo2029-02-11Valid
COMODO RSA Code Signing CA Sectigo2028-05-08Valid

Cross-signed versions

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

Signed byCA ownerExpiresStatus
AAA Certificate Services crt.sh Sectigo2028-12-31Valid
AddTrust External CA Root crt.sh Sectigo2020-05-30Expired

CRL and OCSP addresses

In the root certificate

COMODO RSA 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/COMODORSACertificationAuthority.crl

Used by the intermediates it issued

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

  • CRL: http://crl.comodoca.com/COMODORSACertificationAuthority.crl (23)
  • OCSP: http://ocsp.comodoca.com (23)

What happens when it expires

COMODO RSA Certification Authority is valid until 2038-01-18, about 11.2 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. Root programs can stop trusting it before it expires: Chrome 2026-09-30.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up COMODO RSA Certification Authority by common name (COMODO RSA 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 RSA Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 52F0E1C4E58EC629291B60317F074671B85D7EA80D5B07273463534B32B40234

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 AFE5D244A8D1194230FF479FE2F897BBCD7A8CB4

Linux (ca-certificates follows Mozilla: Included · Trusted for TLS)

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 RSA Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "COMODO RSA 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 "52:F0:E1:C4:E5:8E:C6:29:29:1B:60:31:7F:07:46:71:B8:5D:7E:A8:0D:5B:07:27:34:63:53:4B:32:B4:02:34"

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 RSA 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-rsa-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=52:F0:E1:C4:E5:8E:C6:29:29:1B:60:31:7F:07:46:71:B8:5D:7E:A8:0D:5B:07:27:34:63:53:4B:32:B4:02:34

FAQ

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

Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication. Distrust-after dates already set: Chrome 2026-09-30.

When does COMODO RSA Certification Authority expire?

On 2038-01-18, about 11.2 years after the 2026-11-10 data snapshot.

How many intermediate certificates has COMODO RSA Certification Authority issued?

The CCADB lists 42: 23 valid, 15 expired and 4 revoked. The newest valid one is Sectigo Public Server Authentication Root R46, valid until 2038-01-18.

Is COMODO RSA Certification Authority cross-signed?

Yes. The CCADB has 2 cross-certificate(s) with its subject and key, signed by AAA Certificate Services, AddTrust External CA Root; 1 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