# Halcom Root Certificate Authority root certificate (HALCOM d.d.)

> Halcom Root Certificate Authority is a root CA certificate operated by HALCOM d.d. (RSA 2048, valid until 2036-06-10, SHA-256 D7BA3F4F). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Source: https://ssl.sh/roots/halcom-root-ca/
Last updated: 2026-11-10

Halcom Root Certificate Authority is a root CA certificate operated by HALCOM d.d. (RSA 2048, valid until 2036-06-10, SHA-256 D7BA3F4F). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

| Field | Value |
|---|---|
| CA owner | HALCOM d.d. |
| Subject | CN=Halcom Root Certificate Authority,2.5.4.97=VATSI-43353126,O=Halcom d.d.,C=SI |
| SHA-256 | D7BA3F4FF8AD05633451470DDA3378A3491B90005E5C687D2B68D53647CFDD66 |
| SPKI SHA-256 | 5899D913EAD119B9CDB7BA2F30EFE0DF68AD2CD225BDF493E8323A25AA4DBE23 |
| Valid from | 2016-06-10 |
| Expires | 2036-06-10 |
| Key | RSA 2048 |
| Signature algorithm | sha256WithRSAEncryption |
| Serial number | CDF9B |
| SHA-1 (Windows thumbprint) | 23D731FEDC5C8BB97DE6DC8E13B411BD4F24004F |

## Root store status

| Root store | Status | Trusted for TLS | Distrust for TLS after | Details |
|---|---|---|---|---|
| Chrome | Not included | No | - | - |
| Mozilla | Not included | No | - | - |
| Apple | Not included | No | - | - |
| Microsoft | Included | Yes | - | Trusted EKUs: Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, Secure Email, Time Stamping; Not-before cutoff: 2026-05-19 (Code Signing, Secure Email) |

The CCADB lists no EV policy OID for Halcom Root Certificate Authority.

## Intermediate CAs issued by this root

The CCADB lists 10 intermediate CA certificates signed directly by Halcom Root Certificate Authority: 8 currently valid, 2 expired and 0 revoked (revoked includes those whose parent was revoked).

| Intermediate | Operated by | Expires | Status | SHA-256 |
|---|---|---|---|---|
| Halcom CA web 2 | HALCOM d.d. | 2035-03-25 | Valid | CF4334AA7269188407450C4DB00FF3B1F93A6F151077E55A4BD8896F2DCFB0CD |
| Halcom CA TSA 2 | HALCOM d.d. | 2035-03-25 | Valid | 436CC754D2E76055AE3E0FBD1EE180CFA6433E5D56E92D3BE99EE7BC8CC09D61 |
| Halcom CA FO e-signature 2 | HALCOM d.d. | 2033-04-03 | Valid | B2FDA13F819007E924A5FF453FB4A450C2D3451FDB432CED4ABD34532D4477C2 |
| Halcom CA PO e-seal 2 | HALCOM d.d. | 2033-04-03 | Valid | 5AE7385644A83ED2E18C66ECB80993EA17941CCE26D1ED6285DF83CB35BA24BA |
| Halcom CA PO e-signature 2 | HALCOM d.d. | 2033-04-03 | Valid | 4436A54D37BF9934B2FF7AAF235B77D95BAA0839BA7E5FFE9640EFC6655860CF |
| Halcom CA web 1 | Halcom D.D. | 2027-04-22 | Valid | D12DF63569F0F814514C2E29C93A9A133A4CBAA92D3046F8C6BC2D9D6F66F087 |
| Halcom CA TSA 1 | Halcom D.D. | 2027-04-22 | Valid | A2FE481DBD77689629828DA50957B55B0D2CC4960601B3CB04E60C1DC3BC246C |
| Halcom CA PO e-seal 1 | Halcom D.D. | 2027-04-22 | Valid | 7B1D60647E7DAB721BCE21BD2EC8D2AF281207B01474B1A47BF5CF772A311D9D |
| Halcom CA PO e-signature 1 | Halcom D.D. | 2026-06-15 | Expired | 6616DA2DC8C81CD1D5ACB8664D8715E07925915B1130D0D2284604620FABFA98 |
| Halcom CA FO e-signature 1 | Halcom D.D. | 2026-06-15 | Expired | 24709797CD505CD70F27B2A6A013AF7455155CF7BA3E9AB6ACF03ABB12B8045B |

## Cross-signed versions

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


## What happens when it expires

Halcom Root Certificate Authority is valid until 2036-06-10, about 9.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.

## FAQ

**Is Halcom Root Certificate Authority 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 Halcom Root Certificate Authority expire?**

On 2036-06-10, about 9.6 years after the 2026-11-10 data snapshot.

**How many intermediate certificates has Halcom Root Certificate Authority issued?**

The CCADB lists 10: 8 valid, 2 expired and 0 revoked. The newest valid one is Halcom CA web 2, valid until 2035-03-25.

**Is Halcom Root Certificate Authority cross-signed?**

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

Sources: CCADB TLS Server Authentication report, All Included Root Certificate Trust Bit Settings, All Certificate Information (V5), the per-store TLS reports and Mozilla's Included CA Certificate Report (ccadb.org/resources).