# Please support wildcard certificates

**URL:** <https://community.letsencrypt.org/t/please-support-wildcard-certificates/258>\
**Category:** Issuance Policy\
**Created:** [August 17, 2015, 8:53am UTC](https://community.letsencrypt.org/t/please-support-wildcard-certificates/258 "2015-08-17T08:53:58Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [August 26, 2015, 5:30pm UTC](https://community.letsencrypt.org/t/please-support-wildcard-certificates/258/19 "2015-08-26T17:30:27Z")

</div>

@docwhat, that’s definitely a reason that we think most users won’t need wildcard certificates as much as they have in the past: if they have a new host they should be able to get a new cert that includes that host for free in one minute.

But some people have described use cases where this is a problem: examples include deployments that have thousands of hostnames, or where the hostnames are dynamically generated by software (In the latter case, the administrator doesn’t even necessarily know ahead of time what hostnames will exist or will be accessed by clients.)

---

_[View the full topic](https://community.letsencrypt.org/t/please-support-wildcard-certificates/258)._
