中文

Root certificate · OATI

OATI WebCARES Root CA

OATI WebCARES Root CA is a root CA certificate operated by OATI (RSA 4096, valid until 2038-06-03, SHA-256 7A77C6C6). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists no EV policy OID for OATI WebCARES 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, Client Authentication, Secure Email
Not-before cutoff
2026-05-19 (Secure Email)

"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 Root CA,O=Open Access Technology International Inc,L=Minneapolis,ST=MN,C=US
SHA-256
7A77C6C61EEEB9AA65C4EA410D65D895B26A81123283009DB104B48DE80B2479
SHA-1 (Windows thumbprint)
4B6BD2D3884E46C80CE2B962BC598CD9D5D84013
SPKI SHA-256
8E15D426CD04898F218BE2E5FE3784F375094CC435DC61AD86C4A3C01511DBE1
Valid from
2008-06-03
Expires
2038-06-03
Key
RSA 4096
Signature algorithm
sha1WithRSAEncryption
Serial number
25762066A7560874F9004BFA1C82841
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://valid2021.oaticerts.com · expired: https://expired2021.oaticerts.com · revoked: https://revoked2021.oaticerts.com
CCADB record
A002435
PEM
oati-webcares-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 5 intermediate CA certificates signed directly by OATI WebCARES Root CA: 3 currently valid, 2 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 5 of 5: 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
webCARES Client Issuing CA 2025 Open Access Technology International, Inc. (OATI)2030-10-09Valid
webCARES Server Issuing CA 2025 Open Access Technology International, Inc. (OATI)2030-10-09Valid
webCARES Issuing CA 2021 Open Access Technology International, Inc. (OATI)2027-03-25Valid
webCARES Issuing CA 2017 Open Access Technology International, Inc. (OATI)2023-08-07Expired
webCARES Issuing CA 2013 Open Access Technology International, Inc. (OATI)2019-10-28Expired

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

  • CRL: http://certs.oaticerts.com/repository/OATICA2.crl
  • CRL: http://certs.oati.net/repository/OATICA2.crl

Full CRL this CA publishes (CCADB)

  • http://certs.oaticerts.com/repository/OATIIA2021.crl

Used by the intermediates it issued

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

  • CRL: http://certs.oati.net/repository/OATICA2.crl (3)
  • CRL: http://certs.oaticerts.com/repository/OATICA2.crl (3)
  • OCSP: http://ocsp.oaticerts.com/ocsp (3)

What happens when it expires

OATI WebCARES Root CA is valid until 2038-06-03, about 11.6 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 Root CA by common name (OATI WebCARES 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 Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 7A77C6C61EEEB9AA65C4EA410D65D895B26A81123283009DB104B48DE80B2479

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 4B6BD2D3884E46C80CE2B962BC598CD9D5D84013

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 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 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 "7A:77:C6:C6:1E:EE:B9:AA:65:C4:EA:41:0D:65:D8:95:B2:6A:81:12:32:83:00:9D:B1:04:B4:8D:E8:0B:24:79"

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 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-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=7A:77:C6:C6:1E:EE:B9:AA:65:C4:EA:41:0D:65:D8:95:B2:6A:81:12:32:83:00:9D:B1:04:B4:8D:E8:0B:24:79

FAQ

Is OATI WebCARES 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 Root CA expire?

On 2038-06-03, about 11.6 years after the 2026-11-10 data snapshot.

How many intermediate certificates has OATI WebCARES Root CA issued?

The CCADB lists 5: 3 valid, 2 expired and 0 revoked. The newest valid one is webCARES Client Issuing CA 2025, valid until 2030-10-09.

Is OATI WebCARES 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

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