The whois email address is no longer supported for Domain Control Validaiton and has been removed from API responses and the web application.

The CAB Forum has voted to update the maximum certificate lifetimes supported by browsers. This will impact all certificates that require to be trusted in browsers issued by any CA. The main push for these changes has come from Apple.

The advantage of shorter lifespans for certificates is the security improvements. It is likely to lead to the eventual removal of OCSP and much smaller CRLs both checks which can slow down browsers.

The proposed changes to certificate lifetimes are as follows

From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days.
As of March 15, 2026, the maximum lifetime for a TLS certificate will be 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.

Ultimately this will lead to a major push to automate certificate issues. We already offer an API to allow for customers to automate the ordering and delivery of their HTTPS/TLS certificate. Some customers have integrated with the console to complete the automation process.

We are developing in partnership with our provides a process using the ACME protocol and we will be making this available to customers and resellers. The ACME protocol will allow for the complete automation of certificate issuance. This will be provided via a CaaS (Certificate as a Service) subscription.

Updates will be provided on how we will implement the CaaS and the options availabel to resellers.

Any certificates you purchase now will still remain valid and can be reissued until the end of the order expiry date. We will offer long term certificates the opportunity to transition to the CaaS model.

Customers can now update the account email address.

You can update your email address via the billing portal. Once logged in click on the Account Information link and update your email address.

api2.servertastic.com is currently redirected to api.servertastic.com/v2/

From 1 MARCH 2025 the endpoint api2.servertastic.com will be removed and no longer respond to connection requests.

Users of api2.servertastic.com should update code to utilise api.servertastic.com/v2/ with the same endpoints.

We are also moving away from XML responses and JSON will become the default reqponse. This is anticipated during 2025. Customers are asked to consider updating their codebase to support JSON in the future.

We have implemented some improvements to our integrations with Sectigo and DigiCert. These improvements mean that certificates should become available much quicker in our system after the certificate authority issues the certificate.

We are currently beta testing a new app dashboard. Customers can login to the new dashboard at https://beta-app.servertastic.com

If you experience any issues you can still use the existing dashboard at https://app.servertastic.com

We will be adding new features to the beta dashboard over the coming weeks and eventually roll this out as the current version. If you have any requests or see any issues you can vote on features and report issues on our product page at https://product.servertastic.com

We have fixed an issue causing an incorrect currency conversion at checkout when purchasing products or points over the value of €/£1,000. Some customers may have been under charged for top-ups on their account. We will contact affected customers individually with an account remedy.

Due to some customers having large points audits causing the API call to timeout this call is now paginated. Updated API Docs.

Digicert products including RapidSSL, Geotrust and Thawte now support the ability to select the appropriate Intermediate Certificate Authority. This is supported by both the API and the order management page.

For most customers the Default option will suffice if the highest compatibility is required. However we have some customers who require support for older ICA and more modern ICA.

API Updates

When using the API we recommend using the productfields API call to obtain a list of the supported ICA for the specific product. The required ICA can then be specified using the selected_ca_cert option under the place call. If no ICA is provided as part of the API call then the default for that product will be used which is suitable for the majority of installations.

As a result of this update the hashing_algorithm API parameter will be ignored. This will be used in a future update to allow the selection of supported hashes depending on the product.

It is now possible to copy the 2FA link from the account page rather than needing to scan the QR code. This is useful for customers using systems such as 1Password on a computer rather than a mobile device.