Root certificate · Deutsche Telekom Security
Telekom Security TLS RSA Root 2023
Telekom Security TLS RSA Root 2023 is a root CA certificate operated by Deutsche Telekom Security (RSA 4096, valid until 2048-03-27, SHA-256 EFC65CAD). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Mozilla, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2027-08-30 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Not included Not included | No | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2027-08-30 (sct_not_after). Mozilla treats it as an EV root for policy OID 2.23.140.1.1.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2027-08-30
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.23.140.1.1
- First included in
- NSS 3.98 / Firefox 124
- Inclusion bug
- #1820592
Not included Apple
- Status
- Not included
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication
"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
- Deutsche Telekom Security GmbH
- Subject
- CN=Telekom Security TLS RSA Root 2023,O=Deutsche Telekom Security GmbH,C=DE
- SHA-256
EFC65CADBB59ADB6EFE84DA22311B35624B71B3B1EA0DA8B6655174EC8978646- SHA-1 (Windows thumbprint)
54D3ACB3BD5756F6859DCEE5C321E2D4AD83D093- SPKI SHA-256
0E05E9BB23869EB689DC56839DCEC475A3AE75FA6B50BC5A4978360CBE673323- Valid from
- 2023-03-28
- Expires
- 2048-03-27
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
219C542DE8F6EC7177FA4EE8C3705797- Country
- DE
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://active.tstlsrr23.test.telesec.de/· expired:https://expired.tstlsrr23.test.telesec.de/· revoked:https://revoked.tstlsrr23.test.telesec.de/ - CCADB record
- A011215
- PEM
- telekom-security-tls-rsa-root-2023.pem
Intermediate CAs issued by this root
The CCADB lists 8 intermediate CA certificates signed directly by Telekom Security TLS RSA Root 2023: 7 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 8 of 8: 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 |
|---|---|---|---|
| Telekom Security OV RSA CA 26A | Deutsche Telekom Security GmbH | 2029-03-18 | Valid |
| Telekom Security OV RSA CA 26B | Deutsche Telekom Security GmbH | 2029-03-18 | Valid |
| Telekom Security OV RSA qualified CA 25 | Deutsche Telekom Security GmbH | 2035-10-22 | Valid |
| Telekom Security EV RSA CA 25 | Deutsche Telekom Security GmbH | 2035-02-26 | Valid |
| Telekom Security DV RSA CA 24 | Deutsche Telekom Security GmbH | 2034-11-25 | Valid |
| Telekom Security OV RSA CA 24 | Deutsche Telekom Security GmbH | 2034-11-25 | Valid |
| Telekom Security EV RSA CA 23 | Deutsche Telekom Security GmbH | 2033-03-27 | Valid |
| Telekom Security OV RSA qCA 25 | Deutsche Telekom Security GmbH | 2035-07-07 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as Telekom Security TLS RSA Root 2023 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Telekom Security TLS RSA Root 2023, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| T-TeleSec GlobalRoot Class 3 crt.sh | Deutsche Telekom Security GmbH | 2033-09-30 | Valid |
CRL and OCSP addresses
In the root certificate
Telekom Security TLS RSA Root 2023 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://tstlsrr23.crl.telesec.de/rl/Telekom_Security_TLS_RSA_Root_2023.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 7 valid intermediates signed by Telekom Security TLS RSA Root 2023; the number in brackets is how many of them use each address.
- CRL:
http://tstlsrr23.crl.telesec.de/rl/Telekom_Security_TLS_RSA_Root_2023.crl(7) - OCSP:
http://tstlsrr23.ocsp.telesec.de/ocspr(7)
What happens when it expires
Telekom Security TLS RSA Root 2023 is valid until 2048-03-27, about 21.4 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-08-30.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up Telekom Security TLS RSA Root 2023 by common name (Telekom Security TLS RSA Root 2023) 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: Not included)
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 "Telekom Security TLS RSA Root 2023" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: EFC65CADBB59ADB6EFE84DA22311B35624B71B3B1EA0DA8B6655174EC8978646Windows (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 54D3ACB3BD5756F6859DCEE5C321E2D4AD83D093Linux (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 "Telekom Security TLS RSA Root 2023"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Telekom Security TLS RSA Root 2023"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 "EF:C6:5C:AD:BB:59:AD:B6:EF:E8:4D:A2:23:11:B3:56:24:B7:1B:3B:1E:A0:DA:8B:66:55:17:4E:C8:97:86:46"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 Deutsche Telekom Security GmbH → Telekom Security TLS RSA Root 2023.
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 telekom-security-tls-rsa-root-2023.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=EF:C6:5C:AD:BB:59:AD:B6:EF:E8:4D:A2:23:11:B3:56:24:B7:1B:3B:1E:A0:DA:8B:66:55:17:4E:C8:97:86:46FAQ
Is Telekom Security TLS RSA Root 2023 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Chrome, Mozilla, Microsoft trust it for TLS server authentication; Apple do not. Distrust-after dates already set: Chrome 2027-08-30.
When does Telekom Security TLS RSA Root 2023 expire?
On 2048-03-27, about 21.4 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Telekom Security TLS RSA Root 2023 issued?
The CCADB lists 8: 7 valid, 0 expired and 1 revoked. The newest valid one is Telekom Security OV RSA CA 26A, valid until 2029-03-18.
Is Telekom Security TLS RSA Root 2023 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by T-TeleSec GlobalRoot Class 3; 1 of them are still valid.
Other roots from Deutsche Telekom Security
- T-TeleSec GlobalRoot Class 2 RSA 2048 · 2033-10-01
- T-TeleSec GlobalRoot Class 3 RSA 2048 · 2033-10-01
- Telekom Security TLS ECC Root 2020 ECDSA P-384 · 2045-08-25
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