2. FAQ

Our FAQ provides information regarding issues related to TrustView, SSL certificates and other topics.

Tip

If you have a question not answered here, contact our Support and we may add it to the FAQ.

2.1. Industry Shift to 47-Day validity for SSL/TLS Certificates by 2029

The maximum lifetime of certificates is going down:

  • Until March 15, 2026, the maximum lifetime for an SSL/TLS certificate was 398 days.

  • As of March 15, 2026, the maximum lifetime for a TLS certificate is 200 days.

  • As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.

  • As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.

You can read more about the details here.

– CAB Forum CAB Ballot SC081v3

2.2. Are you not receiving any notifications?

For any notification-related issue (Email or SMS), see this segment of the documentation for details and troubleshooting tips.

2.3. Certificates ordered with a CSR do not include a private key

When ordering a certificate from TrustView using a CSR (Certificate Signing Request), the certificate will never include a private key. This is because when using the other method (by not using a CSR) TrustView will generate the private key for the certificate you are ordering and store it encrypted in the TrustView database. A private key can still be imported for the certificate at a later time if you provide one. This can be done from the detail page of the certificate inside TrustView.

Once the private key has been either created for the certificate by TrustView or provided by importing it at a later time, the certificate can be exported with or without the private key.

Tip

A private key can be generated for a certificate in several ways. An example could be by using OpenSSL.

2.4. How to revoke certificates

It is possible to revoke issued certificates directly from TrustView, by going to the details page of the specific certificate and pressing Revoke certificate. You will be prompted to confirm whether you want the certificate revoked or not.

After the revocation has been executed, it may take some time for the status shown in TrustView to update to reflect the new revoked status of the certificate.

How revocation behaves depends on how the certificate was issued:

  • ADCS-issued certificates - you can additionally choose a revocation reason. Revocation is asynchronous: the certificate is marked as revocation-requested, and can end up in a failed state that requires pressing Revoke certificate again to resubmit the request.

  • Let’s Encrypt certificates - revoked immediately, via the ACME protocol.

  • Certificates ordered through TrustView (e.g. DigiCert, Entrust, GeoTrust, Certum) - revoked immediately, via the Cryptomathic backend.

  • Manually entered certificates - cannot be revoked through this feature; pressing Revoke certificate will fail with a generic error.

Danger

Once a certificate has been revoked, the revocation cannot be undone.