Securing a root domain along with all its subdomains (*.example.com) usually means SSH-ing into a server, installing Certbot, and wrestling with terminal flags or DNS plugins.
While CLI tools are great for automated pipelines, sometimes you just need a quick Wildcard certificate for a staging environment, shared hosting (cPanel), or a custom appliance where installing ACME clients isn't practical.
Here is a straightforward, browser-based workflow to issue a free Let's Encrypt Wildcard SSL certificate using the ACME v2 protocol without touching the command line.
Why Wildcard Certificates Require DNS-01 Verification
Standard single-domain certificates can be verified via HTTP-01 (placing a file in /.well-known/acme-challenge/). However, Let's Encrypt strictly requires DNS-01 challenge verification for Wildcard domains (*.yourdomain.com) to prove you control the entire DNS zone.
Step-by-Step: Issuing a Wildcard SSL via Web ACME v2
1. Define Your Domain Scope
When generating your certificate request, include both the bare root domain and the wildcard entry so browsers trust both:
example.com*.example.com
You can follow the complete visual walkthrough on the SSL Free Site Guides if you want to see how each ACME step behaves under the hood.
2. Add the _acme-challenge TXT Record
Once the ACME server generates your challenge token, log into your DNS provider (Cloudflare, Namecheap, Route53, etc.) and create a new TXT record:
-
Type:
TXT -
Host / Name:
_acme-challenge(Note: Most DNS panels automatically append.example.com) -
Value:
<the-verification-token-provided> -
TTL: Lowest possible (e.g.,
60seconds orAuto)
3. Wait for DNS Propagation & Verify
Before triggering the ACME validation check, make sure the TXT record is globally visible. You can verify this via dig or any DNS lookup tool:
bash
dig -t TXT _acme-challenge.example.com +short
Top comments (0)