# Does wildcard SSL certificate covers root domain?

**URL:** <https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713>\
**Category:** Feature Requests\
**Created:** [April 28, 2022, 6:42am UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713 "2022-04-28T06:42:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![EIthq982kz](https://avatars.discourse-cdn.com/v4/letter/e/f9ae1b/32.png) [@EIthq982kz](https://community.letsencrypt.org/u/EIthq982kz)\
**Post date:** [April 28, 2022, 6:42am UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/1 "2022-04-28T06:42:39Z")

</div>

Does wildcard certificate also validates root domain?

There are few writings about "Does a wildcard certificate cover root domain"

> [@ACME v2 Production Environment & Wildcards](https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578):
>
> T…

[https://www.rapidsslonline.com/ssl/does-a-wildcard-certificate-cover-a-root-domain/](https://www.rapidsslonline.com/ssl/does-a-wildcard-certificate-cover-a-root-domain/)

According to these writings as per my understanding Single Wildcard \*.example.com domain can have wildcard DNS names for multiple base domains, and can also mix in non-wildcard names  
(e.g \*.example.com and [example.com](http://example.com))

Although I don't register base domain([example.com](http://example.com)), does SSL providers automatically add the root domain as a Subject Alternative Name to a wildcard SSL certificate?

so that I don't need to add additional root-domain([example.com](http://example.com))?

Thank you

---

<div class="post-metadata">

**Author:** ![maxh](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/maxh/32/31936_2.png) [@maxh](https://community.letsencrypt.org/u/maxh)\
**Post date:** [April 28, 2022, 8:14am UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/2 "2022-04-28T08:14:44Z")

</div>

You need to generate a certificate for `*.example.com` and `example.com`. They can both be on the same certificate, but you do have to request both. There are some CAs that will _only_ give you a certificate for the root and wildcard, but I don't know of any that let you make your own request, but then automatically amend it (and they shouldn't).

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [April 28, 2022, 11:09am UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/3 "2022-04-28T11:09:08Z")

</div>

I think it is best to get exactly what you ask for (despite what may seem obvious).  
[not for the CA to think they know more about what I need and change my request (in any way)]

Q1. How much trouble is it to add "`example.com`" to the "\*.example.com" request (if/when needed)?

Q2. What would happen when someone requests more than 50 wildcard entries on a single cert?  
[there would be no room to include more than 50 more base domains into it]

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [April 28, 2022, 11:16am UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/4 "2022-04-28T11:16:07Z")

</div>

> [@EIthq982kz](#):
>
> Although I don't register base domain([example.com](http://example.com)), does SSL providers automatically add the root domain as a Subject Alternative Name to a wildcard SSL certificate?

Some CA's _might_ automatically also include the root domain, but Let's Encrypt doesn't: you only get what you've asked for.

---

<div class="post-metadata">

**Author:** ![jvanasco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jvanasco/32/55900_2.png) [@jvanasco](https://community.letsencrypt.org/u/jvanasco)\
**Post date:** [April 28, 2022, 2:06pm UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/5 "2022-04-28T14:06:32Z")

</div>

@maxh I edited your comment above to put the domain names within backticks for clarity.

---

<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:** [May 28, 2022, 2:07pm UTC](https://community.letsencrypt.org/t/does-wildcard-ssl-certificate-covers-root-domain/176713/6 "2022-05-28T14:07:15Z")

</div>

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