Root certificate · CFCA
CFCA EV ROOT
CFCA EV ROOT is a root CA certificate operated by CFCA (RSA 4096, valid until 2029-12-31, SHA-256 5CC3D78E). 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 | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | Yes |
| Microsoft | Included Included | Yes | — | Yes |
Mozilla treats it as an EV root for policy OID 2.16.156.112554.3.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.16.156.112554.3
- First included in
- NSS 3.18 / Firefox 38
- Inclusion bug
- #926029
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
- Allowed policies
- Server Authentication, Client Authentication, Code Signing, Timestamp Signing
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, OCSP Signing, Secure Email, Time Stamping
- Not-before cutoff
- 2026-05-19 (Code Signing, Encrypting File System, IP Security End System, IP Security Tunnel Termination, IP Security User, Secure Email)
- Disallowed EKUs
- OCSP Signing
"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
- China Financial Certification Authority (CFCA)
- Subject
- CN=CFCA EV ROOT,O=China Financial Certification Authority,C=CN
- SHA-256
5CC3D78E4E1D5E45547A04E6873E64F90CF9536D1CCC2EF800F355C4C5FD70FD- SHA-1 (Windows thumbprint)
E2B8294B5584AB6B58C290466CAC3FB8398F8483- SPKI SHA-256
DD5ED1C090F9F448061BAA94A6BB11017544E9EEFAA20CC714CE6C633F5DC629- Valid from
- 2012-08-08
- Expires
- 2029-12-31
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
184ACCD6- Country
- CN
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Time Stamping
- EV policy OIDs (CCADB)
- 2.16.156.112554.3, 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://www.anxinsign.com/Web/login· expired:https://exp.cebnet.com.cn/· revoked:https://rev.cebnet.com.cn/ - CCADB record
- A000295
- PEM
- cfca-ev-root.pem
Intermediate CAs issued by this root
The CCADB lists 11 intermediate CA certificates signed directly by CFCA EV ROOT: 6 currently valid, 0 expired and 5 revoked (revoked includes those whose parent was revoked).
Showing 11 of 11: 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 |
|---|---|---|---|
| CFCA Global RSA ROOT G2 | China Financial Certification Authority (CFCA) | 2029-10-12 | Valid |
| CFCA Global RSA ROOT G2 | China Financial Certification Authority (CFCA) | 2029-08-25 | Valid |
| CFCA TLS EV OCA | China Financial Certification Authority (CFCA) | 2029-12-30 | Valid |
| CFCA TLS OV OCA | China Financial Certification Authority (CFCA) | 2029-12-30 | Valid |
| CFCA OV OCA | China Financial Certification Authority (CFCA) | 2029-12-25 | Valid |
| CFCA EV OCA | China Financial Certification Authority (CFCA) | 2029-12-29 | Valid |
| CFCA Global RSA ROOT G2 | China Financial Certification Authority (CFCA) | 2029-12-30 | Revoked |
| CFCA DV OCA | China Financial Certification Authority (CFCA) | 2029-12-26 | Revoked |
| CFCA DV OCA | China Financial Certification Authority (CFCA) | 2029-12-25 | Revoked |
| CFCA EV CodeSign OCA | China Financial Certification Authority (CFCA) | 2029-12-24 | Revoked |
| CFCA OV CodeSign OCA | China Financial Certification Authority (CFCA) | 2029-12-25 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as CFCA EV ROOT with a different issuer, so a client has to carry CFCA EV ROOT itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
CFCA EV ROOT 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.cfca.com.cn/evrca/RSA/allCRL.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 6 valid intermediates signed by CFCA EV ROOT; the number in brackets is how many of them use each address.
- CRL:
http://crl.cfca.com.cn/evrca/RSA/allCRL.crl(4) - CRL:
http://crl.cfca.com.cn/evrca/RSA/crl1.crl(2) - OCSP:
http://ocsp.cfca.com.cn/ocsp(6)
What happens when it expires
CFCA EV ROOT is valid until 2029-12-31, about 3.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.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up CFCA EV ROOT by common name (CFCA EV ROOT) 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 "CFCA EV ROOT" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 5CC3D78E4E1D5E45547A04E6873E64F90CF9536D1CCC2EF800F355C4C5FD70FD
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 E2B8294B5584AB6B58C290466CAC3FB8398F8483
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 "CFCA EV ROOT"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "CFCA EV ROOT"
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 "5C:C3:D7:8E:4E:1D:5E:45:54:7A:04:E6:87:3E:64:F9:0C:F9:53:6D:1C:CC:2E:F8:00:F3:55:C4:C5:FD:70:FD"
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 China Financial Certification Authority → CFCA EV ROOT.
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 cfca-ev-root.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=5C:C3:D7:8E:4E:1D:5E:45:54:7A:04:E6:87:3E:64:F9:0C:F9:53:6D:1C:CC:2E:F8:00:F3:55:C4:C5:FD:70:FD
FAQ
Is CFCA EV ROOT 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.
When does CFCA EV ROOT expire?
On 2029-12-31, about 3.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has CFCA EV ROOT issued?
The CCADB lists 11: 6 valid, 0 expired and 5 revoked. The newest valid one is CFCA Global RSA ROOT G2, valid until 2029-10-12.
Is CFCA EV ROOT cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
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