Root certificate · DigiCert
DigiCert Trusted Root G4
DigiCert Trusted Root G4 is a root CA certificate operated by DigiCert (RSA 4096, valid until 2038-01-15, SHA-256 552F7BDC). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2026-09-14 | Yes |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-14 (sct_not_after). The CCADB lists EV policy OID 2.23.140.1.1, 2.16.840.1.114412.2.1, 2.23.140.1.3 for this root, but Mozilla does not mark it as EV-enabled.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2026-09-14
Included Mozilla
- Status
- Included
- Trust bits
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.16.3 / Firefox 32
- Inclusion bug
- #908827
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
- DigiCert
- Subject
- CN=DigiCert Trusted Root G4,OU=www.digicert.com,O=DigiCert Inc,C=US
- SHA-256
552F7BDCF1A7AF9E6CE672017F4F12ABF77240C78E761AC203D1D9D20AC89988- SHA-1 (Windows thumbprint)
DDFB16CD4931C973A2037D3FC83A4D7D775D05E4- SPKI SHA-256
59DF317BFA9F4F0AB7CA514D7772296AA2C765B87664D08B96E57399E364729C- Valid from
- 2013-08-01
- Expires
- 2038-01-15
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
59B1B579E8E2132E23907BDA777755C- 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.114412.2.1, 2.23.140.1.3 · TLS EV capable: Yes
- Test websites
- valid:
https://trusted-root-g4.chain-demos.digicert.com/· expired:https://trusted-root-g4-expired.chain-demos.digicert.com/· revoked:https://trusted-root-g4-revoked.chain-demos.digicert.com/ - CCADB record
- A000121
- PEM
- digicert-trusted-root-g4.pem
Intermediate CAs issued by this root
The CCADB lists 32 intermediate CA certificates signed directly by DigiCert Trusted Root G4: 32 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).
Showing 20 of 32: 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.
Cross-signed versions
5 certificate(s) in the CCADB have the same subject and public key as DigiCert Trusted Root G4 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not DigiCert Trusted Root G4, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| VeriSign Class 3 Public Primary Certification Authority - G5 crt.sh | DigiCert | 2031-09-21 | Valid |
| DigiCert High Assurance EV Root CA crt.sh | DigiCert | 2031-11-09 | Valid |
| DigiCert Assured ID Root CA crt.sh | DigiCert | 2031-11-09 | Valid |
| DigiCert Assured ID Root CA crt.sh | DigiCert | 2031-11-09 | Valid |
| DigiCert Global Root CA crt.sh | DigiCert | 2023-10-22 | Expired |
CRL and OCSP addresses
In the root certificate
DigiCert Trusted Root 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://crl3.digicert.com/DigiCertTrustedRootG4.crlhttp://crl4.digicert.com/DigiCertTrustedRootG4.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 32 valid intermediates signed by DigiCert Trusted Root G4; the number in brackets is how many of them use each address.
- CRL:
http://crl3.digicert.com/DigiCertTrustedRootG4.crl(28) - CRL:
http://crl4.digicert.com/DigiCertTrustedRootG4.crl(5) - OCSP:
http://ocsp.digicert.com(32)
What happens when it expires
DigiCert Trusted Root G4 is valid until 2038-01-15, about 11.2 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: Chrome 2026-09-14.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up DigiCert Trusted Root G4 by common name (DigiCert Trusted Root 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 "DigiCert Trusted Root G4" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 552F7BDCF1A7AF9E6CE672017F4F12ABF77240C78E761AC203D1D9D20AC89988Windows (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 DDFB16CD4931C973A2037D3FC83A4D7D775D05E4Linux (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 "DigiCert Trusted Root G4"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "DigiCert Trusted Root 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 "55:2F:7B:DC:F1:A7:AF:9E:6C:E6:72:01:7F:4F:12:AB:F7:72:40:C7:8E:76:1A:C2:03:D1:D9:D2:0A:C8:99: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 DigiCert Inc → DigiCert Trusted Root 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 digicert-trusted-root-g4.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=55:2F:7B:DC:F1:A7:AF:9E:6C:E6:72:01:7F:4F:12:AB:F7:72:40:C7:8E:76:1A:C2:03:D1:D9:D2:0A:C8:99:88FAQ
Is DigiCert Trusted Root G4 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Chrome, Apple, Microsoft trust it for TLS server authentication; Mozilla do not. Distrust-after dates already set: Chrome 2026-09-14.
When does DigiCert Trusted Root G4 expire?
On 2038-01-15, about 11.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has DigiCert Trusted Root G4 issued?
The CCADB lists 32: 32 valid, 0 expired and 0 revoked. The newest valid one is DigiCert Trusted G4 Multi Doc Signing RSA4096 SHA384 2026 CA1, valid until 2036-08-18.
Is DigiCert Trusted Root G4 cross-signed?
Yes. The CCADB has 5 cross-certificate(s) with its subject and key, signed by VeriSign Class 3 Public Primary Certification Authority - G5, DigiCert High Assurance EV Root CA, DigiCert Assured ID Root CA, DigiCert Global Root CA; 4 of them are still valid.
Other roots from DigiCert
- DigiCert Assured ID Root CA RSA 2048 · 2031-11-10
- DigiCert Assured ID Root G2 RSA 2048 · 2038-01-15
- DigiCert Assured ID Root G3 ECDSA P-384 · 2038-01-15
- DigiCert ECC P384 Root G5 ECDSA P-384 · 2046-01-14
- DigiCert Global Root CA RSA 2048 · 2031-11-10
- DigiCert Global Root G2 RSA 2048 · 2038-01-15
- DigiCert Global Root G3 ECDSA P-384 · 2038-01-15
- DigiCert High Assurance EV Root CA RSA 2048 · 2031-11-10
- DigiCert RSA4096 Root G5 RSA 4096 · 2046-01-14
- DigiCert TLS ECC P384 Root G5 ECDSA P-384 · 2046-01-14
- DigiCert TLS RSA4096 Root G5 RSA 4096 · 2046-01-14
- QuoVadis Root CA 1 G3 RSA 4096 · 2042-01-12
- QuoVadis Root CA 2 RSA 4096 · 2031-11-24
- QuoVadis Root CA 2 G3 RSA 4096 · 2042-01-12
- QuoVadis Root CA 3 RSA 4096 · 2031-11-24
- QuoVadis Root CA 3 G3 RSA 4096 · 2042-01-12
- QuoVadis TLS ECC P384 Root G4 ECDSA P-384 · 2048-03-09
- QuoVadis TLS RSA 4096 Root G4 RSA 4096 · 2048-03-09
- Verizon Global Root CA RSA 2048 · 2034-07-30
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