Certificate authority
NAVER Cloud Trust Services
NAVER Cloud Trust Services operates 3 root certificate(s) trusted for TLS by at least one major root store (CCADB owner: NAVER Cloud Trust Services; country: KR). See fingerprints, expiry and Chrome, Mozilla, Apple and Microsoft status.
Details
- CCADB CA owner
- NAVER Cloud Trust Services
- Country
- KR
- Country (CCADB)
- Republic of Korea (South Korea)
- Roots
- 3
- Roots trusted for TLS
- Chrome 1 · Mozilla 1 · Apple 1 · Microsoft 3
- Intermediates under its roots
- 20 (7 valid)
- Auditor
- KPMG
- CAA
navercloudtrust.com
CAA records
The CCADB lists 1 CAA issuer domain(s) recognized by the currently valid intermediate certificates of NAVER Cloud Trust Services. One issue record with any of them lets NAVER Cloud Trust Services issue for your domain. Domains that contain the CA's name come first, the rest by how many valid intermediates recognize them.
Copy-ready record(s) for the first 1 domain(s):
example.com. CAA 0 issue "navercloudtrust.com"| Domain | Valid intermediates |
|---|---|
navercloudtrust.com | 7 |
For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator
Root certificates (CCADB)
NAVER Cloud Trust Services has 3 root certificate(s) in the CCADB TLS report. Together they have signed 20 intermediate CA certificates, 7 of them still valid.
Roots this CA owner has in the CCADB TLS Server Authentication report, with current status in each root store.
- trusted for TLS
- included with limits (NotBefore / no TLS bit)
- removed or blocked
- not included
| Root certificate | Key | Expires | Ch | Mo | Ap | MS | Intermediates |
|---|---|---|---|---|---|---|---|
| NAVER Cloud Trust Services ECC Root G1 | ECDSA P-384 | 2043-06-06 | Not included | Not included | Not included | Included | 6 (2) |
| NAVER Cloud Trust Services RSA Root G1 | RSA 4096 | 2043-06-06 | Not included | Not included | Not included | Included | 6 (2) |
| NAVER Global Root Certification Authority | RSA 4096 | 2037-08-18 | Included | Included | Included | Included | 8 (3) |
Audits
Audit data the CCADB records for the TLS roots of NAVER Cloud Trust Services. Auditor(s): KPMG. The most recent audit period ended on 2025-09-30.
| Audit | Scheme | Period | Statement | Report |
|---|---|---|---|---|
| Standard audit | WebTrust | 2024-10-01 – 2025-09-30 | 2025-11-21 | cpacanada.ca |
| Network security | WebTrust | 2024-10-01 – 2025-09-30 | 2025-11-21 | cpacanada.ca |
| TLS Baseline Requirements | WebTrust | 2024-10-01 – 2025-09-30 | 2025-11-21 | cpacanada.ca |
CP/CPS documents
Certificate Policy and Certification Practice Statement links that NAVER Cloud Trust Services has disclosed in the CCADB for its TLS roots, with effective dates:
- CP/CPS: https://ssl.pstatic.net/static/rootca/CPS/NAVER_Cloud_Trust_Services_CPS_v1.1.3.pdf (effective 2026-10-23)
- Markdown CP/CPS: https://github.com/NaverCloudTrustServices/PolicyDocument/blob/423a4e812e28361039db0645ecc812ab04147f07/docs/cpcps_1.1.3.md (effective 2026-10-23)
- Document repository: https://pki.navercloudtrust.com/
Report a certificate problem
To report a mis-issued certificate, a compromised private key or other abuse, use the channels NAVER Cloud Trust Services lists in the CCADB (replace [at] and [dot] in addresses):
dl_rootca[at]navercorp[dot]com
Incident reports
CAs in Mozilla's root program file compliance incident reports in Mozilla's Bugzilla (product CA Program, component CA Certificate Compliance). This search lists the bugs whose title contains the words “NAVER Cloud Trust”:
ACME directories (CCADB)
DV ACME directory URLs that NAVER Cloud Trust Services has disclosed in the CCADB for its valid certificates:
https://acme.navercloudtrust.com/acme/directory
FAQ
What CAA record allows NAVER Cloud Trust Services to issue certificates?
Publish example.com. CAA 0 issue "navercloudtrust.com". The CCADB lists 1 recognized domain(s) for NAVER Cloud Trust Services: navercloudtrust.com.
Who audits NAVER Cloud Trust Services?
KPMG, according to the CCADB. The latest TLS Baseline Requirements audit (WebTrust) covers 2024-10-01 to 2025-09-30; the statement is dated 2025-11-21.
How do I report a problem certificate to NAVER Cloud Trust Services?
Use the channel(s) listed in the CCADB: dl_rootca[at]navercorp[dot]com.
How many root certificates does NAVER Cloud Trust Services have?
3 in the CCADB TLS report. Trusted for TLS: Chrome 1, Mozilla 1, Apple 1, Microsoft 3. They have signed 20 intermediates, 7 of them still valid.