Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was just wondering if a wildcard SSL certificate necessarily needs to have a common name that contains the domain name of the sites that need the SSL certificate applied to.

For example, for the following:

Domain name:



Do I necessarily need my wildcard certificate to have a common name of *

share|improve this question

migrated from Sep 6 '12 at 5:59

This question came from our site for professional and enthusiast programmers. might be a better place for this question. – Jay Riggs Oct 14 '09 at 0:23
up vote 31 down vote accepted

Yes, your common name should be * for a wildcard certificate.

Basically, the Common Name is what states what domain your certificate is good for, so it has to specify the actual domain.

Clarification: It shouldn't "contain" the domain name of the sites, it should be the domain of the sites. I'm guessing there is no difference in your question, I just wanted to clarify, in case there's a misconception of what the domain should be, or what the certificate will be used for.

share|improve this answer

Yes, Wildcard SSL Certificate is best solution as per your requirements. With Wildcard certificate you will be able to protect your visitor’s information. There is no matter, which page of your website is submitted. Wildcard certificate secures unlimited number of sub domains that share the same domain name.

Installing the same wildcard certificate across all sub-domains & servers transmits inbuilt risk: if one server or sub-domain is compromised, all sub-domains can be equally compromised. Make sure that your website is protected with multiple levels of protection from all external and internal pressure.

share|improve this answer

You must log in to answer this question.