中文

Root certificate · Telia Company

Telia RSA TLS Root CA v3

Telia RSA TLS Root CA v3 is a root CA certificate operated by Telia Company (RSA 4096, valid until 2048-05-23, SHA-256 D13DB129). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Mozilla, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaIncluded IncludedYes—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists no EV policy OID for Telia RSA TLS Root CA v3.

Not included Chrome

Status
Not included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
not EV-enabled
First included in
3.126 / 154
Inclusion bug
#1968852

Not included Apple

Status
Not included

Included Microsoft

Status
Included
Trusted EKUs
Server 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
Telia Company
Subject
CN=Telia RSA TLS Root CA v3,O=Telia Company AB,C=SE
SHA-256
D13DB1294C45EBC6FC86C6BBF69FA29BDFE692DFF7C713C243C7A956C6A2284C
SHA-1 (Windows thumbprint)
B52E884E40C111FB50C7E24FAC182BBD6815D234
SPKI SHA-256
536CFDAE8A6257BF14266C43285958D0F9B937E3068E2A215374170133A9FFCC
Valid from
2023-11-15
Expires
2048-05-23
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
18BD250AB42552C475ABDA1DC1AC5
Country
SE
Trust bits (CCADB)
Server Authentication
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://teliarsatlsrootcav3-valid-2.chain.trust.telia.com · expired: https://teliarsatlsrootcav3-expired-2.chain.trust.telia.com · revoked: https://teliarsatlsrootcav3-revoked-2.chain.trust.telia.com
CCADB record
A012103
PEM
telia-rsa-tls-root-ca-v3.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 3 intermediate CA certificates signed directly by Telia RSA TLS Root CA v3: 3 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 3 of 3: 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
Telia CA EC QWAC R1 Telia Company2048-05-22Valid
Telia RSA OV CA v4 Telia Company2048-05-23Valid
Telia RSA DV CA v4 Telia Company2048-05-23Valid

Cross-signed versions

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

Signed byCA ownerExpiresStatus
Telia Root CA v2 crt.sh Telia Company2043-11-28Valid
Telia Root CA v2 crt.sh Telia Company2043-11-28Revoked

CRL and OCSP addresses

In the root certificate

Telia RSA TLS Root CA v3 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://httpcrl.trust.telia.com/teliarsatlsrootcav3.crl

Used by the intermediates it issued

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

  • CRL: http://httpcrl.trust.telia.com/teliarsatlsrootcav3.crl (3)
  • OCSP: http://ocsp.trust.telia.com (3)

What happens when it expires

Telia RSA TLS Root CA v3 is valid until 2048-05-23, about 21.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 Telia RSA TLS Root CA v3 by common name (Telia RSA TLS Root CA v3) 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 "Telia RSA TLS Root CA v3" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: D13DB1294C45EBC6FC86C6BBF69FA29BDFE692DFF7C713C243C7A956C6A2284C

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 B52E884E40C111FB50C7E24FAC182BBD6815D234

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

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 "D1:3D:B1:29:4C:45:EB:C6:FC:86:C6:BB:F6:9F:A2:9B:DF:E6:92:DF:F7:C7:13:C2:43:C7:A9:56:C6:A2:28:4C"

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 Telia Company AB → Telia RSA TLS Root CA v3.

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 telia-rsa-tls-root-ca-v3.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=D1:3D:B1:29:4C:45:EB:C6:FC:86:C6:BB:F6:9F:A2:9B:DF:E6:92:DF:F7:C7:13:C2:43:C7:A9:56:C6:A2:28:4C

FAQ

Is Telia RSA TLS Root CA v3 trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Mozilla, Microsoft trust it for TLS server authentication; Chrome, Apple do not.

When does Telia RSA TLS Root CA v3 expire?

On 2048-05-23, about 21.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Telia RSA TLS Root CA v3 issued?

The CCADB lists 3: 3 valid, 0 expired and 0 revoked. The newest valid one is Telia CA EC QWAC R1, valid until 2048-05-22.

Is Telia RSA TLS Root CA v3 cross-signed?

Yes. The CCADB has 2 cross-certificate(s) with its subject and key, signed by Telia Root CA v2; 1 of them are still valid.

Other roots from Telia Company

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