SSL Certificates
Traditional SSL Certificate products remain available for existing customers and special certificate requirements.
Buy standard SSL certificates for compatibility and manual workflows.
Choose traditional certificates when you need a specific CA product, manual issuance, IP SSL, or an environment that is not ready for AutoSSL.
Product Types
| Type | Description |
|---|---|
| Single SSL | Protects one domain, usually including root and www |
| Multi SSL | Protects multiple domains or hostnames |
| Wildcard SSL | Protects a root domain and first-level subdomains |
| IP SSL | Protects a public IP address |
Single-Domain SSL
For one primary website name, usually root + www.
Traditional Single-Domain SSL is for one primary website name, usually the root domain and www pair. It is simple and compatible, but it is not the future automation-first product path.
Use it when a customer needs a standard certificate order, a specific CA product, or a manual installation workflow.
Multi-Domain SSL
For multiple domains or hostnames on one traditional certificate.
Traditional Multi-Domain SSL is for several different domains or hostnames on one certificate.
Use it when the customer needs a classic SAN certificate and wants to manage the domain list manually during order, validation, and reissue.
Wildcard SSL
For a root domain and first-level subdomains.
Traditional Wildcard SSL protects one root domain and its first-level subdomains, such as *.example.com.
Use it when the customer needs broad subdomain coverage but is not ready to use AutoSSL renewal and deployment workflows.
Positioning
Traditional certificates are no longer the main product narrative, but remain useful for:
- Customers who need a specific CA or certificate type
- IP SSL use cases
- Manual issuance or special installation workflows
- Environments that cannot use AutoSSL yet
Documentation
Legacy WHMCS Knowledge Base content is archived: