Root certificate · Atos
Atos TrustedRoot 2011
Atos TrustedRoot 2011 is a root CA certificate operated by Atos (RSA 2048, valid until 2030-12-31, SHA-256 F356BEA2). 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 | — | No |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
The CCADB lists no EV policy OID for Atos TrustedRoot 2011.
Removed Chrome
- Status
- Removed
Included Mozilla
- Status
- Included
- Trust bits
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.16 / Firefox 29
- Inclusion bug
- #711366
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, OCSP Signing, Secure Email, Time Stamping
- Not-before cutoff
- 2020-06-01 (OCSP 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
- Atos
- Subject
- C=DE,O=Atos,CN=Atos TrustedRoot 2011
- SHA-256
F356BEA244B7A91EB35D53CA9AD7864ACE018E2D35D5F8F96DDF68A6F41AA474- SHA-1 (Windows thumbprint)
2BB1F53E550C1DC5F1D4E6B76A464B550602AC21- SPKI SHA-256
E5CA37BC7B6C361979BC6B123CA9A1DB019046D7FF5F57DFB854B19D10B0682F- Valid from
- 2011-07-07
- Expires
- 2030-12-31
- Key
- RSA 2048
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
5C33CB622C5FB332- Country
- DE
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://pki-valid.atos.net· expired:https://pki-expired.atos.net· revoked:https://pki-revoked.atos.net - CCADB record
- A000085
- PEM
- atos-trustedroot-2011.pem
Intermediate CAs issued by this root
The CCADB lists 56 intermediate CA certificates signed directly by Atos TrustedRoot 2011: 18 currently valid, 7 expired and 31 revoked (revoked includes those whose parent was revoked).
Showing 20 of 56: 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.
Cross-signed versions
No certificate in the CCADB has the same subject and public key as Atos TrustedRoot 2011 with a different issuer, so a client has to carry Atos TrustedRoot 2011 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
Atos TrustedRoot 2011 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://pki-crl.atos.net/crl/Atos_TrustedRoot_CA_2011.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 18 valid intermediates signed by Atos TrustedRoot 2011; the number in brackets is how many of them use each address.
- CRL:
http://pki-crl.atos.net/crl/Atos_TrustedRoot_CA_2011.crl(18) - CRL:
ldap://pki-ldap.atos.net/cn=Atos%20TrustedRoot%202011,ou=CA,ou=Atos%20TC,o=Atos,dc=atos,dc=net?certificateRevocationList(9) - OCSP:
http://pki-ocsp.atos.net(18)
What happens when it expires
Atos TrustedRoot 2011 is valid until 2030-12-31, about 4.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 Atos TrustedRoot 2011 by common name (Atos TrustedRoot 2011) 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 "Atos TrustedRoot 2011" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: F356BEA244B7A91EB35D53CA9AD7864ACE018E2D35D5F8F96DDF68A6F41AA474Windows (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 2BB1F53E550C1DC5F1D4E6B76A464B550602AC21Linux (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 "Atos TrustedRoot 2011"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Atos TrustedRoot 2011"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 "F3:56:BE:A2:44:B7:A9:1E:B3:5D:53:CA:9A:D7:86:4A:CE:01:8E:2D:35:D5:F8:F9:6D:DF:68:A6:F4:1A:A4:74"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 Atos → Atos TrustedRoot 2011.
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 atos-trustedroot-2011.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=F3:56:BE:A2:44:B7:A9:1E:B3:5D:53:CA:9A:D7:86:4A:CE:01:8E:2D:35:D5:F8:F9:6D:DF:68:A6:F4:1A:A4:74FAQ
Is Atos TrustedRoot 2011 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 Atos TrustedRoot 2011 expire?
On 2030-12-31, about 4.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Atos TrustedRoot 2011 issued?
The CCADB lists 56: 18 valid, 7 expired and 31 revoked. The newest valid one is Eviden TrustedRoot Client CA for Bull G2 2026, valid until 2030-12-31.
Is Atos TrustedRoot 2011 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from Atos
- Atos TrustedRoot Root CA ECC TLS 2021 ECDSA P-384 · 2041-04-17
- Atos TrustedRoot Root CA RSA TLS 2021 RSA 4096 · 2041-04-17
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