Root certificate · TrustAsia
TrustAsia TLS ECC Root CA
TrustAsia TLS ECC Root CA is a root CA certificate operated by TrustAsia (ECDSA P-384, valid until 2044-05-15, SHA-256 C0076B9E). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Chrome, Mozilla.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Not included Not included | No | — | No |
| Microsoft | Not included Not included | No | — | 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 ECC Root CA,O=TrustAsia Technologies\, Inc.,C=CN
- SHA-256
C0076B9EF0531FB1A656D67C4EBE97CD5DBAA41EF44598ACC2489878C92D8711- SHA-1 (Windows thumbprint)
B5EC39F3A16637AEC3059457E2BE11BEB7A17F36- SPKI SHA-256
F4632E58701C0BD7DAFC7E3831355EC433FC13777DE286683E8EC50964DF0452- Valid from
- 2024-05-15
- Expires
- 2044-05-15
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
3674E14D7C6513C9AC835525A03E527E2F5068C7- 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-ecctls-valid.trustasia.com· expired:https://ev-ecctls-expired.trustasia.com· revoked:https://ev-ecctls-revoked.trustasia.com - CCADB record
- A011889
- PEM
- trustasia-tls-ecc-root-ca.pem
Intermediate CAs issued by this root
The CCADB lists 17 intermediate CA certificates signed directly by TrustAsia TLS ECC 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.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| AutoCert TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-09-18 | Valid |
| iTrust TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-09-18 | Valid |
| Unicom TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-04-28 | Valid |
| DNSPod DV TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-04-28 | Valid |
| DNSPod TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-04-28 | Valid |
| Unicom DV TLS ECC CA 2026 | TrustAsia Technologies, Inc. | 2029-04-28 | Valid |
| LiteSSL Pro ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| XinNet EV TLS ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| 宝塔 TLS ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| LiteSSL ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| XinNet OV TLS ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| XinNet DV TLS ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| 宝塔 DV TLS ECC CA 2025 | TrustAsia Technologies, Inc. | 2030-10-21 | Valid |
| TrustAsia EV TLS ECC CA 2024 V2 | TrustAsia Technologies, Inc. | 2034-07-18 | Valid |
| TrustAsia DV TLS ECC CA 2024 | TrustAsia Technologies, Inc. | 2034-05-15 | Valid |
| TrustAsia OV TLS ECC CA 2024 | TrustAsia Technologies, Inc. | 2034-05-15 | Valid |
| TrustAsia EV TLS ECC CA 2024 | TrustAsia Technologies, Inc. | 2034-05-15 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as TrustAsia TLS ECC 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 ECC Root CA, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Certum Trusted Network CA crt.sh | Asseco Data Systems S.A. | 2029-01-14 | Valid |
CRL and OCSP addresses
In the root certificate
TrustAsia TLS ECC 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/TrustAsiaTLSECCRootCA.crlhttp://crl.litessl.com/TrustAsiaTLSECCRootCA.crlhttp://crl-pro.litessl.com/TrustAsiaTLSECCRootCA.crlhttp://crl.oem.trustca.net/TrustAsiaTLSECCRootCA.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 ECC Root CA; the number in brackets is how many of them use each address.
- CRL:
http://crl.oem.trustca.net/TrustAsiaTLSECCRootCA.crl(11) - CRL:
http://crl.wt.trustasia.com/TrustAsiaTLSECCRootCA.crl(3) - CRL:
http://crl-pro.litessl.com/TrustAsiaTLSECCRootCA.crl(1) - CRL:
http://crl.litessl.com/TrustAsiaTLSECCRootCA.crl(1) - OCSP:
http://ocsp.oem.trustca.net/TrustAsiaTLSECCRootCA(11) - OCSP:
http://ocsp.wt.trustasia.com/TrustAsiaTLSECCRootCA(3) - OCSP:
http://ocsp-pro.litessl.com/TrustAsiaTLSECCRootCA(1)
What happens when it expires
TrustAsia TLS ECC 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 ECC Root CA by common name (TrustAsia TLS ECC 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 ECC Root CA" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: C0076B9EF0531FB1A656D67C4EBE97CD5DBAA41EF44598ACC2489878C92D8711
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 B5EC39F3A16637AEC3059457E2BE11BEB7A17F36
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 ECC 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 ECC 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 "C0:07:6B:9E:F0:53:1F:B1:A6:56:D6:7C:4E:BE:97:CD:5D:BA:A4:1E:F4:45:98:AC:C2:48:98:78:C9:2D:87:11"
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 ECC 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.
# 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-ecc-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=C0:07:6B:9E:F0:53:1F:B1:A6:56:D6:7C:4E:BE:97:CD:5D:BA:A4:1E:F4:45:98:AC:C2:48:98:78:C9:2D:87:11
FAQ
Is TrustAsia TLS ECC 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 ECC 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 ECC Root CA issued?
The CCADB lists 17: 16 valid, 0 expired and 1 revoked. The newest valid one is AutoCert TLS ECC CA 2026, valid until 2029-09-18.
Is TrustAsia TLS ECC 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
- TrustAsia Global Root CA G3 RSA 4096 · 2046-05-19
- TrustAsia Global Root CA G4 ECDSA P-384 · 2046-05-19
- TrustAsia TLS RSA Root CA RSA 4096 · 2044-05-15
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