Root certificate · Sectigo

Entrust Root Certification Authority

Entrust Root Certification Authority is a root CA certificate operated by Sectigo (RSA 2048, valid until 2026-11-27, SHA-256 73C17643). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—Yes
MozillaRemoved RemovedNo—Yes
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

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

Removed Chrome

Status
Removed

Removed Mozilla

Status
Removed

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 IKE Intermediate, 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=Entrust Root Certification Authority,OU=(c) 2006 Entrust\, Inc.,OU=www.entrust.net/CPS is incorporated by reference,O=Entrust\, Inc.,C=US
SHA-256
73C176434F1BC6D5ADF45B0E76E727287C8DE57616C1E6E6141A2B2CBC7D8E4C
SHA-1 (Windows thumbprint)
B31EB1B740E36C8402DADC37D44DF5D4674952F9
SPKI SHA-256
6DBFAE00D37B9CD73F8FB47DE65917AF00E0DDDF42DBCEAC20C17C0275EE2095
Valid from
2006-11-27
Expires
2026-11-27
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
456B5054
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email, Time Stamping, IP Security IKE Intermediate
EV policy OIDs (CCADB)
2.23.140.1.1, 2.16.840.1.114028.10.1.2 · TLS EV capable: Yes
Test websites
valid: https://entrustrootcertificationauthority.sectigo.com · expired: https://entrustrootcertificationauthority.sectigo.com:442 · revoked: https://entrustrootcertificationauthority.sectigo.com:444
CCADB record
A000132
PEM
sectigo-entrust-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 18 intermediate CA certificates signed directly by Entrust Root Certification Authority: 2 currently valid, 7 expired and 9 revoked (revoked includes those whose parent was revoked).

Showing 18 of 18: 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
Entrust Root Certification Authority - G2 → Entrust Root Certification Authority - G2 Sectigo2026-11-26Valid
Entrust Root Certification Authority - EC1 → Entrust Root Certification Authority - EC1 Sectigo2026-11-10Valid
UIS-IntB-CA Unisys Corporation2021-07-19Expired
UIS-IntB-CA Unisys Corporation2020-06-27Expired
UIS-IntB-CA Unisys Corporation2019-07-11Expired
UIS-IntB-CA Unisys Corporation2018-07-14Expired
Entrust Certification Authority - L1M Sectigo2024-11-19Expired
Entrust Root Certification Authority - G2 → Entrust Root Certification Authority - G2 Sectigo2024-09-23Expired
Entrust Certification Authority - L1A Entrust2017-01-05Expired
UIS-IntB-CA Unisys Corporation2024-07-01Revoked
UIS-IntB-CA Unisys Corporation2023-07-29Revoked
UIS-IntB-CA Unisys Corporation2022-07-28Revoked
Entrust Certification Authority - L1E Entrust2026-11-19Revoked
UIS-INTB2-CA Entrust2020-07-16Revoked
UIS-IntB-CA Unisys Corporation2020-07-13Revoked
Entrust Certification Authority - L1E Entrust2021-11-12Revoked
Entrust Certification Authority - L1E Entrust2021-11-12Revoked
Entrust Certification Authority - L1E Entrust2019-12-10Revoked

Cross-signed versions

No certificate in the CCADB has the same subject and public key as Entrust Root Certification Authority with a different issuer, so a client has to carry Entrust Root Certification Authority itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

Entrust Root 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.entrust.net/rootca1.crl

Used by the intermediates it issued

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

  • CRL: http://crl.entrust.net/rootca1.crl (2)
  • OCSP: http://ocsp.entrust.net (2)

What happens when it expires

Entrust Root Certification Authority is valid until 2026-11-27, about 0.0 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 Entrust Root Certification Authority by common name (Entrust Root 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 "Entrust Root Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 73C176434F1BC6D5ADF45B0E76E727287C8DE57616C1E6E6141A2B2CBC7D8E4C

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 B31EB1B740E36C8402DADC37D44DF5D4674952F9

Linux (ca-certificates follows Mozilla: Removed)

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 "Entrust Root Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Entrust Root 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 "73:C1:76:43:4F:1B:C6:D5:AD:F4:5B:0E:76:E7:27:28:7C:8D:E5:76:16:C1:E6:E6:14:1A:2B:2C:BC:7D:8E:4C"

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 Entrust, Inc. → Entrust Root 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-entrust-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=73:C1:76:43:4F:1B:C6:D5:AD:F4:5B:0E:76:E7:27:28:7C:8D:E5:76:16:C1:E6:E6:14:1A:2B:2C:BC:7D:8E:4C

FAQ

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

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

When does Entrust Root Certification Authority expire?

On 2026-11-27, about 0.0 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Entrust Root Certification Authority issued?

The CCADB lists 18: 2 valid, 7 expired and 9 revoked. The newest valid one is Entrust Root Certification Authority - G2, valid until 2026-11-26.

Is Entrust Root Certification Authority cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

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