# Wildcard certicate poorly supported

**URL:** <https://community.letsencrypt.org/t/wildcard-certicate-poorly-supported/191779>\
**Category:** Feature Requests\
**Created:** [January 26, 2023, 2:06pm UTC](https://community.letsencrypt.org/t/wildcard-certicate-poorly-supported/191779 "2023-01-26T14:06:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [January 26, 2023, 2:15pm UTC](https://community.letsencrypt.org/t/wildcard-certicate-poorly-supported/191779/2 "2023-01-26T14:15:36Z")

</div>

Is this a suggestion for improving Certbot?

If so, Certbot offers several built-in plugins for DNS wildcard automation. And, there are several 3rd party plugins. These are described in the Certbot docs ([link here](https://eff-certbot.readthedocs.io/en/stable/using.html#certbot-command-line-options)).

Certbot also has this extension by one of their developers for further DNS support for wildcard certs ([link here](https://community.letsencrypt.org/t/certbot-dns-multi-bringing-legos-100-dns-providers-to-certbot/186013))

But, there are many ACME clients you can use to get certs from Let's Encrypt. One of them, acme.sh, has support for numerous DNS systems for automation. Search github for it or see this list for Let's Encrypt's list of other ACME clients

> **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/)**
>
> Last updated: Jun 29, 2022 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece...

---

_[View the full topic](https://community.letsencrypt.org/t/wildcard-certicate-poorly-supported/191779)._