Certificate authority
HALCOM d.d.
HALCOM d.d. operates 1 root certificate(s) trusted for TLS by at least one major root store (CCADB owner: HALCOM d.d.; country: SI). See fingerprints, expiry and Chrome, Mozilla, Apple and Microsoft status.
Details
- CCADB CA owner
- HALCOM d.d.
- Country
- SI
- Country (CCADB)
- Slovenia
- Roots
- 1
- Roots trusted for TLS
- Chrome 0 · Mozilla 0 · Apple 0 · Microsoft 1
- Intermediates under its roots
- 10 (8 valid)
- Auditor
- Bureau Veritas d.o.o.
CAA records
The CCADB lists no recognized CAA domain for the valid intermediates of HALCOM d.d.. Section 4.2 of a CA's CP/CPS has to state the issuer domain names it accepts in CAA records, so check that document.
For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator
Root certificates (CCADB)
HALCOM d.d. has 1 root certificate(s) in the CCADB TLS report. Together they have signed 10 intermediate CA certificates, 8 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 |
|---|---|---|---|---|---|---|---|
| Halcom Root Certificate Authority | RSA 2048 | 2036-06-10 | Not included | Not included | Not included | Included | 10 (8) |
Audits
Audit data the CCADB records for the TLS roots of HALCOM d.d.. Auditor(s): Bureau Veritas d.o.o.. The most recent audit period ended on 2026-05-31.
| Audit | Scheme | Period | Statement | Report |
|---|---|---|---|---|
| Standard audit | ETSI EN 319 411 | 2025-06-01 – 2026-05-31 | 2026-06-12 | bureauveritas.si |
| TLS Baseline Requirements | ETSI EN 319 411 | 2025-06-01 – 2026-05-31 | 2026-06-12 | bureauveritas.si |
CP/CPS documents
Certificate Policy and Certification Practice Statement links that HALCOM d.d. has disclosed in the CCADB for its TLS roots, with effective dates:
- CPS: https://static.halcom.com/si/CPS_halcom_ca.pdf (effective 2026-06-15)
- Document repository: https://www.halcom.si/repository
Report a certificate problem
The CCADB lists no problem-reporting address for HALCOM d.d.. The Baseline Requirements put these instructions in section 1.5.2 of the CA's CPS.
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 “HALCOM”:
FAQ
What CAA record allows HALCOM d.d. to issue certificates?
The CCADB lists no recognized CAA domain for HALCOM d.d.; check section 4.2 of its CP/CPS.
Who audits HALCOM d.d.?
Bureau Veritas d.o.o., according to the CCADB. The latest TLS Baseline Requirements audit (ETSI EN 319 411) covers 2025-06-01 to 2026-05-31; the statement is dated 2026-06-12.
How many root certificates does HALCOM d.d. have?
1 in the CCADB TLS report. Trusted for TLS: Chrome 0, Mozilla 0, Apple 0, Microsoft 1. They have signed 10 intermediates, 8 of them still valid.
Where are the incident reports for HALCOM d.d.?
In Mozilla's Bugzilla, product CA Program, component CA Certificate Compliance. Search for bug titles containing “HALCOM”; CAs title their reports with their own name.