Certificate authority

SwissSign AG

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

Data updated

Details

CCADB CA owner
SwissSign AG
Country
CH
Country (CCADB)
Switzerland
Roots
3
Roots trusted for TLS
Chrome 1 · Mozilla 1 · Apple 2 · Microsoft 3
Intermediates under its roots
35 (3 valid)
Auditor
TÜV Austria
CAA
swisssign.com

CAA records

The CCADB lists 1 CAA issuer domain(s) recognized by the currently valid intermediate certificates of SwissSign AG. One issue record with any of them lets SwissSign AG 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 "swisssign.com"
DomainValid intermediates
swisssign.com22

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

Root certificates (CCADB)

SwissSign AG has 3 root certificate(s) in the CCADB TLS report. Together they have signed 35 intermediate CA certificates, 3 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
SwissSign Gold CA - G2 RSA 4096 2036-10-25 RemovedIncludedIncludedIncluded23 (3)
SwissSign RSA TLS Root CA 2022 - 1 RSA 4096 2047-06-08 IncludedIncludedNot includedIncluded0 (0)
SwissSign Silver CA - G2 RSA 4096 2036-10-25 RemovedRemovedIncludedIncluded (NotBefore cutoff)12 (0)

Audits

Audit data the CCADB records for the TLS roots of SwissSign AG. Auditor(s): TÜV Austria. The most recent audit period ended on 2026-06-12.

AuditSchemePeriodStatementReport
Standard auditETSI EN 319 4112025-06-14 – 2026-06-122026-09-02 it-tuv.com
TLS Baseline RequirementsETSI EN 319 4112025-06-14 – 2026-06-122026-09-02 it-tuv.com
TLS EV GuidelinesETSI EN 319 4112025-06-14 – 2026-06-122026-09-02 it-tuv.com

CP/CPS documents

Certificate Policy and Certification Practice Statement links that SwissSign AG 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 SwissSign AG lists in the CCADB (replace [at] and [dot] in addresses):

  • certificatemisuse[at]swisssign[dot]com
  • keycompromise[at]swisssign[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 “SwissSign”:

Bugzilla: incident reports matching “SwissSign”

ACME directories (CCADB)

DV ACME directory URLs that SwissSign AG has disclosed in the CCADB for its valid certificates:

  • https://acme.swisssign.ch/v1/pma-d23e4206-ccfb-492c-9b27-fc05e05577be/directory

FAQ

What CAA record allows SwissSign AG to issue certificates?

Publish example.com. CAA 0 issue "swisssign.com". The CCADB lists 1 recognized domain(s) for SwissSign AG: swisssign.com.

Who audits SwissSign AG?

TÜV Austria, according to the CCADB. The latest TLS Baseline Requirements audit (ETSI EN 319 411) covers 2025-06-14 to 2026-06-12; the statement is dated 2026-09-02.

How do I report a problem certificate to SwissSign AG?

Use the channel(s) listed in the CCADB: certificatemisuse[at]swisssign[dot]com, keycompromise[at]swisssign[dot]com.

How many root certificates does SwissSign AG have?

3 in the CCADB TLS report. Trusted for TLS: Chrome 1, Mozilla 1, Apple 2, Microsoft 3. They have signed 35 intermediates, 3 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