# Manage Netlify's SSL Certificate Domains

**URL:** <https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400>\
**Category:** Support\
**Tags:** netlify-newbie, netlify-dns-https-ssl\
**Created:** [October 22, 2019, 5:32pm UTC](https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400 "2019-10-22T17:32:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![subjektobjekt](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/subjektobjekt/32/3637_2.png) [@subjektobjekt](https://answers.netlify.com/u/subjektobjekt)\
**Post date:** [October 22, 2019, 5:32pm UTC](https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400/1 "2019-10-22T17:32:12Z")

</div>

I continue to run into the issue when I am hosting with Netlify that the SSL Certificate doesn’t include the wild card and I have to reach out to support every time. Is there a way that I can manage the domains for the SSL certificate on Netlify?

Currently it’s **Domains** : [mydomain.com](http://mydomain.com)  
Need it to be **Domains** : \*.mydomain.com, [mydomain.com](http://mydomain.com)

---

<div class="post-metadata">

**Author:** ![fool](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/fool/32/37_2.png) [@fool](https://answers.netlify.com/u/fool)\
**Post date:** [October 26, 2019, 12:26am UTC](https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400/2 "2019-10-26T00:26:07Z")

</div>

Sure thing, two options:

1. import your own custom wildcard certificate. These can be had for relatively cheap from vendors such as alphassl. There are almost always “deals” out there on the internet to get them for under 50 bucks, if you literally google “cheap wildcard ssl”. I haven’t found those companies (usually comodo or alphassl) to offer the same cheap pricing without going in via google, but YMMV.
2. let us manage your DNS. That’s the only way we can get wildcard certificates; we are not permitted to otherwise by our SSL provider.

---

<div class="post-metadata">

**Author:** ![jessiecris](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/jessiecris/32/28000_2.png) [@jessiecris](https://answers.netlify.com/u/jessiecris)\
**Post date:** [December 7, 2023, 6:40am UTC](https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400/3 "2023-12-07T06:40:46Z")

</div>

Hi,

How do we add wildcard domains on the Certificate if we are on Netlify DNS?

Thanks,  
JC

---

<div class="post-metadata">

**Author:** ![SamO](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/samo/32/41847_2.png) [@SamO](https://answers.netlify.com/u/SamO)\
**Post date:** [December 7, 2023, 8:07pm UTC](https://answers.netlify.com/t/manage-netlifys-ssl-certificate-domains/4400/4 "2023-12-07T20:07:20Z")

</div>

Wildcard subdomains aren’t enabled by default and can only be enabled from our end. There are also a few requirements before we’re able to do so:

- Either you have to use Netlify DNS so we can get you a wildcard SSL cert, or you must bring a custom wildcard certificate.
- We can only do this for a site that’s on a paid team (see [Pricing and Plans | Netlify](https://www.netlify.com/pricing#teams) for details)

Also note:

You can’t use domain aliases on the site with Wildcard subdomains enabled, just the bare domain and subdomains under your primary domain. If you try to add a domain alias then it won’t work.  
The primary custom domain for the site, if it is a `example.com` with `www.example.com` setting in our UI, must be `www.example.com` and **not** `example.com`!

Once the wildcard subdomain feature is enabled, you do not need to add new subdomains under the site settings. You’ll will need still need to create DNS records.

This might be a single wildcard DNS record for all subdomains (like a CNAME for \*.example.com pointing to the netlify.app subdomain for the site). Alternatively, you can also create the individual DNS records to add each subdomain (like CNAMEs for [subdomain-a.example.com](http://subdomain-a.example.com), [subdomain-b.example.com](http://subdomain-b.example.com), etc.) as covered in our external DNS documentation. Both work so please do whichever you prefer.

Let us know which site and we’ll verify that it meets the requirements and get that set up for you.
