Root certificate · Sectigo

Entrust Root Certification Authority - EC1

Entrust Root Certification Authority - EC1 is a root CA certificate operated by Sectigo (ECDSA P-384, valid until 2037-12-18, SHA-256 02ED0EB2). 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
MozillaIncluded IncludedNo2024-11-30Yes
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

Mozilla stops trusting TLS certificates from this root issued after 2024-11-30. 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

Included Mozilla

Status
Included
Distrust for TLS after
2024-11-30
Trust bits
Email
EV policy OIDs
not EV-enabled
First included in
NSS 3.18 / Firefox 38
Inclusion bug
#849950

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, 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 - EC1,OU=(c) 2012 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US
SHA-256
02ED0EB28C14DA45165C566791700D6451D7FB56F0B2AB1D3B8EB070E56EDFF5
SHA-1 (Windows thumbprint)
20D80640DF9B25F512253A11EAF7598AEB14B547
SPKI SHA-256
FEA2B7D645FBA73D753C1EC9A7870C40E1F7B0C561E927B985BF711866E36F22
Valid from
2012-12-18
Expires
2037-12-18
Key
ECDSA P-384
Signature algorithm
ecdsa-with-SHA384
Serial number
A68B79290000000050D091F9
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email, Time Stamping
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://entrustrootcertificationauthorityec1.sectigo.com · expired: https://entrustrootcertificationauthorityec1.sectigo.com:442 · revoked: https://entrustrootcertificationauthorityec1.sectigo.com:444
CCADB record
A000299
PEM
sectigo-entrust-root-ca-ec1.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

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

Showing 4 of 4: 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 Certification Authority - L1J Sectigo2037-10-05Valid
Entrust Certification Authority - L1F Sectigo2037-10-05Valid
Entrust Certification Authority - L1E Entrust2024-10-22Revoked
Entrust Certification Authority - L1E Entrust2024-09-12Revoked

Cross-signed versions

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

Signed byCA ownerExpiresStatus
Entrust Root Certification Authority crt.sh Sectigo2026-11-10Valid

CRL and OCSP addresses

In the root certificate

Entrust Root Certification Authority - EC1 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/ec1root.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 - EC1; the number in brackets is how many of them use each address.

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

What happens when it expires

Entrust Root Certification Authority - EC1 is valid until 2037-12-18, about 11.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. Root programs can stop trusting it before it expires: Mozilla 2024-11-30.

Check whether your device trusts it

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

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 20D80640DF9B25F512253A11EAF7598AEB14B547

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 "Entrust Root Certification Authority - EC1"
# 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 - EC1"

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 "02:ED:0E:B2:8C:14:DA:45:16:5C:56:67:91:70:0D:64:51:D7:FB:56:F0:B2:AB:1D:3B:8E:B0:70:E5:6E:DF:F5"

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 - EC1.

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-ec1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=02:ED:0E:B2:8C:14:DA:45:16:5C:56:67:91:70:0D:64:51:D7:FB:56:F0:B2:AB:1D:3B:8E:B0:70:E5:6E:DF:F5

FAQ

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

As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not. Distrust-after dates already set: Mozilla 2024-11-30.

When does Entrust Root Certification Authority - EC1 expire?

On 2037-12-18, about 11.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Entrust Root Certification Authority - EC1 issued?

The CCADB lists 4: 2 valid, 0 expired and 2 revoked. The newest valid one is Entrust Certification Authority - L1J, valid until 2037-10-05.

Is Entrust Root Certification Authority - EC1 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Entrust Root Certification Authority; 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