Hello, Could you please offer a way to mark a domain name (via DNS) as ok to validate wildcard via HTTP? Live updating of DNS is extremely impractical for me. Thanks! James

Right. That’s why I am suggesting marking ‘control of *.xyz.com is by the person who controls xyz.com HTTP’ via DNS.

The ACME working group is working on a CAA extension that can be used to tell CAs which validation methods are permitted for a domain, including a separate “issuewild” property for wildcard identifiers. It would be possible to relax the DNS validation requirement for domains with a CAA record indica…

Indeed, using dns-01 method is not a good option in cases where you want to provide Let’s Encrypt support in widely distributed servers which have to run mostly autonomous. It would be very simple to support http-01 based validation for requesting wildcards like *.aa.bb.cc from a specific server, x…

HTTP-based verification for wildcards

Feature Requests

mkwm November 29, 2017, 4:44pm 2

“Why not HTTP validation” was already covered there: Wildcard Certificates Coming January 2018

Topic		Replies	Views
HTTP validation for wildcard certificates Feature Requests	6	5208	September 5, 2017
Wildcard certificates via http-01 Issuance Policy	17	19611	January 29, 2018
ACME v2 http01 challange Feature Requests	2	1360	January 15, 2018
Dns-01 vs. Wildcard certificates Issuance Policy	4	3721	May 30, 2016
Help need to implement wildcard certificate to my website Help	4	1957	February 3, 2018

HTTP-based verification for wildcards

Related topics