Root certificate · SHECA

UCA Global G2 Root

UCA Global G2 Root is a root CA certificate operated by SHECA (RSA 4096, valid until 2040-12-31, SHA-256 9BEA11C9). 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

The CCADB lists no EV policy OID for UCA Global G2 Root.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
not EV-enabled
First included in
NSS 3.41 / Firefox 65
Inclusion bug
#1309797

Not included Apple

Status
Not included

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping

"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
Shanghai Electronic Certification Authority Co., Ltd.
Subject
CN=UCA Global G2 Root,O=UniTrust,C=CN
SHA-256
9BEA11C976FE014764C1BE56A6F914B5A560317ABD9988393382E5161AA0493C
SHA-1 (Windows thumbprint)
28F97816197AFF182518AA44FEC1A0CE5CB64C8A
SPKI SHA-256
1255CABE8152FA64DF942F7A47417E29F96C1CE11BF8C84ECBE2815CC1280810
Valid from
2016-03-11
Expires
2040-12-31
Key
RSA 4096
Signature algorithm
sha256WithRSAEncryption
Serial number
5DDFB1DA5AA3ED5DBE5A6520650390EF
Country
CN
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Time Stamping
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://rsaovg5.good.sheca.com/ · expired: https://rsaovg5.expired.sheca.com/ · revoked: https://rsaovg5.revoked.sheca.com/
CCADB record
A003654
PEM
sheca-uca-global-g2-root.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 71 intermediate CA certificates signed directly by UCA Global G2 Root: 54 currently valid, 0 expired and 17 revoked (revoked includes those whose parent was revoked).

Showing 20 of 71: 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
HUAWEI DV TLS RSA CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
CHINA UNICOM OV TLS RSA CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
CHINA UNICOM OV TLS ECC CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
HUAWEI DV TLS ECC CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
HUAWEI OV TLS ECC CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
CHINA UNICOM DV TLS ECC CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
CHINA UNICOM DV TLS RSA CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
HUAWEI OV TLS RSA CA 2026 Shanghai Electronic Certification Authority Co., Ltd.2029-04-22Valid
UniTrust Global TLS ECC Root CA R2 Shanghai Electronic Certification Authority Co., Ltd.2029-02-04Valid
SanFront DV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2030-11-11Valid
SanFront OV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2030-11-11Valid
SanFront OV TLS RSA CA G1 Shanghai Electronic Certification Authority Co., Ltd.2030-09-17Valid
SanFront DV TLS RSA CA G1 Shanghai Electronic Certification Authority Co., Ltd.2030-09-17Valid
SNCA OV TLS RSA CA G1 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
SHECA OV TLS RSA CA A1 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
Xinnet OV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
Xinnet DV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
SHECA DV TLS RSA CA A1 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
CT2 DV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid
CT2 OV TLS RSA CA G2 Shanghai Electronic Certification Authority Co., Ltd.2035-04-27Valid

Cross-signed versions

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

Signed byCA ownerExpiresStatus
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2029-01-06Valid
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2029-01-06Valid
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2025-02-21Revoked
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2025-02-21Expired

CRL and OCSP addresses

In the root certificate

UCA Global G2 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.global.sheca.com/root/globalg2.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 54 valid intermediates signed by UCA Global G2 Root; the number in brackets is how many of them use each address.

  • CRL: http://crl.global.sheca.com/root/grcag2.crl (34)
  • CRL: http://crl.global.sheca.com/root/globalg2.crl (20)
  • OCSP: http://ocsp.global.sheca.com/grcag2 (34)
  • OCSP: http://ocsp.global.sheca.com/globalg2 (20)

What happens when it expires

UCA Global G2 Root is valid until 2040-12-31, about 14.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 UCA Global G2 Root by common name (UCA Global G2 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: 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 "UCA Global G2 Root" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 9BEA11C976FE014764C1BE56A6F914B5A560317ABD9988393382E5161AA0493C

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 28F97816197AFF182518AA44FEC1A0CE5CB64C8A

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 "UCA Global G2 Root"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "UCA Global G2 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 "9B:EA:11:C9:76:FE:01:47:64:C1:BE:56:A6:F9:14:B5:A5:60:31:7A:BD:99:88:39:33:82:E5:16:1A:A0:49:3C"

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 UniTrust → UCA Global G2 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.

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 sheca-uca-global-g2-root.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=9B:EA:11:C9:76:FE:01:47:64:C1:BE:56:A6:F9:14:B5:A5:60:31:7A:BD:99:88:39:33:82:E5:16:1A:A0:49:3C

FAQ

Is UCA Global G2 Root 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 UCA Global G2 Root expire?

On 2040-12-31, about 14.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has UCA Global G2 Root issued?

The CCADB lists 71: 54 valid, 0 expired and 17 revoked. The newest valid one is HUAWEI DV TLS RSA CA 2026, valid until 2029-04-22.

Is UCA Global G2 Root cross-signed?

Yes. The CCADB has 4 cross-certificate(s) with its subject and key, signed by Certum Trusted Network CA; 2 of them are still valid.

Other roots from SHECA

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