# Wildcard Certificates Coming January 2018

**URL:** <https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567>\
**Category:** Issuance Policy\
**Created:** [July 6, 2017, 3:38pm UTC](https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567 "2017-07-06T15:38:17Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![JamieE](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jamiee/32/60_2.png) [@JamieE](https://community.letsencrypt.org/u/JamieE)\
**Post date:** [July 6, 2017, 5:49pm UTC](https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567/17 "2017-07-06T17:49:06Z")

</div>

> [@jaddison](#):
>
> I would love to see multi-level domain wildcard support - so \*.sub.domain.tld as well as \*.domain.tld.

Per [RFC 2818](http://www.ietf.org/rfc/rfc2818.txt), you can't combine those both into one certificate. But you should be able to do it using two separate certificates.

---

_[View the full topic](https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567)._
