Certificate authority

Microsec Ltd.

Microsec Ltd. operates 3 root certificate(s) trusted for TLS by at least one major root store (CCADB owner: Microsec Ltd.; country: HU). See fingerprints, expiry and Chrome, Mozilla, Apple and Microsoft status.

Data updated

Details

CCADB CA owner
Microsec Ltd.
Country
HU
Country (CCADB)
Hungary
Roots
3
Roots trusted for TLS
Chrome 3 · Mozilla 3 · Apple 1 · Microsoft 3
Intermediates under its roots
87 (58 valid)
Auditor
Hunguard
CAA
e-szigno.hu

CAA records

The CCADB lists 1 CAA issuer domain(s) recognized by the currently valid intermediate certificates of Microsec Ltd.. One issue record with any of them lets Microsec Ltd. 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 "e-szigno.hu"
DomainValid intermediates
e-szigno.hu56

For issuewild, iodef or DNS-provider formats, use the CAA record generator: CAA Generator

Root certificates (CCADB)

Microsec Ltd. has 3 root certificate(s) in the CCADB TLS report. Together they have signed 87 intermediate CA certificates, 58 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 ChMoApMSIntermediates
e-Szigno Root CA 2017 ECDSA P-256 2042-08-22 IncludedIncludedNot includedIncluded23 (18)
e-Szigno TLS Root CA 2023 ECDSA P-521 2038-07-17 IncludedIncludedNot includedIncluded10 (7)
Microsec e-Szigno Root CA 2009 RSA 2048 2029-12-30 IncludedIncludedIncludedIncluded54 (33)

Audits

Audit data the CCADB records for the TLS roots of Microsec Ltd.. Auditor(s): Hunguard. The most recent audit period ended on 2025-09-09.

AuditSchemePeriodStatementReport
Standard auditETSI EN 319 4112024-09-10 – 2025-09-092025-12-05 hunguard.hu
TLS Baseline RequirementsETSI EN 319 4112024-09-10 – 2025-09-092025-12-05 hunguard.hu
TLS EV GuidelinesETSI EN 319 4112024-09-10 – 2025-09-092025-12-05 hunguard.hu

CP/CPS documents

Certificate Policy and Certification Practice Statement links that Microsec Ltd. has disclosed in the CCADB for its TLS roots, with effective dates:

Report a certificate problem

To report a mis-issued certificate, a compromised private key or other abuse, use the channels Microsec Ltd. lists in the CCADB (replace [at] and [dot] in addresses):

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 “Microsec”:

Bugzilla: incident reports matching “Microsec”

ACME directories (CCADB)

DV ACME directory URLs that Microsec Ltd. has disclosed in the CCADB for its valid certificates:

  • https://acme.e-szigno.hu/acme/directory

FAQ

What CAA record allows Microsec Ltd. to issue certificates?

Publish example.com. CAA 0 issue "e-szigno.hu". The CCADB lists 1 recognized domain(s) for Microsec Ltd.: e-szigno.hu.

Who audits Microsec Ltd.?

Hunguard, according to the CCADB. The latest TLS Baseline Requirements audit (ETSI EN 319 411) covers 2024-09-10 to 2025-09-09; the statement is dated 2025-12-05.

How do I report a problem certificate to Microsec Ltd.?

Use the channel(s) listed in the CCADB: HighPriorityCertificateProblemReport[at]e-szigno[dot]hu, https://e-szigno.hu/security-events-report.

How many root certificates does Microsec Ltd. have?

3 in the CCADB TLS report. Trusted for TLS: Chrome 3, Mozilla 3, Apple 1, Microsoft 3. They have signed 87 intermediates, 58 of them still valid.

Sources

  1. CCADB — Resources
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — List of CAA Identifiers
  4. CCADB — List of CA problem reporting mechanisms