Certamira
Independent reseller and guide. Not a certificate authority and not affiliated with any certificate authority.

Wildcard certificate: what it is and who needs one

A wildcard certificate secures one domain and every subdomain at one level, for example *.example.com. If you run many subdomains, one wildcard is usually simpler than six single certificates. Validation is by DNS record, and certificates now last at most 200 days. The asterisk matches one label. A name such as a.b.example.com, or a second domain, needs its own certificate. You still install the certificate and private key on each server that presents the names.

What is a wildcard certificate?

A wildcard certificate is a public TLS certificate whose name uses an asterisk for one label, as in *.example.com. That pattern covers www.example.com, mail.example.com, and any other name with exactly one label in front of example.com. It does not cover a.b.example.com, because two labels sit in front of the domain. Different domains, such as example.com and example.org, need a multi-domain certificate or separate certificates.

Wildcard or single certificate?

A single certificate lists each host by its full name. A wildcard lists the pattern, so a new subdomain at the same level can use the certificate you already hold. With many subdomains, one file, one private key, and one expiry replace a stack of single certificates. A single certificate fits a few names. A wildcard key works for every matching name, so keep it only on the hosts that serve them.

How is a wildcard validated?

The authority checks that you control the domain before it issues the wildcard. The check is a DNS record that you publish and the authority reads. Let's Encrypt issues wildcard certificates only with DNS-01 validation. DNS-01 is a TXT record under the domain. Under CA/Browser Forum Baseline Requirements v2.2.7, section 4.2.1, domain validation can be reused for up to 200 days from 15 March 2026, then for 100 days from 15 March 2027, then for 10 days from 15 March 2029.

How long does it last?

Section 6.3.2 of the same baseline sets the maximum lifetime of a public TLS certificate at 200 days from 15 March 2026, 100 days from 15 March 2027, and 47 days from 15 March 2029. A certificate must expire within the cap that applies on its issue date. Let's Encrypt uses a default lifetime of 90 days, and renewal is advised every 60 days so a failed run can be retried. When the public cap falls to 100 days and later to 47 days, a scheduled client is the workable control. The client should refresh the DNS proof, install the new file, and reload the service before expiry.

Is free enough?

If you can automate DNS and renewal, free Let's Encrypt is enough. A paid wildcard helps when you cannot automate, or need vendor support. That choice does not lift the one level limit, and it does not extend life past the caps of 200 days, then 100 days, then 47 days. Names on two domains still need a multi-domain certificate or separate certificates, and names two levels down still need another certificate. Use the free certificate when a machine can update DNS and renew on a schedule, and use a paid certificate when a person must finish validation by hand or you want vendor help if issuance fails.

Need a paid wildcard?

Certamira sells wildcard domain validation certificates to companies and private persons, EUR 89 per year excl. VAT as of 4 November 2026. The checkout is run by our payment provider, Creem, which shows the final amount with VAT before you pay. See the dated price comparison first, then order a certificate. The site is an independent guide and is not a certificate authority; who runs it is on its own page.

Checked on 4 November 2026. Source: CA/Browser Forum Baseline Requirements v2.2.7; Let's Encrypt documentation.