Root certificate · TrustAsia

TrustAsia TLS RSA Root CA

TrustAsia TLS RSA Root CA is a root CA certificate operated by TrustAsia (RSA 4096, valid until 2044-05-15, SHA-256 06C08D7D). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Chrome, Mozilla.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes—No
MozillaIncluded IncludedYes—No
AppleNot included Not includedNo—No
MicrosoftNot included Not includedNo—No

Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.23.140.1.1
First included in
3.114 / 142

Not included Apple

Status
Not included

Not included Microsoft

Status
Not included

"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
TrustAsia Technologies, Inc.
Subject
CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN
SHA-256
06C08D7DAFD876971EB1124FE67F847EC0C7A158D3EA53CBE940E2EA9791F4C3
SHA-1 (Windows thumbprint)
A54650C562EA959A1AA7046F1758C729533D03FA
SPKI SHA-256
5628872E245FE66148B80BADEAC9C40F6252E642FA9595AECE4B3E8A58B8FD46
Valid from
2024-05-15
Expires
2044-05-15
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
1C18D8CFE5533F2235465354243C6C47D15C4A9C
Country
CN
Trust bits (CCADB)
Server Authentication
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://ev-rsatls-valid.trustasia.com · expired: https://ev-rsatls-expired.trustasia.com · revoked: https://ev-rsatls-revoked.trustasia.com
CCADB record
A011888
PEM
trustasia-tls-rsa-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

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

Showing 17 of 17: 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
iTrust TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-09-18Valid
AutoCert TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-09-18Valid
DNSPod TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-04-28Valid
Unicom TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-04-28Valid
Unicom DV TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-04-28Valid
DNSPod DV TLS RSA CA 2026 TrustAsia Technologies, Inc.2029-04-28Valid
宝塔 DV TLS RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
LiteSSL RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
宝塔 TLS RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
XinNet EV TLS RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
XinNet DV TLS RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
XinNet OV TLS RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
LiteSSL Pro RSA CA 2025 TrustAsia Technologies, Inc.2030-10-21Valid
TrustAsia EV TLS RSA CA 2024 V2 TrustAsia Technologies, Inc.2034-07-18Valid
TrustAsia OV TLS RSA CA 2024 TrustAsia Technologies, Inc.2034-05-15Valid
TrustAsia DV TLS RSA CA 2024 TrustAsia Technologies, Inc.2034-05-15Valid
TrustAsia EV TLS RSA CA 2024 TrustAsia Technologies, Inc.2034-05-15Revoked

Cross-signed versions

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

Signed byCA ownerExpiresStatus
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2029-01-14Valid

CRL and OCSP addresses

In the root certificate

TrustAsia TLS RSA Root CA 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.wt.trustasia.com/TrustAsiaTLSRSARootCA.crl
  • http://crl.litessl.com/TrustAsiaTLSRSARootCA.crl
  • http://crl-pro.litessl.com/TrustAsiaTLSRSARootCA.crl
  • http://crl.oem.trustca.net/TrustAsiaTLSRSARootCA.crl

Used by the intermediates it issued

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

  • CRL: http://crl.oem.trustca.net/TrustAsiaTLSRSARootCA.crl (11)
  • CRL: http://crl.wt.trustasia.com/TrustAsiaTLSRSARootCA.crl (3)
  • CRL: http://crl-pro.litessl.com/TrustAsiaTLSRSARootCA.crl (1)
  • CRL: http://crl.litessl.com/TrustAsiaTLSRSARootCA.crl (1)
  • OCSP: http://ocsp.oem.trustca.net/TrustAsiaTLSRSARootCA (11)
  • OCSP: http://ocsp.wt.trustasia.com/TrustAsiaTLSRSARootCA (3)
  • OCSP: http://ocsp-pro.litessl.com/TrustAsiaTLSRSARootCA (1)

What happens when it expires

TrustAsia TLS RSA Root CA is valid until 2044-05-15, about 17.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 TrustAsia TLS RSA Root CA by common name (TrustAsia TLS RSA Root CA) 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 "TrustAsia TLS RSA Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 06C08D7DAFD876971EB1124FE67F847EC0C7A158D3EA53CBE940E2EA9791F4C3

Windows (Microsoft store: Not included)

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 A54650C562EA959A1AA7046F1758C729533D03FA

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

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 "06:C0:8D:7D:AF:D8:76:97:1E:B1:12:4F:E6:7F:84:7E:C0:C7:A1:58:D3:EA:53:CB:E9:40:E2:EA:97:91:F4:C3"

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 TrustAsia Technologies, Inc. → TrustAsia TLS RSA Root CA.

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 trustasia-tls-rsa-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=06:C0:8D:7D:AF:D8:76:97:1E:B1:12:4F:E6:7F:84:7E:C0:C7:A1:58:D3:EA:53:CB:E9:40:E2:EA:97:91:F4:C3

FAQ

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

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

When does TrustAsia TLS RSA Root CA expire?

On 2044-05-15, about 17.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has TrustAsia TLS RSA Root CA issued?

The CCADB lists 17: 16 valid, 0 expired and 1 revoked. The newest valid one is iTrust TLS RSA CA 2026, valid until 2029-09-18.

Is TrustAsia TLS RSA Root CA cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Certum Trusted Network CA; 1 of them are still valid.

Other roots from TrustAsia

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