Generating a CSR for a Wildcard SSL Certificate

Wildcard SSL certificates will allow you to secure an unlimited number of subdomains for a registered base-domain. Let's say you own the base-domain, then a wildcard for * can secure Basically the asterisk (*), or star is the wildcard and can be any valid subdomain.

About the Common Name (CN)

Every SSL certificate has a Common Name, or CN for short. When generating a Certificate Signing Request (CSR), the CN causes lots of head-scratching. The meaning of Common Name isn't plainly obvious and it can trip up even the most experienced techies, especially when it comes to the CN for a wildcard certificate

The CN is simply the fully qualified domain name (FQDN) that you want to secure with an SSL certificate. Suppose that you want to secure then the CN would be

Strictly-speaking, the naked, or base-domain, like, is not a true FQDN because it does not include a hostname, but nowadays leaving the www hostname out is widely accepted. 


The Common Name (CN) for a Wildcard SSL Certificate

The Common Name for wildcard certificates is always starts with an asterisk (* star). 

Example: a Common Name of * will secure:

Will secure... 

Will not secure...

Example: a Common Name of * will secure

Will secure...

Will not secure...