Multiple Wild Card Certificates for One Domain

Hi All

Hopefully this had been answered before - i had a quick look but couldn’t find anything.

We have multiple customers (accounts).

One of the services we offer is automatic generation of gateway names using DNS.

For example if you deploy a mqtt gateway we automatically assign

We are now looking at how to automatically secure these as well

In an ideal world we would be able to have a * certificate per customer (so a private key is the same for one customer but not across all customers)

It this an ideal design? Are there other ways we could do this?

A second design is that we manage just one certificate and share it with all customers but don’t let them know what the private key (i.e. inject when the gateway is spun up).


Both designs allow customers to impersonate each other.

Perhaps your service can generate a private key and certificate for the device, during the registration of the device to your service.

This way, no private keys are shared between devices and certificate names are appropriately constrained (e.g. to

I am sure that Let’s Encrypt would give you an appropriate rate limit exemption for such an IoT scenario, so that your service can generate and distribute new certificates on-demand (at device registration time and then subsequent renewals).


Does the client actually need a wildcard? I.e., does one client get multiple hostnames? Or only one

Because if the client doesn't need multiple hostnames, you might just offer a single SAN cert. Don't bother getting a wildcard.

If your client actually gets multiple hostnames, you might want to consider giving every client his/hers own subdomain:, so you can get a certificate for *

1 Like

In addition to the good suggestions above, you may want to submit your domain to the Public Suffix List. Let’s Encrypt uses it to control rate limits, and it offers many other advantages too.

thanks all for the suggestions and feedback :smiley:

1 Like

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