Root certificate · OISTE

OISTE WISeKey Global Root GC CA

OISTE WISeKey Global Root GC CA is a root CA certificate operated by OISTE (ECDSA P-384, valid until 2042-05-09, SHA-256 8560F91C). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2026-09-30Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-09-30 (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
2026-09-30

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
not EV-enabled
First included in
NSS 3.39 / Firefox 63
Inclusion bug
#1403591

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, Secure Email, Time Stamping
Not-before cutoff
2026-09-15 (Code Signing, Document Signing, Encrypting File System, 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
OISTE
Subject
CN=OISTE WISeKey Global Root GC CA,OU=OISTE Foundation Endorsed,O=WISeKey,C=CH
SHA-256
8560F91C3624DABA9570B5FEA0DBE36FF11A8323BE9486854FB3F34A5571198D
SHA-1 (Windows thumbprint)
E011845E34DEBE8881B99CF61626D1961FC3B931
SPKI SHA-256
FD371BEA9755FF60C8828C849B8E5215DE532D61B009855FA0AD630D90EEF82E
Valid from
2017-05-09
Expires
2042-05-09
Key
ECDSA P-384
Signature algorithm
ecdsa-with-SHA384
Serial number
212A560CAEDA0CAB4045BF2BA22D3AEA
Country
CH
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://gcevvalidssl.hightrusted.com/ · expired: https://gcevexpiredssl.hightrusted.com/ · revoked: https://gcevrevokedssl.hightrusted.com/
CCADB record
A004779
PEM
oiste-wisekey-global-root-gc-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 2 intermediate CA certificates signed directly by OISTE WISeKey Global Root GC CA: 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.

IntermediateOperated byExpiresStatus
WISeKey CertifyID SSL GC CA 1 WISeKey2039-02-16Valid
WISeKey CertifyID Advanced GC CA 1 WISeKey2042-05-09Revoked

Cross-signed versions

No certificate in the CCADB has the same subject and public key as OISTE WISeKey Global Root GC CA with a different issuer, so a client has to carry OISTE WISeKey Global Root GC CA itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

OISTE WISeKey Global Root GC 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://public.wisekey.com/crl/owgrgcca.crl

Used by the intermediates it issued

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

  • CRL: http://public.wisekey.com/crl/owgrgc.crl (1)
  • OCSP: http://ocsp.wisekey.com (1)

What happens when it expires

OISTE WISeKey Global Root GC CA is valid until 2042-05-09, about 15.5 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 2026-09-30.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up OISTE WISeKey Global Root GC CA by common name (OISTE WISeKey Global Root GC 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: 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 "OISTE WISeKey Global Root GC CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 8560F91C3624DABA9570B5FEA0DBE36FF11A8323BE9486854FB3F34A5571198D

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 E011845E34DEBE8881B99CF61626D1961FC3B931

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 "OISTE WISeKey Global Root GC CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "OISTE WISeKey Global Root GC 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 "85:60:F9:1C:36:24:DA:BA:95:70:B5:FE:A0:DB:E3:6F:F1:1A:83:23:BE:94:86:85:4F:B3:F3:4A:55:71:19:8D"

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 WISeKey → OISTE WISeKey Global Root GC 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 oiste-wisekey-global-root-gc-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=85:60:F9:1C:36:24:DA:BA:95:70:B5:FE:A0:DB:E3:6F:F1:1A:83:23:BE:94:86:85:4F:B3:F3:4A:55:71:19:8D

FAQ

Is OISTE WISeKey Global Root GC CA 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 2026-09-30.

When does OISTE WISeKey Global Root GC CA expire?

On 2042-05-09, about 15.5 years after the 2026-11-10 data snapshot.

How many intermediate certificates has OISTE WISeKey Global Root GC CA issued?

The CCADB lists 2: 1 valid, 0 expired and 1 revoked. The newest valid one is WISeKey CertifyID SSL GC CA 1, valid until 2039-02-16.

Is OISTE WISeKey Global Root GC CA cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

Other roots from OISTE

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