Root certificate · Amazon Trust Services

Amazon Root CA 3

Amazon Root CA 3 is a root CA certificate operated by Amazon Trust Services (ECDSA P-256, valid until 2040-05-26, SHA-256 18CE6CFE). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2027-09-14Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2027-09-14 (sct_not_after). The CCADB lists EV policy OID 2.23.140.1.1 for this root, but Mozilla does not mark it as EV-enabled.

Included Chrome

Status
Included
Distrust for TLS after
2027-09-14

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, Document Signing, Encrypting File System, 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
Amazon Trust Services
Subject
CN=Amazon Root CA 3,O=Amazon,C=US
SHA-256
18CE6CFE7BF14E60B2E347B8DFE868CB31D02EBB3ADA271569F50343B46DB3A4
SHA-1 (Windows thumbprint)
0D44DD8C3C8C1A1A58756481E90F2E2AFFB3D26E
SPKI SHA-256
36ABC32656ACFC645C61B71613C4BF21C787F5CABBEE48348D58597803D7ABC9
Valid from
2015-05-26
Expires
2040-05-26
Key
ECDSA P-256
Signature algorithm
ecdsa-with-SHA256
Serial number
66C9FD5749736663F3B0B9AD9E89E7603F24A
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 · TLS EV capable: Yes
Test websites
valid: https://good.sca3a.amazontrust.com/ · expired: https://expired.sca3a.amazontrust.com/ · revoked: https://revoked.sca3a.amazontrust.com/
CCADB record
A002356
PEM
amazon-root-ca-3.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 21 intermediate CA certificates signed directly by Amazon Root CA 3: 15 currently valid, 0 expired and 6 revoked (revoked includes those whose parent was revoked).

Showing 20 of 21: 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
Amazon ECDSA 256 S16 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S15 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S19 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S14 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S18 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S20 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S17 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 S21 Amazon Trust Services2029-07-07Valid
Amazon ECDSA 256 Root EU M1 Amazon Trust Services2033-09-15Valid
Amazon ECDSA 256 M06 Amazon Trust Services2033-01-13Valid
Amazon ECDSA 256 M05 Amazon Trust Services2033-01-13Valid
Amazon ECDSA 256 M02 DigiCert2030-08-23Valid
Amazon ECDSA 256 M04 DigiCert2030-08-23Valid
Amazon ECDSA 256 M03 DigiCert2030-08-23Valid
Amazon ECDSA 256 M01 DigiCert2030-08-23Valid
Amazon ECDSA 256 S02 Amazon Trust Services2033-05-28Revoked
Amazon ECDSA 256 S04 Amazon Trust Services2033-05-28Revoked
Amazon ECDSA 256 S01 Amazon Trust Services2033-05-28Revoked
Amazon ECDSA 256 S05 Amazon Trust Services2033-05-28Revoked
Amazon ECDSA 256 S00 Amazon Trust Services2033-05-28Revoked

Cross-signed versions

1 certificate(s) in the CCADB have the same subject and public key as Amazon Root CA 3 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Amazon Root CA 3, can still build a chain.

Signed byCA ownerExpiresStatus
Starfield Services Root Certificate Authority - G2 crt.sh Amazon Trust Services2037-12-31Valid

CRL and OCSP addresses

In the root certificate

Amazon Root CA 3 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.rootca3.amazontrust.com/rootca3.crl

Used by the intermediates it issued

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

  • CRL: http://crl.rootca3.amazontrust.com/rootca3.crl (15)
  • OCSP: http://ocsp.rootca3.amazontrust.com (15)

What happens when it expires

Amazon Root CA 3 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. Root programs can stop trusting it before it expires: Chrome 2027-09-14.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up Amazon Root CA 3 by common name (Amazon Root CA 3) 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 3" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 18CE6CFE7BF14E60B2E347B8DFE868CB31D02EBB3ADA271569F50343B46DB3A4

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 0D44DD8C3C8C1A1A58756481E90F2E2AFFB3D26E

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 3"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Amazon Root CA 3"

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 "18:CE:6C:FE:7B:F1:4E:60:B2:E3:47:B8:DF:E8:68:CB:31:D0:2E:BB:3A:DA:27:15:69:F5:03:43:B4:6D:B3:A4"

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

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 amazon-root-ca-3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=18:CE:6C:FE:7B:F1:4E:60:B2:E3:47:B8:DF:E8:68:CB:31:D0:2E:BB:3A:DA:27:15:69:F5:03:43:B4:6D:B3:A4

FAQ

Is Amazon Root CA 3 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 2027-09-14.

When does Amazon Root CA 3 expire?

On 2040-05-26, about 13.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Amazon Root CA 3 issued?

The CCADB lists 21: 15 valid, 0 expired and 6 revoked. The newest valid one is Amazon ECDSA 256 S16, valid until 2029-07-07.

Is Amazon Root CA 3 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

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