The Common Name must be the same as the Web address you will be accessing when connecting to a secure site. For example, an SSL Server Certificate for the domain domain.com will receive a browser warning if accessing a site named www.domain.com or secure.domain.com , as www.domain.com and secure.domain.com are different from domain.com .
Here’s the information you’ll need to fill out in your Certificate Signing Request for your Wildcard SSL CSR: Common Name (CN) – Your fully-qualified domain name goes here. Organization Name (O) – The legal name of your company or organization; Organization Unit (OU) – What department or division of your company are you? *In the case of the Multi Domain Wildcard, even though the certificate will cover multiple wildcard SANs, the common name listed in the CSR must be a fully-qualified domain name (FQDN), and therefore cannot have the wildcard asterisk (*). All of the SANs, however, can either be FQDNs or wildcards. SANs A wildcard is a certificate that protects all of the subdomains at a specified level in the common name domain. Common names for wildcard certificates use an asterisk to specify the unlimited level and are formatted as such — *.yoursite.com. Put simply, a common name on an SSL/TLS certificate is the domain name, which must match exactly with the web address in your host. For example, if you’re going to secure example.com with an SSL/TLS Certificate, the common name must also be example.com. Also, there are two different versions of the domain name, WWW and non-WWW. The EssentialSSL Wildcard certificate is a great value for small and medium-sized businesses. Because it's a wildcard certificate, you can quickly and easily secure an unlimited number of subdomains of the same domain name. You are entering the Common Name (CN) of the certificate as a SAN. Following regulations, we will always add your Common Name as a SAN, this does not need to be specified. You incorrectly enter the SAN as a sub-domain, multi-domain name, internal SAN or IP.
Sep 18, 2019 · The Common Name mismatch warning may occur if a wildcard certificate is installed via cPanel or WHM for the bare domain only, while one tries to establish an https connection to a subdomain of the domain the wildcard certificate is issued for. Wildcard certificates are supposed to cover the naked domain name and subdomains of the same level.
The common name can only contain up to one entry: either a wildcard or non-wildcard name. It’s not possible to specify a list of names covered by an SSL certificate in the common name field. The Subject Alternative Name extension (also called Subject Alternate Name or SAN) was introduced to solve this limitation. The Common Name allows specifying a single entry (either a wildcard or single-name), whereas the SAN extension supports multiple entries. However, the SAN is only supported by certain SSL certificate products . Wildcard SSL certificates secures your website URL and an unlimited number of its subdomains. For example, a single Wildcard certificate can secure www.coolexample.com, blog.coolexample.com, and store.coolexample.com. Wildcard certificates secure the common name and all subdomains at the level you specify when you submit your request.
Jan 12, 2014 · In SSL/TLS, domain name verification occurs by matching the FQDN of the system with the name specified in the certificate. The certificate name can be in two locations, either the Subject or the Subject Alternative Name (subjectAltName) extension. When present in the Subject, the name that is used is the Common Name (CN) component of the X.500
Wildcard SSL Certificates are big money-savers. A Wildcard SSL Certificate allows you to secure an unlimited number of first-level sub-domains on a single domain name. That means you can get an SSL Certificate with the common name as *.mydomain.com and you can use it on all of the following without receiving any errors: www.mydomain.com