Root certificate · Sectigo

Entrust.net Certification Authority (2048)

Entrust.net Certification Authority (2048) is a root CA certificate operated by Sectigo (RSA 2048, valid until 2029-07-24, SHA-256 6DC47172). 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—No
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.15 / Firefox 23
Inclusion bug
#694536

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=Entrust.net Certification Authority (2048),OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),O=Entrust.net
SHA-256
6DC47172E01CBCB0BF62580D895FE2B8AC9AD4F873801E0C10B9C837D21EB177
SHA-1 (Windows thumbprint)
503006091D97D4F5AE39F7CBE7927D7D652D3431
SPKI SHA-256
1EA3C5E43ED66C2DA2983A42A4A79B1E906786CE9F1B58621419A00463A87D38
Valid from
1999-12-24
Expires
2029-07-24
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
3863DEF8
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, 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://entrustnetcertificationauthority2048.sectigo.com · expired: https://entrustnetcertificationauthority2048.sectigo.com:442 · revoked: https://entrustnetcertificationauthority2048.sectigo.com:444
CCADB record
A000133
PEM
sectigo-entrust-net-ca-2048.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 35 intermediate CA certificates signed directly by Entrust.net Certification Authority (2048): 9 currently valid, 20 expired and 6 revoked (revoked includes those whose parent was revoked).

Showing 20 of 35: 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 Digital Signing Root Certification Authority - DSR1 Sectigo2029-07-23Valid
Entrust Certification Authority - L1K Sectigo2029-07-23Valid
Entrust Enterprise Intermediate CA - ICA1 Sectigo2029-07-07Valid
Entrust Class 2 Client CA - C2CA2 Sectigo2029-07-16Valid
Entrust Certification Authority - L1F Sectigo2029-07-05Valid
Entrust Class 2 Client CA Sectigo2029-06-29Valid
Entrust Class 2 Client CA Sectigo2028-12-20Valid
Entrust Class 3 Client CA - SHA256 Sectigo2029-06-25Valid
Entrust Timestamping CA - TS1 Sectigo2029-06-22Valid
UIS-IntB-CA Unisys Corporation2018-07-01Expired
UIS-IntB-CA Unisys Corporation2018-07-01Expired
Entrust Certification Authority - L1K Sectigo2024-10-11Expired
UIS-IntB-CA Unisys Corporation2017-07-25Expired
UIS-IntB-CA Unisys Corporation2017-07-25Expired
UIS-IntB-CA Unisys Corporation2017-07-24Expired
Entrust Code Signing Certification Authority - L1D Entrust2021-11-12Expired
Entrust Certification Authority - L1C Entrust2021-11-11Expired
Entrust Class 1 Client CA Entrust2021-11-12Expired
Entrust Class 1 Client CA Entrust2021-11-11Expired
Entrust Code Signing Certification Authority - L1D Entrust2021-11-12Expired

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

Entrust.net Certification Authority (2048) 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/2048ca.crl

Used by the intermediates it issued

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

  • CRL: http://crl.entrust.net/2048ca.crl (9)
  • OCSP: http://ocsp.entrust.net (9)

What happens when it expires

Entrust.net Certification Authority (2048) is valid until 2029-07-24, about 2.7 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.net Certification Authority (2048) by common name (Entrust.net Certification Authority (2048)) 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.net Certification Authority (2048)" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 6DC47172E01CBCB0BF62580D895FE2B8AC9AD4F873801E0C10B9C837D21EB177

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 503006091D97D4F5AE39F7CBE7927D7D652D3431

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.net Certification Authority (2048)"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Entrust.net Certification Authority (2048)"

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 "6D:C4:71:72:E0:1C:BC:B0:BF:62:58:0D:89:5F:E2:B8:AC:9A:D4:F8:73:80:1E:0C:10:B9:C8:37:D2:1E:B1:77"

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.net → Entrust.net Certification Authority (2048).

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-net-ca-2048.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=6D:C4:71:72:E0:1C:BC:B0:BF:62:58:0D:89:5F:E2:B8:AC:9A:D4:F8:73:80:1E:0C:10:B9:C8:37:D2:1E:B1:77

FAQ

Is Entrust.net Certification Authority (2048) 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.net Certification Authority (2048) expire?

On 2029-07-24, about 2.7 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Entrust.net Certification Authority (2048) issued?

The CCADB lists 35: 9 valid, 20 expired and 6 revoked. The newest valid one is Entrust Digital Signing Root Certification Authority - DSR1, valid until 2029-07-23.

Is Entrust.net Certification Authority (2048) 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