OpenSSL identified a high-risk vulnerability over the weekend and released a patch on November 1st. If you are running OpenSSL on any platform (highly likely), you’ll need to run an update to ensure your connections and infrastructure remain secure. Note: this only affects the OpenSSL library, you do not need to update your SSL certificate(s).
Update immediately if you’re running OpenSSL version 3.0.0 through 3.0.6.
The new Terms and Conditions will take effect from 13 October 2022 and by keeping and renewing your domain name(s), you confirm having read and accepted the modified terms and conditions.
If you do not agree with the new Terms and Conditions, you may choose to delete your domain name(s) before the effective date via your registrar, i.e. the company with whom you have registered your domain name(s).
Adapting to Industry Changes for Better Web Security The CA/B Forum has voted on removing the file-based domain control validation (DCV) method for Wildcard certificates (e.g. *.domain.com) starting Dec. 1, 2021. So why the update?
The change was created in response to the concern that host-based control validation isn’t a strong enough way to demonstrate that someone has control over a domain’s entire namespace. Ultimately, this change improves security for subdomains and therefore, web users overall.
To be prepared and acclimated before the official start date, major CA’s such as DigiCert and Sectigo, will no longer allow file-based DCV for Wildcard certificates starting Nov. 15. After that, users can only use email and DNS validation methods to perform DCV for Wildcards.
You can buy a Certificate not only to protect any server or hosting that is provided by us, but for any other services/servers that you use from different providers. You can also order SSL installation service from us to get your Certificate installed correctly.