A Swiss authority for DV, OV and EV certificates. Its CAA value is swisssign.com.
| Run by | SwissSign AG, Switzerland |
| CAA value | swisssign.com |
| CAA parameters | Not documented |
| Cost | Paid |
| Certificates | DV, OV and EV; wildcards except EV |
| Longest certificate | 200 days |
| Issuer names on its certificates | SwissSign RSA TLS DV ICA 2022 - 1, SwissSign RSA TLS OV ICA 2026 - 1 |
May SwissSign issue for your domain?
Enter a domain or hostname: we read its CAA records as SwissSign must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for SwissSign
Published on your domain, this lets SwissSign issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "swisssign.com"
An issue record covers wildcard certificates too. To let SwissSign issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "swisssign.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
It supports issue and issuewild and reads but does not act on iodef. If an unknown tag is marked critical, or the check cannot run for any reason, it issues nothing.
Getting a certificate
ACME is for Managed PKI customers, with a directory address per account.
What changed
- 10 June 2026 — New 2026 issuing CAs for DV, OV and EV.
Worth knowing
- Chrome has removed SwissSign Gold CA – G2; its certificates chain to SwissSign RSA TLS Root CA 2022 – 1, which Apple does not include.
Sources
Checked on 27 September 2026 against these official sources:
- SwissSign CPCPS TLS — repository.swisssign.com