Root certificate · DigiCert

DigiCert ECC P384 Root G5

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

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists EV policy OID 2.23.140.1.1, 2.23.140.1.3 for this root, but Mozilla does not mark it as EV-enabled.

Not included Chrome

Status
Not included

Not included Mozilla

Status
Not included

Not included Apple

Status
Not included

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Document 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 ECC P384 Root G5,O=DigiCert\, Inc.,C=US
SHA-256
C1468CF2254E6004B24696ABA209D1A30BA6E2DFF68A9A4E32C6AB414F90C8D9
SHA-1 (Windows thumbprint)
D1EEB1E8C09020BAB85D3DE27F78EE33A06CAEDB
SPKI SHA-256
BDACCBF2E8B27C0C02A689EE866C9B86EC04442AFCDDDD5D4EC36DEF21E761DD
Valid from
2021-01-15
Expires
2046-01-14
Key
ECDSA P-384
Signature algorithm
ecdsa-with-SHA384
Serial number
DF3D93765A379C59566EA92E2244F34
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping
EV policy OIDs (CCADB)
2.23.140.1.1, 2.23.140.1.3 · TLS EV capable: Yes
Test websites
valid: https://digicert-ecc-p384-root-g5.chain-demos.digicert.com/ · expired: https://digicert-ecc-p384-root-g5-expired.chain-demos.digicert.com/ · revoked: https://digicert-ecc-p384-root-g5-revoked.chain-demos.digicert.com/
CCADB record
A007749
PEM
digicert-ecc-p384-root-g5.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

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

Showing 2 of 2: 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
DigiCert G5 ECC SHA384 2021 CA1 DigiCert2031-04-13Valid
DigiCert G5 ECC SHA384 2021 CA1 DigiCert2031-03-10Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as DigiCert ECC P384 Root G5 with a different issuer, so a client has to carry DigiCert ECC P384 Root G5 itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

DigiCert 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/DigiCertECCP384RootG5.crl

Used by the intermediates it issued

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

  • CRL: http://crl3.digicert.com/DigiCertECCP384RootG5.crl (2)
  • OCSP: http://ocsp.digicert.com (2)

What happens when it expires

DigiCert 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 ECC P384 Root G5 by common name (DigiCert 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: Not included)

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 ECC P384 Root G5" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: C1468CF2254E6004B24696ABA209D1A30BA6E2DFF68A9A4E32C6AB414F90C8D9

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 D1EEB1E8C09020BAB85D3DE27F78EE33A06CAEDB

Linux (ca-certificates follows Mozilla: Not 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 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 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 "C1:46:8C:F2:25:4E:60:04:B2:46:96:AB:A2:09:D1:A3:0B:A6:E2:DF:F6:8A:9A:4E:32:C6:AB:41:4F:90:C8:D9"

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 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-ecc-p384-root-g5.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=C1:46:8C:F2:25:4E:60:04:B2:46:96:AB:A2:09:D1:A3:0B:A6:E2:DF:F6:8A:9A:4E:32:C6:AB:41:4F:90:C8:D9

FAQ

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

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does DigiCert 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 ECC P384 Root G5 issued?

The CCADB lists 2: 2 valid, 0 expired and 0 revoked. The newest valid one is DigiCert G5 ECC SHA384 2021 CA1, valid until 2031-04-13.

Is DigiCert ECC P384 Root G5 cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

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