中文

Root certificate · TWCA

TWCA CYBER Root CA

TWCA CYBER Root CA is a root CA certificate operated by TWCA (RSA 4096, valid until 2047-11-22, SHA-256 3F63BB28). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Mozilla, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes—No
MozillaIncluded IncludedYes—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—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
NSS 3.104 / Firefox 131

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
Taiwan-CA Inc. (TWCA)
Subject
CN=TWCA CYBER Root CA,OU=Root CA,O=TAIWAN-CA,C=TW
SHA-256
3F63BB2814BE174EC8B6439CF08D6D56F0B7C405883A5648A334424D6B3EC558
SHA-1 (Windows thumbprint)
F6B11C1A8338E97BDBB3A8C83324E02D9C7F2666
SPKI SHA-256
06600B94C0318BB6967F0C7787CC8A1032A179C4E95E3C5760B32E290F7FEC9B
Valid from
2022-11-22
Expires
2047-11-22
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
4001348CC200000000000000013CF2C6
Country
TW
Trust bits (CCADB)
Server Authentication
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://cyberevnormal.twca.com.tw/ · expired: https://cyberevexpired.twca.com.tw/ · revoked: https://cyberevrevoked.twca.com.tw/
CCADB record
A010825
PEM
twca-cyber-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 5 intermediate CA certificates signed directly by TWCA CYBER Root CA: 1 currently valid, 0 expired and 4 revoked (revoked includes those whose parent was revoked).

Showing 5 of 5: 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
TWCA CYBER Root CA G3 Taiwan-CA Inc. (TWCA)2036-10-31Valid
TWCA EVSSL Certification Authority Taiwan-CA Inc. (TWCA)2034-09-06Revoked
TWCA SSL Certification Authority Taiwan-CA Inc. (TWCA)2034-09-06Revoked
TWCA EVSSL Certification Authority Taiwan-CA Inc. (TWCA)2033-02-23Revoked
TWCA SSL Certification Authority Taiwan-CA Inc. (TWCA)2033-02-23Revoked

Cross-signed versions

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

Signed byCA ownerExpiresStatus
TWCA Global Root CA crt.sh Taiwan-CA Inc. (TWCA)2030-11-01Valid
TWCA Global Root CA crt.sh Taiwan-CA Inc. (TWCA)2030-12-09Revoked

CRL and OCSP addresses

In the root certificate

TWCA CYBER 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://RootCA.twca.com.tw/TWCARCA/cyber_root_revoke_2022.crl

Used by the intermediates it issued

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

  • CRL: http://RootCA.twca.com.tw/TWCARCA/cyber_root_revoke_2022.crl (1)
  • OCSP: http://rootocsp.twca.com.tw/ (1)

What happens when it expires

TWCA CYBER Root CA is valid until 2047-11-22, about 21.0 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 TWCA CYBER Root CA by common name (TWCA CYBER 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 "TWCA CYBER Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 3F63BB2814BE174EC8B6439CF08D6D56F0B7C405883A5648A334424D6B3EC558

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 F6B11C1A8338E97BDBB3A8C83324E02D9C7F2666

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 "TWCA CYBER Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "TWCA CYBER 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 "3F:63:BB:28:14:BE:17:4E:C8:B6:43:9C:F0:8D:6D:56:F0:B7:C4:05:88:3A:56:48:A3:34:42:4D:6B:3E:C5:58"

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 TAIWAN-CA → TWCA CYBER 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 twca-cyber-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=3F:63:BB:28:14:BE:17:4E:C8:B6:43:9C:F0:8D:6D:56:F0:B7:C4:05:88:3A:56:48:A3:34:42:4D:6B:3E:C5:58

FAQ

Is TWCA CYBER Root CA trusted by Chrome, Firefox, Safari and Windows?

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

When does TWCA CYBER Root CA expire?

On 2047-11-22, about 21.0 years after the 2026-11-10 data snapshot.

How many intermediate certificates has TWCA CYBER Root CA issued?

The CCADB lists 5: 1 valid, 0 expired and 4 revoked. The newest valid one is TWCA CYBER Root CA G3, valid until 2036-10-31.

Is TWCA CYBER Root CA cross-signed?

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

Other roots from TWCA

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