# HTTP-based verification for wildcards

**URL:** <https://community.letsencrypt.org/t/http-based-verification-for-wildcards/47315>\
**Category:** Feature Requests\
**Created:** [November 29, 2017, 4:29pm UTC](https://community.letsencrypt.org/t/http-based-verification-for-wildcards/47315 "2017-11-29T16:29:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mkwm](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mkwm](https://community.letsencrypt.org/u/mkwm)\
**Post date:** [November 29, 2017, 4:44pm UTC](https://community.letsencrypt.org/t/http-based-verification-for-wildcards/47315/2 "2017-11-29T16:44:19Z")

</div>

“Why not HTTP validation” was already covered there: [Wildcard Certificates Coming January 2018](https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567/26?u=mkwm)

---

_[View the full topic](https://community.letsencrypt.org/t/http-based-verification-for-wildcards/47315)._
