Root certificate · Sectigo

Entrust Root Certification Authority - G2

Entrust Root Certification Authority - G2 is a root CA certificate operated by Sectigo (RSA 2048, valid until 2030-12-07, SHA-256 43DF5774). 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, 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 Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US
SHA-256
43DF5774B03E7FEF5FE40D931A7BEDF1BB2E6B42738C4E6D3841103D3AA7F339
SHA-1 (Windows thumbprint)
8CF427FD790C3AD166068DE81E57EFBB932272D4
SPKI SHA-256
76EE8590374C715437BBCA6BBA6028EADDE2DC6DBBB8C3F610E851F11D1AB7F5
Valid from
2009-07-07
Expires
2030-12-07
Key
RSA 2048
Signature algorithm
sha256WithRSAEncryption
Serial number
4A538C28
Country
US
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://entrustrootcertificationauthorityg2.sectigo.com · expired: https://entrustrootcertificationauthorityg2.sectigo.com:442 · revoked: https://entrustrootcertificationauthorityg2.sectigo.com:444
CCADB record
A000298
PEM
sectigo-entrust-root-ca-g2.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 29 intermediate CA certificates signed directly by Entrust Root Certification Authority - G2: 12 currently valid, 3 expired and 14 revoked (revoked includes those whose parent was revoked).

Showing 20 of 29: 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 Legacy Server Authentication CA OV R30 Sectigo2030-12-06Valid
SSL.com TLS RSA Root CA 2022 → SSL.com TLS RSA Root CA 2022 SSL.com2030-12-06Valid
Entrust SMIME Root CA - 2022 Sectigo2030-12-07Valid
Namirial OV SSL CA 2023 Sectigo2030-12-07Valid
CrowdStrike TLS CA 2022 Sectigo2030-12-06Valid
Entrust Certification Authority - ES QWAC2 Sectigo2030-12-01Valid
Entrust Code Signing Root Certification Authority - CSBR1 Sectigo2030-11-07Valid
Entrust Class 1 Client CA - SHA256 Sectigo2030-11-16Valid
Entrust Certification Authority - L1K Sectigo2030-12-05Valid
Entrust Extended Validation Code Signing CA - EVCS1 Sectigo2030-11-10Valid
Entrust Code Signing CA - OVCS1 Sectigo2030-11-10Valid
Entrust Certification Authority - L1M Sectigo2030-10-15Valid
UIS-IntB-CA Unisys Corporation2018-07-01Expired
Entrust Certification Authority - L1K Sectigo2024-10-23Expired
Entrust Certification Authority - L1K Sectigo2024-08-27Expired
Entrust 4K EV TLS Root CA - 2022 Entrust2030-12-06Revoked
Entrust 4K TLS Root CA - 2022 Entrust2030-12-06Revoked
Namirial EV SSL CA 2023 Entrust2030-12-07Revoked
CRYPTAS OV Issuing CA Entrust2030-12-01Revoked
CRYPTAS EV Issuing CA Entrust2030-12-01Revoked

Cross-signed versions

2 certificate(s) in the CCADB have the same subject and public key as Entrust Root Certification Authority - G2 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 - G2, can still build a chain.

Signed byCA ownerExpiresStatus
Entrust Root Certification Authority crt.sh Sectigo2026-11-26Valid
Entrust Root Certification Authority crt.sh Sectigo2024-09-23Expired

CRL and OCSP addresses

In the root certificate

Entrust Root Certification Authority - G2 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/g2ca.crl

Used by the intermediates it issued

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

  • CRL: http://crl.entrust.net/g2ca.crl (12)
  • OCSP: http://ocsp.entrust.net (12)

What happens when it expires

Entrust Root Certification Authority - G2 is valid until 2030-12-07, about 4.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 - G2 by common name (Entrust Root Certification Authority - G2) 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 - G2" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 43DF5774B03E7FEF5FE40D931A7BEDF1BB2E6B42738C4E6D3841103D3AA7F339

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 8CF427FD790C3AD166068DE81E57EFBB932272D4

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 - G2"
# 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 - G2"

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 "43:DF:57:74:B0:3E:7F:EF:5F:E4:0D:93:1A:7B:ED:F1:BB:2E:6B:42:73:8C:4E:6D:38:41:10:3D:3A:A7:F3:39"

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

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-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=43:DF:57:74:B0:3E:7F:EF:5F:E4:0D:93:1A:7B:ED:F1:BB:2E:6B:42:73:8C:4E:6D:38:41:10:3D:3A:A7:F3:39

FAQ

Is Entrust Root Certification Authority - G2 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 - G2 expire?

On 2030-12-07, about 4.1 years after the 2026-11-10 data snapshot.

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

The CCADB lists 29: 12 valid, 3 expired and 14 revoked. The newest valid one is Sectigo Legacy Server Authentication CA OV R30, valid until 2030-12-06.

Is Entrust Root Certification Authority - G2 cross-signed?

Yes. The CCADB has 2 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