Root certificate · OISTE

OISTE WISeKey Global Root GB CA

OISTE WISeKey Global Root GB CA is a root CA certificate operated by OISTE (RSA 2048, valid until 2039-12-01, SHA-256 6B9C08E8). 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). Mozilla treats it as an EV root for policy OID 2.16.756.5.14.7.4.8.

Included Chrome

Status
Included
Distrust for TLS after
2026-09-30

Included Mozilla

Status
Included
Trust bits
Websites, Email
EV policy OIDs
2.16.756.5.14.7.4.8
First included in
NSS 3.21 / Firefox 44
Inclusion bug
#1172819

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
Not-before cutoff
2019-10-01 (Code 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
OISTE
Subject
CN=OISTE WISeKey Global Root GB CA,OU=OISTE Foundation Endorsed,O=WISeKey,C=CH
SHA-256
6B9C08E86EB0F767CFAD65CD98B62149E5494A67F5845E7BD1ED019F27B86BD6
SHA-1 (Windows thumbprint)
0FF9407618D3D76A4B98F0A8359E0CFD27ACCCED
SPKI SHA-256
149F2EE63B9A5E5803240A770DC991FC2E3445E62831C245A49BC4F1F738FF9C
Valid from
2014-12-01
Expires
2039-12-01
Key
RSA 2048
Signature algorithm
sha256WithRSAEncryption
Serial number
76B1205274F0858746B3F8231AF6C2C0
Country
CH
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email, Time Stamping
EV policy OIDs (CCADB)
2.16.756.5.14.7.4.8, 2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://gbevvalidssl.hightrusted.com/ · expired: https://gbevexpiredssl.hightrusted.com/ · revoked: https://gbevrevokedssl.hightrusted.com/
CCADB record
A000780
PEM
oiste-wisekey-global-root-gb-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 15 intermediate CA certificates signed directly by OISTE WISeKey Global Root GB CA: 9 currently valid, 2 expired and 4 revoked (revoked includes those whose parent was revoked).

Showing 15 of 15: 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
OISTE Server Root ECC G1 → OISTE Server Root ECC G1 OISTE2039-12-01Valid
OISTE Client Root RSA G1 OISTE2039-12-01Valid
OISTE Client Root ECC G1 OISTE2039-12-01Valid
OISTE Server Root RSA G1 → OISTE Server Root RSA G1 OISTE2039-12-01Valid
TuringSign RSA Secure CA 2 OISTE2030-05-26Valid
TuringSign ECC Secure CA 2 OISTE2030-05-26Valid
WISeKey CertifyID Personal GB CA 3 WISeKey2039-12-01Valid
WISeKey CertifyID SSL GB CA 2 WISeKey2035-07-04Valid
WISeKey CertifyID Personal GB CA 4 WISeKey2035-07-04Valid
TuringSign ECC Secure CA WISeKey2026-06-21Expired
TuringSign RSA Secure CA WISeKey2026-06-21Expired
WISeKey CertifyID Personal GB CA 1 WISeKey2039-12-01Revoked
WISeKey CertifyID Personal GB CA 2 WISeKey2039-12-01Revoked
WISeKey CertifyID SSL GB CA 1 WISeKey2039-12-01Revoked
WISeKey CertifyID Policy GB CA 1 WISeKey2039-12-01Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

OISTE WISeKey Global Root GB 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/owgrgbca.crl

Used by the intermediates it issued

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

  • CRL: http://public.wisekey.com/crl/owgrgbca.crl (9)
  • OCSP: http://ocsp.wisekey.com/ (3)
  • OCSP: http://ocsp.wisekey.com (2)

What happens when it expires

OISTE WISeKey Global Root GB CA is valid until 2039-12-01, about 13.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 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 GB CA by common name (OISTE WISeKey Global Root GB 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 GB CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 6B9C08E86EB0F767CFAD65CD98B62149E5494A67F5845E7BD1ED019F27B86BD6

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 0FF9407618D3D76A4B98F0A8359E0CFD27ACCCED

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 GB 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 GB 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 "6B:9C:08:E8:6E:B0:F7:67:CF:AD:65:CD:98:B6:21:49:E5:49:4A:67:F5:84:5E:7B:D1:ED:01:9F:27:B8:6B:D6"

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 GB 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-gb-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=6B:9C:08:E8:6E:B0:F7:67:CF:AD:65:CD:98:B6:21:49:E5:49:4A:67:F5:84:5E:7B:D1:ED:01:9F:27:B8:6B:D6

FAQ

Is OISTE WISeKey Global Root GB 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 GB CA expire?

On 2039-12-01, about 13.1 years after the 2026-11-10 data snapshot.

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

The CCADB lists 15: 9 valid, 2 expired and 4 revoked. The newest valid one is OISTE Server Root ECC G1, valid until 2039-12-01.

Is OISTE WISeKey Global Root GB 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