Root certificate · DigiCert
DigiCert Assured ID Root G3
DigiCert Assured ID Root G3 is a root CA certificate operated by DigiCert (ECDSA P-384, valid until 2038-01-15, SHA-256 7E37CB8B). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, 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 | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-14 (sct_not_after). Mozilla treats it as an EV root for policy OID 2.16.840.1.114412.2.1.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2026-09-14
Included Mozilla
- Status
- Included
- Trust bits
- Websites, Email
- EV policy OIDs
- 2.16.840.1.114412.2.1
- 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
- Not-before cutoff
- 2021-08-01 (Code Signing)
"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 Assured ID Root G3,OU=www.digicert.com,O=DigiCert Inc,C=US
- SHA-256
7E37CB8B4C47090CAB36551BA6F45DB840680FBA166A952DB100717F43053FC2- SHA-1 (Windows thumbprint)
F517A24F9A48C6C9F8A200269FDC0F482CAB3089- SPKI SHA-256
15EED339594B304F8CF847B477371D8D6FEC61F4DB2B01AF589E7C53B35CAE4C- Valid from
- 2013-08-01
- Expires
- 2038-01-15
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
BA15AFA1DDFA0B54944AFCD24A06CEC- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email, Time Stamping
- EV policy OIDs (CCADB)
- 2.16.840.1.114412.2.1, 2.23.140.1.1, 2.23.140.1.3 · TLS EV capable: Yes
- Test websites
- valid:
https://assured-id-root-g3.chain-demos.digicert.com· expired:https://assured-id-root-g3-expired.chain-demos.digicert.com/· revoked:https://assured-id-root-g3-revoked.chain-demos.digicert.com/ - CCADB record
- A000116
- PEM
- digicert-assured-id-root-g3.pem
Intermediate CAs issued by this root
The CCADB lists 6 intermediate CA certificates signed directly by DigiCert Assured ID Root G3: 6 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).
Showing 6 of 6: 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 |
|---|---|---|---|
| DigiCert CS ECC P384 Root G5 | DigiCert | 2036-03-30 | Valid |
| DigiCert Assured ID G3 EUR CS ECC384 SHA384 2025 CA 1 | DigiCert | 2035-09-09 | Valid |
| DigiCert Assured ID G3 CS ECC384 SHA384 2025 CA1 | DigiCert | 2035-08-26 | Valid |
| DigiCert Assured ID G3 TLS ECC384 SHA384 2022 CA1 | DigiCert | 2032-03-02 | Valid |
| DigiCert Assured ID Client CA G3 | DigiCert | 2034-09-23 | Valid |
| DigiCert Assured ID CA G3 | DigiCert | 2028-08-01 | Valid |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as DigiCert Assured ID Root G3 with a different issuer, so a client has to carry DigiCert Assured ID Root G3 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
DigiCert Assured ID Root G3 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/DigiCertAssuredIDRootG3.crlhttp://crl4.digicert.com/DigiCertAssuredIDRootG3.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 6 valid intermediates signed by DigiCert Assured ID Root G3; the number in brackets is how many of them use each address.
- CRL:
http://crl3.digicert.com/DigiCertAssuredIDRootG3.crl(5) - CRL:
http://crl4.digicert.com/DigiCertAssuredIDRootG3.crl(1) - OCSP:
http://ocsp.digicert.com(6)
What happens when it expires
DigiCert Assured ID Root G3 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 Assured ID Root G3 by common name (DigiCert Assured ID Root G3) 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 Assured ID Root G3" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 7E37CB8B4C47090CAB36551BA6F45DB840680FBA166A952DB100717F43053FC2
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 F517A24F9A48C6C9F8A200269FDC0F482CAB3089
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 Assured ID Root G3"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "DigiCert Assured ID Root G3"
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 "7E:37:CB:8B:4C:47:09:0C:AB:36:55:1B:A6:F4:5D:B8:40:68:0F:BA:16:6A:95:2D:B1:00:71:7F:43:05:3F:C2"
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 Assured ID Root G3.
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-assured-id-root-g3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=7E:37:CB:8B:4C:47:09:0C:AB:36:55:1B:A6:F4:5D:B8:40:68:0F:BA:16:6A:95:2D:B1:00:71:7F:43:05:3F:C2
FAQ
Is DigiCert Assured ID Root G3 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. Distrust-after dates already set: Chrome 2026-09-14.
When does DigiCert Assured ID Root G3 expire?
On 2038-01-15, about 11.2 years after the 2026-11-10 data snapshot.
How many intermediate certificates has DigiCert Assured ID Root G3 issued?
The CCADB lists 6: 6 valid, 0 expired and 0 revoked. The newest valid one is DigiCert CS ECC P384 Root G5, valid until 2036-03-30.
Is DigiCert Assured ID Root G3 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
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 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
- DigiCert Trusted Root G4 RSA 4096 · 2038-01-15
- 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