Root certificate · Entrust
AffirmTrust Premium
AffirmTrust Premium is a root CA certificate operated by Entrust (RSA 4096, valid until 2040-12-31, SHA-256 70A73F7F). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | Yes |
| Mozilla | Removed Removed | No | — | Yes |
| Apple | Included Included | Yes | — | Yes |
| Microsoft | Included (NotBefore cutoff) Included (NotBefore cutoff) | Yes | — | Yes |
The CCADB lists EV policy OID 2.23.140.1.1, 1.3.6.1.4.1.34697.2.3 for this root, but Mozilla does not mark it as EV-enabled.
Removed Chrome
- Status
- Removed
Removed Mozilla
- Status
- Removed
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
- Allowed policies
- Server Authentication, Client Authentication, Code Signing, Timestamp Signing
Included (NotBefore cutoff) Microsoft
- Status
- Included (NotBefore cutoff)
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, 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
- Entrust
- Subject
- CN=AffirmTrust Premium,O=AffirmTrust,C=US
- SHA-256
70A73F7F376B60074248904534B11482D5BF0E698ECC498DF52577EBF2E93B9A- SHA-1 (Windows thumbprint)
D8A6332CE0036FB185F6634F7D6A066526322827- SPKI SHA-256
C7F43B4CF5B71568294F822B53762605F6DDD15CADECE739E9E2C3CBA61E9D67- Valid from
- 2010-01-29
- Expires
- 2040-12-31
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
6D8C1446B1A60AEE- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- 2.23.140.1.1, 1.3.6.1.4.1.34697.2.3 · TLS EV capable: Yes
- Test websites
- valid:
https://validpremium.affirmtrust.com/· expired:https://expiredpremium.affirmtrust.com/· revoked:https://revokedpremium.affirmtrust.com/ - CCADB record
- A000080
- PEM
- entrust-affirmtrust-premium.pem
Intermediate CAs issued by this root
The CCADB lists 5 intermediate CA certificates signed directly by AffirmTrust Premium: 0 currently valid, 0 expired and 5 revoked (revoked includes those whose parent was revoked).
Showing 5 of 5: 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 |
|---|---|---|---|
| AffirmTrust 4K TLS Root CA - 2022 | Entrust | 2040-12-30 | Revoked |
| AffirmTrust Extended Validation CA - EV2 | Entrust | 2030-12-02 | Revoked |
| AffirmTrust Extended Validation CA - EV2 | Entrust | 2030-12-02 | Revoked |
| AffirmTrust Premium Extended Validation CA | Entrust | 2040-12-31 | Revoked |
| AffirmTrust Premium Extended Validation CA | Entrust | 2040-12-31 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as AffirmTrust Premium with a different issuer, so a client has to carry AffirmTrust Premium itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
AffirmTrust Premium 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://crl.affirmtrust.com/crl/AffirmTrustPremium.crl
What happens when it expires
AffirmTrust Premium is valid until 2040-12-31, about 14.1 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 AffirmTrust Premium by common name (AffirmTrust Premium) 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 "AffirmTrust Premium" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 70A73F7F376B60074248904534B11482D5BF0E698ECC498DF52577EBF2E93B9A
Windows (Microsoft store: Included (NotBefore cutoff) · 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 D8A6332CE0036FB185F6634F7D6A066526322827
Linux (ca-certificates follows Mozilla: Removed)
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 "AffirmTrust Premium"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "AffirmTrust Premium"
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 "70:A7:3F:7F:37:6B:60:07:42:48:90:45:34:B1:14:82:D5:BF:0E:69:8E:CC:49:8D:F5:25:77:EB:F2:E9:3B:9A"
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 AffirmTrust → AffirmTrust Premium.
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 entrust-affirmtrust-premium.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=70:A7:3F:7F:37:6B:60:07:42:48:90:45:34:B1:14:82:D5:BF:0E:69:8E:CC:49:8D:F5:25:77:EB:F2:E9:3B:9A
FAQ
Is AffirmTrust Premium 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 AffirmTrust Premium expire?
On 2040-12-31, about 14.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has AffirmTrust Premium issued?
The CCADB lists 5: 0 valid, 0 expired and 5 revoked.
Is AffirmTrust Premium cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from Entrust
- AffirmTrust Commercial RSA 2048 · 2030-12-31
- AffirmTrust Networking RSA 2048 · 2030-12-31
- AffirmTrust Premium ECC ECDSA P-384 · 2040-12-31
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