Root certificate · HALCOM d.d.

Halcom Root Certificate Authority

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.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—Yes

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

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, Code Signing, Document Signing, Encrypting File System, Secure Email, Time Stamping
Not-before cutoff
2026-05-19 (Code Signing, 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
HALCOM d.d.
Subject
CN=Halcom Root Certificate Authority,2.5.4.97=VATSI-43353126,O=Halcom d.d.,C=SI
SHA-256
D7BA3F4FF8AD05633451470DDA3378A3491B90005E5C687D2B68D53647CFDD66
SHA-1 (Windows thumbprint)
23D731FEDC5C8BB97DE6DC8E13B411BD4F24004F
SPKI SHA-256
5899D913EAD119B9CDB7BA2F30EFE0DF68AD2CD225BDF493E8323A25AA4DBE23
Valid from
2016-06-10
Expires
2036-06-10
Key
RSA 2048
Signature algorithm
sha256WithRSAEncryption
Serial number
CDF9B
Country
SI
Trust bits (CCADB)
Server Authentication, Client Authentication, Document Signing, Encrypting File System, Time Stamping
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://valid.halcom.si/ · expired: https://expired.halcom.si/ · revoked: https://revoked.halcom.si/
CCADB record
A004544
PEM
halcom-root-ca.pem

Look up this certificate on crt.sh

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).

Showing 10 of 10: 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
Halcom CA web 2 HALCOM d.d.2035-03-25Valid
Halcom CA TSA 2 HALCOM d.d.2035-03-25Valid
Halcom CA FO e-signature 2 HALCOM d.d.2033-04-03Valid
Halcom CA PO e-seal 2 HALCOM d.d.2033-04-03Valid
Halcom CA PO e-signature 2 HALCOM d.d.2033-04-03Valid
Halcom CA web 1 Halcom D.D.2027-04-22Valid
Halcom CA TSA 1 Halcom D.D.2027-04-22Valid
Halcom CA PO e-seal 1 Halcom D.D.2027-04-22Valid
Halcom CA PO e-signature 1 Halcom D.D.2026-06-15Expired
Halcom CA FO e-signature 1 Halcom D.D.2026-06-15Expired

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.

CRL and OCSP addresses

In the root certificate

Halcom Root Certificate 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://domina.halcom.si/crls/halcom_root_certificate_authority.crl

Used by the intermediates it issued

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

  • CRL: http://domina.halcom.si/crls/halcom_root_certificate_authority.crl (8)
  • CRL: ldap://ldap.halcom.si/cn=Halcom%20Root%20Certificate%20Authority,o=Halcom,c=SI?certificaterevocationlist;binary (8)

None of the valid intermediates under this root lists an OCSP responder.

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.

Check whether your device trusts it

Each platform keeps its own root store. The commands below look up Halcom Root Certificate Authority by common name (Halcom Root Certificate 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: 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 "Halcom Root Certificate Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: D7BA3F4FF8AD05633451470DDA3378A3491B90005E5C687D2B68D53647CFDD66

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 23D731FEDC5C8BB97DE6DC8E13B411BD4F24004F

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 "Halcom Root Certificate Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Halcom Root Certificate 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 "D7:BA:3F:4F:F8:AD:05:63:34:51:47:0D:DA:33:78:A3:49:1B:90:00:5E:5C:68:7D:2B:68:D5:36:47:CF:DD:66"

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 Halcom d.d. → Halcom Root Certificate 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 halcom-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=D7:BA:3F:4F:F8:AD:05:63:34:51:47:0D:DA:33:78:A3:49:1B:90:00:5E:5C:68:7D:2B:68:D5:36:47:CF:DD:66

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

  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