A wildcard certificate secures a domain and every subdomain under it with one certificate, useful the moment you have more subdomains than you want to issue individual certs for, or don't know all of them in advance.
When you actually need one
If you're running a platform where each customer gets their own subdomain (client1.yourapp.com, client2.yourapp.com, and so on), a wildcard for *.yourapp.com covers all of them without issuing a certificate every time a new one is created.
Why it requires DNS validation
Standard certificates can be validated by placing a file at a specific URL. Wildcard certificates can't work that way, there's no single path that covers every possible subdomain, so validation happens by adding a TXT record to your DNS instead, proving you control the domain itself rather than one file on one subdomain.
Enable wildcard AutoSSL
In cPanel, go to Security → SSL/TLS Status, and request a wildcard certificate for the domain via AutoSSL.
Add the DNS TXT challenge record
AutoSSL will provide a TXT record to add at your DNS provider. If Anomica manages your DNS, this can happen automatically, otherwise add it manually where your zone lives.
Wait for issuance
Once the TXT record is visible, validation and issuance usually complete within a few minutes to an hour.
Confirm coverage
Check that a random subdomain, like test123.yourdomain.com, loads with a valid padlock, confirming the wildcard is actually active.
Reseller white-label domains
If your clients' domains use your private nameservers, Anomica controls their DNS zone directly, which makes wildcard validation fully automatic with no manual TXT record step.