Root certificate · OATI

OATI webCARES Server Root CA

OATI webCARES Server Root CA is a root CA certificate operated by OATI (RSA 4096, valid until 2045-12-08, SHA-256 30F4E5DD). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

Root store status

Root store	Status	Trusted for TLS	Distrust for TLS after	Constrained
Chrome	Not included Not included	No	—	No
Mozilla	Not included Not included	No	—	No
Apple	Not included Not included	No	—	No
Microsoft	Included Included	Yes	—	No

The CCADB lists no EV policy OID for OATI webCARES Server Root CA.

Not included Chrome

Status: Not included

Not included Mozilla

Status: Not included

Not included Apple

Status: Not included

Included Microsoft

Status: Included
Trusted EKUs: Server Authentication

"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: Open Access Technology International, Inc. (OATI)
Subject: CN=OATI webCARES Server Root CA,O=Open Access Technology International Inc,C=US
SHA-256: 30F4E5DD679FDE8FD11EB6E0C531615C438B06EDD9F59CBAB49680AA2B6990D9
SHA-1 (Windows thumbprint): 5B2907750936AA256E6D702E3AF86585450154E1
SPKI SHA-256: 9DE4650DC1B56452D868B27FBEA1596515CFEB79C15B54FB16D2A4A8C7836982
Valid from: 2025-12-08
Expires: 2045-12-08
Key: RSA 4096
Signature algorithm: sha512WithRSAEncryption
Serial number: 66539C052C681A97499298D88DEAFA44
Country: US
Trust bits (CCADB): Server Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://valid2026.oaticerts.com/ · expired: https://expired2026.oaticerts.com/ · revoked: https://revoked2026.oaticerts.com/
CCADB record: A012887
PEM: oati-webcares-server-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 1 intermediate CA certificates signed directly by OATI webCARES Server Root CA: 1 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 1 of 1: 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
OATI webCARES Server Issuing CA 2026	Open Access Technology International, Inc. (OATI)	2031-12-08	Valid

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

OATI webCARES Server Root 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://certs.oaticerts.com/repository/OATIWebCaresServerRoot.crl

Used by the intermediates it issued

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

CRL: http://certs.oati.net/repository/OATIWebCaresServerRoot.crl (1)
CRL: http://certs.oaticerts.com/repository/OATIWebCaresServerRoot.crl (1)

None of the valid intermediates under this root lists an OCSP responder.

What happens when it expires

OATI webCARES Server Root CA is valid until 2045-12-08, about 19.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 OATI webCARES Server Root CA by common name (OATI webCARES Server Root 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: 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 "OATI webCARES Server Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 30F4E5DD679FDE8FD11EB6E0C531615C438B06EDD9F59CBAB49680AA2B6990D9

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 5B2907750936AA256E6D702E3AF86585450154E1

Linux (ca-certificates follows Mozilla: Not included)

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 "OATI webCARES Server Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "OATI webCARES Server Root 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 "30:F4:E5:DD:67:9F:DE:8F:D1:1E:B6:E0:C5:31:61:5C:43:8B:06:ED:D9:F5:9C:BA:B4:96:80:AA:2B:69:90:D9"

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 Open Access Technology International Inc → OATI webCARES Server Root 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 oati-webcares-server-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=30:F4:E5:DD:67:9F:DE:8F:D1:1E:B6:E0:C5:31:61:5C:43:8B:06:ED:D9:F5:9C:BA:B4:96:80:AA:2B:69:90:D9

FAQ

Is OATI webCARES Server Root CA trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does OATI webCARES Server Root CA expire?

On 2045-12-08, about 19.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has OATI webCARES Server Root CA issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is OATI webCARES Server Issuing CA 2026, valid until 2031-12-08.

Is OATI webCARES Server Root CA cross-signed?

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

Other roots from OATI

OATI WebCARES Root CA RSA 4096 · 2038-06-03

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