Root certificate · DigiCert

DigiCert TLS ECC P384 Root G5

DigiCert TLS ECC P384 Root G5 is a root CA certificate operated by DigiCert (ECDSA P-384, valid until 2046-01-14, SHA-256 018E13F0). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.23.140.1.1
First included in
NSS 3.80 / Firefox 103
Inclusion bug
#1706228

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication

"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 TLS ECC P384 Root G5,O=DigiCert\, Inc.,C=US
SHA-256
018E13F0772532CF809BD1B17281867283FC48C6E13BE9C69812854A490C1B05
SHA-1 (Windows thumbprint)
17F3DE5E9F0F19E98EF61F32266E20C407AE30EE
SPKI SHA-256
A02FAFA192C8CB81CB1341554F9C05B71CCA2A890B0D1298D683647C961EFBDF
Valid from
2021-01-15
Expires
2046-01-14
Key
ECDSA P-384
Signature algorithm
ecdsa-with-SHA384
Serial number
9E09365ACF7D9C8B93E1C0B042A2EF3
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://digicert-tls-ecc-p384-root-g5.chain-demos.digicert.com/ · expired: https://digicert-tls-ecc-p384-root-g5-expired.chain-demos.digicert.com/ · revoked: https://digicert-tls-ecc-p384-root-g5-revoked.chain-demos.digicert.com/
CCADB record
A007717
PEM
digicert-tls-ecc-p384-root-g5.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 20 intermediate CA certificates signed directly by DigiCert TLS ECC P384 Root G5: 20 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 20 of 20: 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

3 certificate(s) in the CCADB have the same subject and public key as DigiCert TLS ECC P384 Root G5 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not DigiCert TLS ECC P384 Root G5, can still build a chain.

Signed byCA ownerExpiresStatus
DigiCert Global Root G3 crt.sh DigiCert2036-03-30Valid
DigiCert Global Root G3 crt.sh DigiCert2036-06-09Valid
DigiCert Global Root G3 crt.sh DigiCert2037-09-20Revoked

CRL and OCSP addresses

In the root certificate

DigiCert TLS ECC P384 Root G5 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/DigiCertTLSECCP384RootG5.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 20 valid intermediates signed by DigiCert TLS ECC P384 Root G5; the number in brackets is how many of them use each address.

  • CRL: http://crl.digicert.cn/DigiCertTLSECCP384RootG5.crl (10)
  • CRL: http://crl3.digicert.com/DigiCertTLSECCP384RootG5.crl (10)
  • OCSP: http://ocsp.digicert.cn (10)
  • OCSP: http://ocsp.digicert.com (10)

What happens when it expires

DigiCert TLS ECC P384 Root G5 is valid until 2046-01-14, about 19.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.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up DigiCert TLS ECC P384 Root G5 by common name (DigiCert TLS ECC P384 Root G5) 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 TLS ECC P384 Root G5" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 018E13F0772532CF809BD1B17281867283FC48C6E13BE9C69812854A490C1B05

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 17F3DE5E9F0F19E98EF61F32266E20C407AE30EE

Linux (ca-certificates follows Mozilla: Included · Trusted for TLS)

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 TLS ECC P384 Root G5"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "DigiCert TLS ECC P384 Root G5"

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 "01:8E:13:F0:77:25:32:CF:80:9B:D1:B1:72:81:86:72:83:FC:48:C6:E1:3B:E9:C6:98:12:85:4A:49:0C:1B:05"

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 TLS ECC P384 Root G5.

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 digicert-tls-ecc-p384-root-g5.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=01:8E:13:F0:77:25:32:CF:80:9B:D1:B1:72:81:86:72:83:FC:48:C6:E1:3B:E9:C6:98:12:85:4A:49:0C:1B:05

FAQ

Is DigiCert TLS ECC P384 Root G5 trusted by Chrome, Firefox, Safari and Windows?

Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication.

When does DigiCert TLS ECC P384 Root G5 expire?

On 2046-01-14, about 19.2 years after the 2026-11-10 data snapshot.

How many intermediate certificates has DigiCert TLS ECC P384 Root G5 issued?

The CCADB lists 20: 20 valid, 0 expired and 0 revoked. The newest valid one is DigiCert TLS ECC P384 Root G6, valid until 2036-10-07.

Is DigiCert TLS ECC P384 Root G5 cross-signed?

Yes. The CCADB has 3 cross-certificate(s) with its subject and key, signed by DigiCert Global Root G3; 2 of them are still valid.

Other roots from DigiCert

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