System status | SwissSign
A data security specialist by Swiss Post

Main section


Release notes of the release of November, 4th 2017

Please take into account the following changes of this release:

It is now possible within a Managed PKI to let validate new main domains in the menu item for domain validation.  SwissSign will validate automatically your access to a domain either by validation of the DNS entry or by validation of a created web page <Domain>/.well-known/pki-validation/swisssign-check.htm.

SwissSign will add the domain after successful validation to the setup of your Managed PKI free of charge. This eliminates the change form and the 250 CHF/EUR change fee for adding domains. However, if you want to check the domain ownership manually by support of the whois entry or power of attorney, you have still to fill out the change form.

Please find detailed information of this new menu item for domain validation of a Managed PKI domain in the current operating instructions .

Furthermore, accounts created under can now be deleted if no certificates have been applied for under these accounts.

We will gradually remove the term "license" from the systems and It is replaced by the term "certificate voucher", or when the corresponding code is redeemed, the term is "voucher code". The term “license” was misleading because it is used in the German language in connection with rights to use a software.

The product E-Mail ID Gold will not be available in the web shop any longer. The high compliance costs and the new ETSI regulations regarding certificates with personal names no longer justify retail sales. The request is still possible in connection with a Managed PKI contract (company registration authority). A Managed PKI is already available from 500 CHF/EUR. For simple e-mail signatures and encryption, the e-mail ID Silver certificate is still available.

We will disable the download of the CRL lists via in the near future. Instead, the default paths for the CRL check must be used. You can find them in the entry of the certificate:<keyid>. Please pay attention to your applications if they are still using the outdated path for certificate validation.