# Wildcard ssl realising time

**URL:** <https://community.letsencrypt.org/t/wildcard-ssl-realising-time/51294>\
**Category:** Feature Requests\
**Created:** [January 24, 2018, 1:32pm UTC](https://community.letsencrypt.org/t/wildcard-ssl-realising-time/51294 "2018-01-24T13:32:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahii](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@mahii](https://community.letsencrypt.org/u/mahii)\
**Post date:** [January 24, 2018, 1:32pm UTC](https://community.letsencrypt.org/t/wildcard-ssl-realising-time/51294/1 "2018-01-24T13:32:21Z")

</div>

is wildcard ssl available ?

---

<div class="post-metadata">

**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\
**Post date:** [January 24, 2018, 1:51pm UTC](https://community.letsencrypt.org/t/wildcard-ssl-realising-time/51294/2 "2018-01-24T13:51:07Z")

</div>

Only via the v2 staging API.  
Have a look into the following statement:

> **[Wildcard Certificates Coming January 2018 - Let's Encrypt - Free SSL/TLS...](https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html)**
>
> Update, January 4, 2018
> We introduced a public test API endpoint for the ACME v2 protocol and wildcard support on January 4, 2018. ACME v2 and wildcard support will be fully available on February 27, 2018.
> Let’s Encrypt will begin issuing wildcard...

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [February 23, 2018, 1:51pm UTC](https://community.letsencrypt.org/t/wildcard-ssl-realising-time/51294/3 "2018-02-23T13:51:08Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
