Root certificate · Sectigo
Entrust Root Certification Authority - G4
Entrust Root Certification Authority - G4 is a root CA certificate operated by Sectigo (RSA 4096, valid until 2037-12-27, SHA-256 DB3517D1). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | Yes |
| Mozilla | Included Included | No | 2024-11-19 | Yes |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
Mozilla stops trusting TLS certificates from this root issued after 2024-11-19. 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-19
- Trust bits
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.48 / Firefox 72
- Inclusion bug
- #1480510
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Document Signing, OCSP 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 - G4,OU=(c) 2015 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US
- SHA-256
DB3517D1F6732A2D5AB97C533EC70779EE3270A62FB4AC4238372460E6F01E88- SHA-1 (Windows thumbprint)
14884E862637B026AF59625C4077EC3529BA9601- SPKI SHA-256
36D7C79F3D089A0FF79972D90923DEA5CA76B4CCBAF7C2751CB152E9494F52D0- Valid from
- 2015-05-27
- Expires
- 2037-12-27
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
D9B5437FAFA9390F000000005565AD58- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Document 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
- CCADB record
- A005752
- PEM
- sectigo-entrust-root-ca-g4.pem
Intermediate CAs issued by this root
The CCADB lists 3 intermediate CA certificates signed directly by Entrust Root Certification Authority - G4: 0 currently valid, 0 expired and 3 revoked (revoked includes those whose parent was revoked).
Showing 3 of 3: 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.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| Entrust Digital Signing Root Certification Authority - DSR1 | Sectigo | 2030-12-30 | Revoked |
| Entrust Certification Authority - AATL1 | Entrust | 2037-12-20 | Revoked |
| Entrust Certification Authority - L1N | Entrust | 2030-12-22 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as Entrust Root Certification Authority - G4 with a different issuer, so a client has to carry Entrust Root Certification Authority - G4 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
Entrust Root Certification Authority - G4 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/g4ca.crl
What happens when it expires
Entrust Root Certification Authority - G4 is valid until 2037-12-27, 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-19.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up Entrust Root Certification Authority - G4 by common name (Entrust Root Certification Authority - G4) 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 - G4" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: DB3517D1F6732A2D5AB97C533EC70779EE3270A62FB4AC4238372460E6F01E88
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 14884E862637B026AF59625C4077EC3529BA9601
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 - G4"
# 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 - G4"
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 "DB:35:17:D1:F6:73:2A:2D:5A:B9:7C:53:3E:C7:07:79:EE:32:70:A6:2F:B4:AC:42:38:37:24:60:E6:F0:1E:88"
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 - G4.
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-entrust-root-ca-g4.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=DB:35:17:D1:F6:73:2A:2D:5A:B9:7C:53:3E:C7:07:79:EE:32:70:A6:2F:B4:AC:42:38:37:24:60:E6:F0:1E:88
FAQ
Is Entrust Root Certification Authority - G4 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-19.
When does Entrust Root Certification Authority - G4 expire?
On 2037-12-27, about 11.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Entrust Root Certification Authority - G4 issued?
The CCADB lists 3: 0 valid, 0 expired and 3 revoked.
Is Entrust Root Certification Authority - G4 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
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.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
- USERTrust RSA Certification Authority RSA 4096 · 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