中文

Root certificate · DigiCert

DigiCert Assured ID Root CA

DigiCert Assured ID Root CA is a root CA certificate operated by DigiCert (RSA 2048, valid until 2031-11-10, SHA-256 3E9099B5). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaIncluded IncludedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

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

Removed Chrome

Status
Removed

Included Mozilla

Status
Included
Trust bits
Email
EV policy OIDs
not EV-enabled
First included in
NSS 3.11.8 / Firefox 2
Inclusion bug
#364568

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 Assured ID Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US
SHA-256
3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
SHA-1 (Windows thumbprint)
0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
SPKI SHA-256
23F2EDFF3EDE90259A9E30F40AF8F912A5E5B3694E6938440341F6060E014FFA
Valid from
2006-11-10
Expires
2031-11-10
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
CE7E0E517D846FE8FE560FC1BF03039
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
EV policy OIDs (CCADB)
2.23.140.1.3, 2.16.840.1.114412.2.1 · TLS EV capable: Yes
Test websites
valid: https://assured-id-root-ca.chain-demos.digicert.com · expired: https://assured-id-root-ca-expired.chain-demos.digicert.com/ · revoked: https://assured-id-root-ca-revoked.chain-demos.digicert.com/
CCADB record
A000114
PEM
digicert-assured-id-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 64 intermediate CA certificates signed directly by DigiCert Assured ID Root CA: 28 currently valid, 23 expired and 13 revoked (revoked includes those whose parent was revoked).

Showing 20 of 64: 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
Imprivata Secure ID CA-2 DigiCert2031-10-05Valid
Data Management Intermediate CA3 DigiCert2031-11-09Valid
DigiCert Assured ID Grid Client RSA2048 SHA256 2024 CA1 DigiCert2031-11-09Valid
Verokey Secure Email G2 DigiCert2031-11-09Valid
Verokey Assured Business ID and Secure Email G2 DigiCert2031-11-09Valid
DigiCert Trusted Root G4 → DigiCert Trusted Root G4 DigiCert2031-11-09Valid
DigiCert Trusted Root G4 → DigiCert Trusted Root G4 DigiCert2031-11-09Valid
DigiCert Assured ID Grid Client RSA2048 SHA256 2022 CA1 DigiCert2031-11-09Valid
Verokey Assured Business ID and Secure Email DigiCert2031-11-09Valid
Verokey Secure Email DigiCert2031-11-09Valid
DigiCert Assured ID Grid TLS RSA2048 SHA256 2022 CA1 DigiCert2031-11-09Valid
DigiCert Assured ID TLS RSA4096 SHA256 2022 CA1 DigiCert2031-11-08Valid
DigiCert Assured ID SMIME RSA2048 SHA256 2021 CA1 DigiCert2031-11-09Valid
DigiCert Assured ID SMIME RSA SHA256 2020 CA1 DigiCert2030-12-07Valid
DigiCert Secure Auth CA2 DigiCert2030-10-08Valid
Riverbed Certificate Issuer DigiCert2028-11-20Valid
RVBD Certificate Issuer DigiCert2028-11-20Valid
TrustAsia Secure Enterprise Email CA DigiCert2028-04-27Valid
TrustAsia Secure Email CA DigiCert2028-04-27Valid
DigiCert Assured ID TLS CA DigiCert2030-02-09Valid

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

DigiCert Assured ID Root CA 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/DigiCertAssuredIDRootCA.crl
  • http://crl4.digicert.com/DigiCertAssuredIDRootCA.crl
  • http://crl.digicert-cn.com/DigiCertAssuredIDRootCA.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 28 valid intermediates signed by DigiCert Assured ID Root CA; the number in brackets is how many of them use each address.

  • CRL: http://crl3.digicert.com/DigiCertAssuredIDRootCA.crl (26)
  • CRL: http://crl4.digicert.com/DigiCertAssuredIDRootCA.crl (12)
  • CRL: http://crl.digicert-cn.com/DigiCertAssuredIDRootCA.crl (2)
  • OCSP: http://ocsp.digicert.com (26)
  • OCSP: http://ocsp.digicert-cn.com (2)

What happens when it expires

DigiCert Assured ID Root CA is valid until 2031-11-10, about 5.0 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 Assured ID Root CA by common name (DigiCert Assured ID Root CA) 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 CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C

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 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43

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 "DigiCert Assured ID Root CA"
# 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 CA"

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 "3E:90:99:B5:01:5E:8F:48:6C:00:BC:EA:9D:11:1E:E7:21:FA:BA:35:5A:89:BC:F1:DF:69:56:1E:3D:C6:32:5C"

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 CA.

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-assured-id-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=3E:90:99:B5:01:5E:8F:48:6C:00:BC:EA:9D:11:1E:E7:21:FA:BA:35:5A:89:BC:F1:DF:69:56:1E:3D:C6:32:5C

FAQ

Is DigiCert Assured ID Root CA trusted by Chrome, Firefox, Safari and Windows?

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

When does DigiCert Assured ID Root CA expire?

On 2031-11-10, about 5.0 years after the 2026-11-10 data snapshot.

How many intermediate certificates has DigiCert Assured ID Root CA issued?

The CCADB lists 64: 28 valid, 23 expired and 13 revoked. The newest valid one is Imprivata Secure ID CA-2, valid until 2031-10-05.

Is DigiCert Assured ID Root CA 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