Root certificate · Chunghwa Telecom
HiPKI Root CA - G1
HiPKI Root CA - G1 is a root CA certificate operated by Chunghwa Telecom (RSA 4096, valid until 2037-12-31, SHA-256 F015CE3C). 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 | 2025-07-31 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2025-07-31 (sct_not_after). The CCADB lists EV policy OID 2.23.140.1.1 for this root, but Mozilla does not mark it as EV-enabled.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2025-07-31
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.74 / Firefox 97
- Inclusion bug
- #1563417
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client 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
- Chunghwa Telecom
- Subject
- CN=HiPKI Root CA - G1,O=Chunghwa Telecom Co.\, Ltd.,C=TW
- SHA-256
F015CE3CC239BFEF064BE9F1D2C417E1A0264A0A94BE1F0C8D121864EB6949CC- SHA-1 (Windows thumbprint)
6A92E4A8EE1BEC964537E3295749CD96E3E5D260- SPKI SHA-256
79CAAF5347E6E4A94C8E78A98496FC74020F809EDE13F220FAB6104C8DED329F- Valid from
- 2019-02-22
- Expires
- 2037-12-31
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
2DDDACCE629794A143E8B0CD766A5E60- Country
- TW
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://good.hipkig1ov.hinet.net· expired:https://expired.hipkig1ov.hinet.net· revoked:https://revoked.hipkig1ov.hinet.net - CCADB record
- A006477
- PEM
- chunghwa-telecom-hipki-root-ca-g1.pem
Intermediate CAs issued by this root
The CCADB lists 2 intermediate CA certificates signed directly by HiPKI Root CA - G1: 1 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 2 of 2: 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 |
|---|---|---|---|
| HiPKI OV TLS CA - G1 | Chunghwa Telecom | 2037-12-31 | Valid |
| HiPKI EV TLS CA - G1 | Chunghwa Telecom | 2037-12-31 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as HiPKI Root CA - G1 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not HiPKI Root CA - G1, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| ePKI Root Certification Authority crt.sh | Chunghwa Telecom | 2034-12-19 | Revoked |
CRL and OCSP addresses
In the root certificate
HiPKI Root CA - G1 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://eca.hinet.net/repository/HRCA_G1/CA.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 1 valid intermediates signed by HiPKI Root CA - G1; the number in brackets is how many of them use each address.
- CRL:
http://eca.hinet.net/repository/HRCA_G1/CA.crl(1) - OCSP:
http://ocsp.eca.hinet.net/HRCA/ocsp(1)
What happens when it expires
HiPKI Root CA - G1 is valid until 2037-12-31, about 11.1 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 2025-07-31.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up HiPKI Root CA - G1 by common name (HiPKI Root CA - G1) 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 "HiPKI Root CA - G1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: F015CE3CC239BFEF064BE9F1D2C417E1A0264A0A94BE1F0C8D121864EB6949CCWindows (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 6A92E4A8EE1BEC964537E3295749CD96E3E5D260Linux (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 "HiPKI Root CA - G1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "HiPKI Root CA - G1"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 "F0:15:CE:3C:C2:39:BF:EF:06:4B:E9:F1:D2:C4:17:E1:A0:26:4A:0A:94:BE:1F:0C:8D:12:18:64:EB:69:49:CC"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 Chunghwa Telecom Co., Ltd. → HiPKI Root CA - G1.
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 chunghwa-telecom-hipki-root-ca-g1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=F0:15:CE:3C:C2:39:BF:EF:06:4B:E9:F1:D2:C4:17:E1:A0:26:4A:0A:94:BE:1F:0C:8D:12:18:64:EB:69:49:CCFAQ
Is HiPKI Root CA - G1 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 2025-07-31.
When does HiPKI Root CA - G1 expire?
On 2037-12-31, about 11.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has HiPKI Root CA - G1 issued?
The CCADB lists 2: 1 valid, 0 expired and 1 revoked. The newest valid one is HiPKI OV TLS CA - G1, valid until 2037-12-31.
Is HiPKI Root CA - G1 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by ePKI Root Certification Authority; 0 of them are still valid.
Other roots from Chunghwa Telecom
- ePKI Root Certification Authority RSA 4096 · 2034-12-20
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