Root certificate · Deutsche Telekom Security
T-TeleSec GlobalRoot Class 3
T-TeleSec GlobalRoot Class 3 is a root CA certificate operated by Deutsche Telekom Security (RSA 2048, valid until 2033-10-01, SHA-256 FD73DAD3). 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 | 2026-05-28 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | Yes |
| Microsoft | Included Included | Yes | — | Yes |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-05-28 (sct_not_after). Mozilla treats it as an EV root for policy OID 1.3.6.1.4.1.7879.13.24.1.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2026-05-28
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 1.3.6.1.4.1.7879.13.24.1
- First included in
- NSS 3.14 / Firefox 18
- Inclusion bug
- #669849
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
- Allowed policies
- Server Authentication, Client Authentication, Code Signing, Timestamp Signing
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, OCSP Signing, Secure Email
- Not-before cutoff
- 2025-09-15 (OCSP Signing, Secure Email)
- Disallowed EKUs
- 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
- Deutsche Telekom Security GmbH
- Subject
- CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE
- SHA-256
FD73DAD31C644FF1B43BEF0CCDDA96710B9CD9875ECA7E31707AF3E96D522BBD- SHA-1 (Windows thumbprint)
55A6723ECBF2ECCDC3237470199D2ABE11E381D1- SPKI SHA-256
8D767764B3CBDA08929D072A22A561F4DCDD1BC57D3CBDDC948C47D2B47F9122- Valid from
- 2008-10-01
- Expires
- 2033-10-01
- Key
- RSA 2048
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
1- Country
- DE
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- 1.3.6.1.4.1.7879.13.24.1, 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://root-class3.test.telesec.de/· expired:https://root-class3-expired.test.telesec.de/· revoked:https://root-class3-revoked.test.telesec.de/ - CCADB record
- A000221
- PEM
- telekom-security-t-telesec-globalroot-class-3.pem
Intermediate CAs issued by this root
The CCADB lists 9 intermediate CA certificates signed directly by T-TeleSec GlobalRoot Class 3: 4 currently valid, 2 expired and 3 revoked (revoked includes those whose parent was revoked).
Showing 9 of 9: 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 TLS RSA Root 2023 → Telekom Security TLS RSA Root 2023 | Deutsche Telekom Security GmbH | 2033-09-30 | Valid |
| Telekom Security TLS ECC Root 2020 → Telekom Security TLS ECC Root 2020 | Deutsche Telekom Security GmbH | 2033-09-30 | Valid |
| Telekom Security EV RSA CA 23A | Deutsche Telekom Security GmbH | 2033-06-19 | Valid |
| Telekom Security ServerID EV Class 3 CA | Deutsche Telekom Security GmbH | 2027-08-02 | Valid |
| TeleSec ServerPass Extended Validation Class 3 CA | Deutsche Telekom Security GmbH | 2024-02-11 | Expired |
| T-TeleSec Extended Validation SSL CA Class 3 | Deutsche Telekom Security GmbH | 2018-10-01 | Expired |
| Telekom Security EV RSA CA 22 | Deutsche Telekom Security GmbH | 2032-06-21 | Revoked |
| TeleSec GlobalRoot Class 3 G2 | Deutsche Telekom Security GmbH | 2029-02-12 | Revoked |
| TeleSec GlobalRoot Class 3 G2 | Deutsche Telekom Security GmbH | 2026-02-23 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as T-TeleSec GlobalRoot Class 3 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not T-TeleSec GlobalRoot Class 3, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Deutsche Telekom Root CA 2 crt.sh | Deutsche Telekom Security GmbH | 2018-10-01 | Expired |
CRL and OCSP addresses
In the root certificate
T-TeleSec GlobalRoot Class 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://pki.telesec.de/rl/GlobalRoot_Class_3.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 4 valid intermediates signed by T-TeleSec GlobalRoot Class 3; the number in brackets is how many of them use each address.
- CRL:
http://grcl3.crl.telesec.de/rl/T-TeleSec_GlobalRoot_Class_3.crl(4) - OCSP:
http://grcl3.ocsp.telesec.de/ocspr(2)
What happens when it expires
T-TeleSec GlobalRoot Class 3 is valid until 2033-10-01, about 6.9 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 2026-05-28.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up T-TeleSec GlobalRoot Class 3 by common name (T-TeleSec GlobalRoot Class 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 "T-TeleSec GlobalRoot Class 3" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: FD73DAD31C644FF1B43BEF0CCDDA96710B9CD9875ECA7E31707AF3E96D522BBD
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 55A6723ECBF2ECCDC3237470199D2ABE11E381D1
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 "T-TeleSec GlobalRoot Class 3"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "T-TeleSec GlobalRoot Class 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 "FD:73:DA:D3:1C:64:4F:F1:B4:3B:EF:0C:CD:DA:96:71:0B:9C:D9:87:5E:CA:7E:31:70:7A:F3:E9:6D:52:2B:BD"
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 T-Systems Enterprise Services GmbH → T-TeleSec GlobalRoot Class 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.
# 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-t-telesec-globalroot-class-3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=FD:73:DA:D3:1C:64:4F:F1:B4:3B:EF:0C:CD:DA:96:71:0B:9C:D9:87:5E:CA:7E:31:70:7A:F3:E9:6D:52:2B:BD
FAQ
Is T-TeleSec GlobalRoot Class 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 2026-05-28.
When does T-TeleSec GlobalRoot Class 3 expire?
On 2033-10-01, about 6.9 years after the 2026-11-10 data snapshot.
How many intermediate certificates has T-TeleSec GlobalRoot Class 3 issued?
The CCADB lists 9: 4 valid, 2 expired and 3 revoked. The newest valid one is Telekom Security TLS RSA Root 2023, valid until 2033-09-30.
Is T-TeleSec GlobalRoot Class 3 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Deutsche Telekom Root CA 2; 0 of them are still valid.
Other roots from Deutsche Telekom Security
- T-TeleSec GlobalRoot Class 2 RSA 2048 · 2033-10-01
- Telekom Security TLS ECC Root 2020 ECDSA P-384 · 2045-08-25
- Telekom Security TLS RSA Root 2023 RSA 4096 · 2048-03-27
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