# HiPKI Root CA - G1 root certificate (Chunghwa Telecom)

> 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.

Source: https://ssl.sh/roots/chunghwa-telecom-hipki-root-ca-g1/
Last updated: 2026-11-10

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.

| Field | Value |
|---|---|
| CA owner | Chunghwa Telecom |
| Subject | CN=HiPKI Root CA - G1,O=Chunghwa Telecom Co.\, Ltd.,C=TW |
| SHA-256 | F015CE3CC239BFEF064BE9F1D2C417E1A0264A0A94BE1F0C8D121864EB6949CC |
| SPKI SHA-256 | 79CAAF5347E6E4A94C8E78A98496FC74020F809EDE13F220FAB6104C8DED329F |
| Valid from | 2019-02-22 |
| Expires | 2037-12-31 |
| Key | RSA 4096 |
| Signature algorithm | sha256WithRSAEncryption |
| Serial number | 2DDDACCE629794A143E8B0CD766A5E60 |
| SHA-1 (Windows thumbprint) | 6A92E4A8EE1BEC964537E3295749CD96E3E5D260 |

## Root store status

| Root store | Status | Trusted for TLS | Distrust for TLS after | Details |
|---|---|---|---|---|
| Chrome | Included | Yes | 2025-07-31 | - |
| Mozilla | Included | Yes | - | Trust bits: Websites; EV policy OIDs: not EV-enabled; First included in: NSS 3.74 / Firefox 97; Inclusion bug: #1563417 |
| Apple | Included | Yes | - | Trust bits: serverAuth, clientAuth |
| Microsoft | Included | Yes | - | Trusted EKUs: Server Authentication, Client Authentication |

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.

## 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).

| Intermediate | Operated by | Expires | Status | SHA-256 |
|---|---|---|---|---|
| HiPKI OV TLS CA - G1 | Chunghwa Telecom | 2037-12-31 | Valid | D34A5B981A85CA075DB62CBAC415EF659D95339040CA476868625D4AA23A9849 |
| HiPKI EV TLS CA - G1 | Chunghwa Telecom | 2037-12-31 | Revoked | 2A8E6A86E74D10EDB2026C81693D64957A0F081C1631912AC95EFDFCB5625657 |

## 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 | SHA-256 |
|---|---|---|---|---|
| ePKI Root Certification Authority | Chunghwa Telecom | 2034-12-19 | Revoked | 6807C97235C5EC6090269A4B5FEDFAB46986E42F4D67D2EDDDCF6E45CF0DFA80 |

## 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.

## FAQ

**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.

Sources: CCADB TLS Server Authentication report, All Included Root Certificate Trust Bit Settings, All Certificate Information (V5), the per-store TLS reports and Mozilla's Included CA Certificate Report (ccadb.org/resources).