Root certificate · KLID (Korea)

MOIS SSL Root CA

MOIS SSL Root CA is a root CA certificate operated by KLID (Korea) (RSA 4096, valid until 2043-02-22, SHA-256 1CF341AE). 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 MOIS SSL 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

"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: Government of Korea, KLID
Subject: CN=MOIS SSL Root CA,O=Ministry of the Interior and Safety,C=KR
SHA-256: 1CF341AE35341AC3AE1DC68D5B10DC0C9DC1307656F75FD92CA2C68489D52E9A
SHA-1 (Windows thumbprint): 65F9901C549C9BEC6BF422B7FD8EE382F626186B
SPKI SHA-256: 2BBD5357548A6F4BB963DC1E0F9AF986C6528EF951FA2213123CDCE64823C921
Valid from: 2023-02-22
Expires: 2043-02-22
Key: RSA 4096
Signature algorithm: sha256WithRSAEncryption
Serial number: 449EFC3EB1A24235A08C1DD3B7062C1167488F2
Country: KR
Trust bits (CCADB): Server Authentication, Client Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://ssl-valid.gpki.go.kr · expired: https://ssl-expired.gpki.go.kr · revoked: https://ssl-revoked.gpki.go.kr
CCADB record: A010935
PEM: klid-mois-ssl-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 MOIS SSL 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
MOIS SSL Server CA	Government of Korea, KLID	2033-02-23	Valid

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

MOIS SSL 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://ssl.gpki.go.kr/crl/ca/Crl001p1Dp1.crl

Used by the intermediates it issued

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

CRL: http://ssl.gpki.go.kr/arl/SSL-RootCA.crl (1)
OCSP: http://ocsp-rca-ssl.gpki.go.kr (1)

What happens when it expires

MOIS SSL Root CA is valid until 2043-02-22, about 16.3 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 MOIS SSL Root CA by common name (MOIS SSL 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 "MOIS SSL Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 1CF341AE35341AC3AE1DC68D5B10DC0C9DC1307656F75FD92CA2C68489D52E9A

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 65F9901C549C9BEC6BF422B7FD8EE382F626186B

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 "MOIS SSL Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "MOIS SSL 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 "1C:F3:41:AE:35:34:1A:C3:AE:1D:C6:8D:5B:10:DC:0C:9D:C1:30:76:56:F7:5F:D9:2C:A2:C6:84:89:D5:2E:9A"

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 Ministry of the Interior and Safety → MOIS SSL 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 klid-mois-ssl-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=1C:F3:41:AE:35:34:1A:C3:AE:1D:C6:8D:5B:10:DC:0C:9D:C1:30:76:56:F7:5F:D9:2C:A2:C6:84:89:D5:2E:9A

FAQ

Is MOIS SSL 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 MOIS SSL Root CA expire?

On 2043-02-22, about 16.3 years after the 2026-11-10 data snapshot.

How many intermediate certificates has MOIS SSL Root CA issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is MOIS SSL Server CA, valid until 2033-02-23.

Is MOIS SSL Root CA cross-signed?

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

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