|
FAQ
Q: When do I need to do to update my server's current SSL/TLS certificate to comply with the new 398-day limit?
A: If your certificate was issued prior to September 1, 2020, it will not be affected by the policy change. However, when that certificate expires, the replacement certificate will have a maximum lifespan of 397 days.
You can check the status of your website's certificate at https://www.ssltools.com. For more certificate options from SSL.com, visit https://www.ssl.ccom/certificates.
Q: I ordered a two-year SSL/TLS certificate from SSL.com before September 1, 2020. What happens if I reprocess it after SSL.com switches to 397-day certificates?
A: If you reprocess a two-year certificate after we have switched over to 397-day certificates, the reissued certificate will be limited to 397 days. However, you will be credited by SSL.com for the time remaining on the order. When the reprocessed certificate expires, you can issue a new certificate to cover the time remaining on the order.
Because each certificate issued after September 1 will be limited to 397 days, this means you may have to issue new certificates more often than you previously had to.
Q: My company has a privately-trusted root CA. Are privately-trusted SSL/TLS certificates subject to the new 398-day limit?
A: No. Apple's change only extends to publicly-trusted root CA certificates pre-installed on its devices, including SSL.com's roots. Root certificates installed by a user or administrator are not affected by the 398-day restriction.
If you have any questions or need assistance navigating this change, please email our support team ar [email protected] or visit https://www.ssl.com/contact_us/.
Regards,
SSL.com Support Team
[email protected]
|
