Root certificate · Sectigo
USERTrust RSA Certification Authority
USERTrust RSA Certification Authority is a root CA certificate operated by Sectigo (RSA 4096, valid until 2038-01-18, SHA-256 E793C9B0). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2026-09-30 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | 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=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US
- SHA-256
E793C9B02FD8AA13E21C31228ACCB08119643B749C898964B1746D46C3D4CBD2- SHA-1 (Windows thumbprint)
2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E- SPKI SHA-256
C784333D20BCD742B9FDC3236F4E509B8937070E73067E254DD3BF9C45BF4DDE- Valid from
- 2010-02-01
- Expires
- 2038-01-18
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
1FD6D30FCA3CA51A81BBC640E35032D- Country
- US
- 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://usertrustrsacertificationauthority-ev.comodoca.com/· expired:https://usertrustrsacertificationauthority-ev.comodoca.com:442/· revoked:https://usertrustrsacertificationauthority-ev.comodoca.com:444/ - CCADB record
- A000286
- PEM
- sectigo-usertrust-rsa-ca.pem
Intermediate CAs issued by this root
The CCADB lists 389 intermediate CA certificates signed directly by USERTrust RSA Certification Authority: 288 currently valid, 86 expired and 15 revoked (revoked includes those whose parent was revoked).
Showing 20 of 389: 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.
Cross-signed versions
2 certificate(s) in the CCADB have the same subject and public key as USERTrust RSA Certification Authority but a different issuer. A server can send one of them so that clients which trust the issuing root, but not USERTrust RSA Certification Authority, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| AAA Certificate Services crt.sh | Sectigo | 2028-12-31 | Valid |
| AddTrust External CA Root crt.sh | Sectigo | 2020-05-30 | Expired |
CRL and OCSP addresses
In the root certificate
USERTrust 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.usertrust.com/USERTrustRSACertificationAuthority.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 288 valid intermediates signed by USERTrust RSA Certification Authority; the number in brackets is how many of them use each address.
- CRL:
http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl(287) - CRL:
http://crl.trust-provider.com/USERTrustRSACertificationAuthority.crl(1) - OCSP:
http://ocsp.usertrust.com(287) - OCSP:
http://ocsp.trust-provider.com(1)
What happens when it expires
USERTrust 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 USERTrust RSA Certification Authority by common name (USERTrust 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 "USERTrust RSA Certification Authority" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: E793C9B02FD8AA13E21C31228ACCB08119643B749C898964B1746D46C3D4CBD2
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 2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E
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 "USERTrust RSA Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "USERTrust 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 "E7:93:C9:B0:2F:D8:AA:13:E2:1C:31:22:8A:CC:B0:81:19:64:3B:74:9C:89:89:64:B1:74:6D:46:C3:D4:CB:D2"
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 The USERTRUST Network → USERTrust 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.
# 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-usertrust-rsa-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=E7:93:C9:B0:2F:D8:AA:13:E2:1C:31:22:8A:CC:B0:81:19:64:3B:74:9C:89:89:64:B1:74:6D:46:C3:D4:CB:D2
FAQ
Is USERTrust 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 USERTrust RSA Certification Authority expire?
On 2038-01-18, about 11.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has USERTrust RSA Certification Authority issued?
The CCADB lists 389: 288 valid, 86 expired and 15 revoked. The newest valid one is iTrust RSA EV SSL CA, valid until 2034-11-05.
Is USERTrust 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
- AAA Certificate Services RSA 2048 · 2028-12-31
- COMODO Certification Authority RSA 2048 · 2029-12-31
- COMODO Certification Authority RSA 2048 · 2030-12-31
- COMODO ECC Certification Authority ECDSA P-384 · 2038-01-18
- COMODO RSA Certification Authority RSA 4096 · 2038-01-18
- Entrust Root Certification Authority RSA 2048 · 2026-11-27
- Entrust Root Certification Authority - EC1 ECDSA P-384 · 2037-12-18
- Entrust Root Certification Authority - G2 RSA 2048 · 2030-12-07
- Entrust Root Certification Authority - G4 RSA 4096 · 2037-12-27
- Entrust.net Certification Authority (2048) RSA 2048 · 2029-07-24
- Sectigo Public Server Authentication Root E46 ECDSA P-384 · 2046-03-21
- Sectigo Public Server Authentication Root R46 RSA 4096 · 2046-03-21
- USERTrust ECC Certification Authority ECDSA P-384 · 2038-01-18
Sources
- CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
- CCADB — All Certificate Information (root and intermediate), CSV V5
- CCADB — Mozilla Included CA Certificate Report
- CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV