ACME v2 was released Let’s Encrypt, officially supports wildcard certificates

Let’s Encrypt announced that ACME v2 officially supports wildcard certificates. Let’s Encrypt announced that it will continue to remove the barriers to using HTTPS on the Web, allowing each site to easily obtain management certificates.

ACMEv is an updated version of the ACME protocol, considering that industry experts and other organizations may wish to use the ACME protocol for certificate issuance and management on a certain day. It has passed the IETF standard process.

Wildcard certificates allow the use of a single certificate to protect all subdomains of a domain. In some cases, wildcard certificates can make certificates easier to manage to help make the Web 100% HTTPS protocol. However, for most use cases, Let’s Encrypt still recommends using non-wildcard certificates.

Wildcard certificates are only available through ACMEv2. In order to use ACMEv2 for the wildcard or non-wildcard certificates, you need an updated client that supports ACMEv. Let’s Encrypt wants all customers and subscribers to be converted to ACMEv2, although the ACMEv1 API has not been “rejected.”

In addition, the wildcard domain must be verified using the DNS-01 challenge type. This indicates that you need to modify the DNS TXT record to demonstrate control of the domain to obtain a wildcard certificate.

Source: Let’s Encrypt