SSL certificates and whether a wildcard common name will support domain.com

Posted by timpone on Server Fault See other posts from Server Fault or by timpone
Published on 2012-10-06T01:17:30Z Indexed on 2012/10/06 3:39 UTC
Read the original article Hit count: 237

Filed under:
|
|

Sorry, if this is very vendor specific but I purchased an inexpensive SSL Cert from GoDaddy. Right now everything on production is hosted off of www.domain.com. When specifying the common name would a wildcard (ie *.domain.com) cover the case of a lack of a third-level domain such as domain.com? Just to be sure, I made it for www.domain.com rather than a wildcard. If it matters, I will be using with nginx and a mod_passenger.

If I want to cover everything including domain.com and staging.domain.com, www.domain.com etc, would a wildcard be the proper cert? Does the inexpensive godaddy cert (12.99 / year) cover wildcard certs (it didn't seem to for me)?

Again, sorry for asking vendor specific questions and thx in advance.

thx

© Server Fault or respective owner

Related posts about nginx

Related posts about ssl