Root certificate · NAVER Cloud Trust Services

NAVER Global Root Certification Authority

NAVER Global Root Certification Authority is a root CA certificate operated by NAVER Cloud Trust Services (RSA 4096, valid until 2037-08-18, SHA-256 88F438DC). 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 IncludedYes—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists no EV policy OID for NAVER Global Root Certification Authority.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
not EV-enabled
First included in
NSS 3.60 / Firefox 85
Inclusion bug
#1404221

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Document Signing, 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
NAVER Cloud Trust Services
Subject
CN=NAVER Global Root Certification Authority,O=NAVER BUSINESS PLATFORM Corp.,C=KR
SHA-256
88F438DCF8FFD1FA8F429115FFE5F82AE1E06E0C70C375FAAD717B34A49E7265
SHA-1 (Windows thumbprint)
8F6BF2A9274ADA14A0C4F48E6127F9C01E785DD1
SPKI SHA-256
786FFA578618C3B9A311175E50816F4DDA0605C3869F296EBC5943BF09F4E904
Valid from
2017-08-18
Expires
2037-08-18
Key
RSA 4096
Signature algorithm
sha384WithRSAEncryption
Serial number
194301EA20BDDF5C5332AB1434471F8D6504D0D
Country
KR
Trust bits (CCADB)
Server Authentication, Client Authentication, Document Signing, Secure Email
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://test-certificate.naver.com/ · expired: https://test2-certificate.naver.com/ · revoked: https://test1-certificate.naver.com/
CCADB record
A006186
PEM
naver-cloud-trust-naver-global-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 8 intermediate CA certificates signed directly by NAVER Global Root Certification Authority: 3 currently valid, 0 expired and 5 revoked (revoked includes those whose parent was revoked).

Showing 8 of 8: 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
NAVER Cloud Trust Services RSA Root G1 → NAVER Cloud Trust Services RSA Root G1 NAVER Cloud Trust Services2036-05-13Valid
NAVER Secure Certification Authority 3 NAVER Cloud Trust Services2029-09-13Valid
NAVER Cloud Trust Services ECC Root G1 → NAVER Cloud Trust Services ECC Root G1 NAVER Cloud Trust Services2036-06-04Valid
NAVER Cloud Trust Services RSA Root G1 → NAVER Cloud Trust Services RSA Root G1 NAVER Cloud Trust Services2036-06-04Revoked
NAVER Secure Certification Authority 2 NAVER Cloud Trust Services2035-11-19Revoked
NAVER Cloud Trust Services RSA Root G1 → NAVER Cloud Trust Services RSA Root G1 NAVER Cloud Trust Services2038-12-09Revoked
NAVER Cloud Trust Services ECC Root G1 → NAVER Cloud Trust Services ECC Root G1 NAVER Cloud Trust Services2038-12-09Revoked
NAVER Secure Certification Authority 1 NAVER Cloud Trust Services2027-08-18Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

NAVER Global Root Certification Authority 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://rca.navercorp.com/arl/Arl.crl
  • http://rca.navercorp.com/arl/Arl1Dp1.crl

Used by the intermediates it issued

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

  • CRL: http://rca.navercorp.com/arl/Arl.crl (3)
  • OCSP: http://ocsp-rca.navercorp.com/ocsp (3)

What happens when it expires

NAVER Global Root Certification Authority is valid until 2037-08-18, about 10.8 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 NAVER Global Root Certification Authority by common name (NAVER Global Root Certification Authority) 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 "NAVER Global Root Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 88F438DCF8FFD1FA8F429115FFE5F82AE1E06E0C70C375FAAD717B34A49E7265

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 8F6BF2A9274ADA14A0C4F48E6127F9C01E785DD1

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 "NAVER Global Root Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "NAVER Global Root Certification Authority"

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 "88:F4:38:DC:F8:FF:D1:FA:8F:42:91:15:FF:E5:F8:2A:E1:E0:6E:0C:70:C3:75:FA:AD:71:7B:34:A4:9E:72:65"

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 NAVER BUSINESS PLATFORM Corp. → NAVER Global Root Certification Authority.

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 naver-cloud-trust-naver-global-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=88:F4:38:DC:F8:FF:D1:FA:8F:42:91:15:FF:E5:F8:2A:E1:E0:6E:0C:70:C3:75:FA:AD:71:7B:34:A4:9E:72:65

FAQ

Is NAVER Global Root Certification Authority 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.

When does NAVER Global Root Certification Authority expire?

On 2037-08-18, about 10.8 years after the 2026-11-10 data snapshot.

How many intermediate certificates has NAVER Global Root Certification Authority issued?

The CCADB lists 8: 3 valid, 0 expired and 5 revoked. The newest valid one is NAVER Cloud Trust Services RSA Root G1, valid until 2036-05-13.

Is NAVER Global Root Certification Authority cross-signed?

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

Other roots from NAVER Cloud Trust Services

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