Root certificate · Amazon Trust Services
Amazon Root CA 4
Amazon Root CA 4 is a root CA certificate operated by Amazon Trust Services (ECDSA P-384, valid until 2040-05-26, SHA-256 E35D2841). 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 | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
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.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.28.1 / Firefox 51
- Inclusion bug
- #1172401
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, 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
- Amazon Trust Services
- Subject
- CN=Amazon Root CA 4,O=Amazon,C=US
- SHA-256
E35D28419ED02025CFA69038CD623962458DA5C695FBDEA3C22B0BFB25897092- SHA-1 (Windows thumbprint)
F6108407D6F8BB67980CC2E244C2EBAE1CEF63BE- SPKI SHA-256
F7ECDED5C66047D28ED6466B543C40E0743ABE81D109254DCF845D4C2C7853C5- Valid from
- 2015-05-26
- Expires
- 2040-05-26
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
66C9FD7C1BB104C2943E5717B7B2CC81AC10E- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Document Signing, Secure Email, Encrypting File System, Time Stamping
- EV policy OIDs (CCADB)
- 2.23.140.1.1, 2.23.140.1.3 · TLS EV capable: Yes
- Test websites
- valid:
https://good.sca4a.amazontrust.com/· expired:https://expired.sca4a.amazontrust.com/· revoked:https://revoked.sca4a.amazontrust.com/ - CCADB record
- A002388
- PEM
- amazon-root-ca-4.pem
Intermediate CAs issued by this root
The CCADB lists 45 intermediate CA certificates signed directly by Amazon Root CA 4: 39 currently valid, 0 expired and 6 revoked (revoked includes those whose parent was revoked).
Showing 20 of 45: 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 |
|---|---|---|---|
| Amazon ECDSA 256 S13 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S25 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S26 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 256 S12 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S16 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S18 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S22 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S28 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S27 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 256 S11 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S14 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S20 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S23 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S29 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S15 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S21 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S19 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S24 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 256 S10 | Amazon Trust Services | 2029-07-07 | Valid |
| Amazon ECDSA 384 S17 | Amazon Trust Services | 2029-07-07 | Valid |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as Amazon Root CA 4 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Amazon Root CA 4, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Starfield Services Root Certificate Authority - G2 crt.sh | Amazon Trust Services | 2037-12-31 | Valid |
CRL and OCSP addresses
In the root certificate
Amazon Root CA 4 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.rootca4.amazontrust.com/rootca4.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 39 valid intermediates signed by Amazon Root CA 4; the number in brackets is how many of them use each address.
- CRL:
http://crl.rootca4.amazontrust.com/rootca4.crl(39) - OCSP:
http://ocsp.rootca4.amazontrust.com(39)
What happens when it expires
Amazon Root CA 4 is valid until 2040-05-26, about 13.5 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 Amazon Root CA 4 by common name (Amazon Root CA 4) 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 "Amazon Root CA 4" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: E35D28419ED02025CFA69038CD623962458DA5C695FBDEA3C22B0BFB25897092
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 F6108407D6F8BB67980CC2E244C2EBAE1CEF63BE
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 "Amazon Root CA 4"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Amazon Root CA 4"
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 "E3:5D:28:41:9E:D0:20:25:CF:A6:90:38:CD:62:39:62:45:8D:A5:C6:95:FB:DE:A3:C2:2B:0B:FB:25:89:70:92"
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 Amazon → Amazon Root CA 4.
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 amazon-root-ca-4.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=E3:5D:28:41:9E:D0:20:25:CF:A6:90:38:CD:62:39:62:45:8D:A5:C6:95:FB:DE:A3:C2:2B:0B:FB:25:89:70:92
FAQ
Is Amazon Root CA 4 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 Amazon Root CA 4 expire?
On 2040-05-26, about 13.5 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Amazon Root CA 4 issued?
The CCADB lists 45: 39 valid, 0 expired and 6 revoked. The newest valid one is Amazon ECDSA 256 S13, valid until 2029-07-07.
Is Amazon Root CA 4 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Starfield Services Root Certificate Authority - G2; 1 of them are still valid.
Other roots from Amazon Trust Services
- Amazon Root CA 1 RSA 2048 · 2038-01-17
- Amazon Root CA 2 RSA 4096 · 2040-05-26
- Amazon Root CA 3 ECDSA P-256 · 2040-05-26
- Starfield Services Root Certificate Authority - G2 RSA 2048 · 2037-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