Hi, It may be cheaper to look at using SANs (subject alternative names). That is where your certificate has a common name, but you add the alternative names to it when ordering. I use this at work quite often - check www.allpayments.net, that is one site that uses SANs - the common name is www.allpayments.net, but there is a subject alternative name of allpayments.net, so that people can use this to request a page without the www prefix. Andrew. -----Original Message----- From: blind-sysadmins-bounces@lists.hodgsonfamily.org [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: 22 July 2011 21:13 To: blind-sysadmins Subject: [Blind-sysadmins] ssl certificate question Hello, I've got to secure some services using an ssl certificate. Each is operated on a different subdomain for example: www.domain.com pop.domain.com smtp.domain.com svn.domain.com etc. It's now time to renew the certificates, I wasn't the one who purchased the original batch, but the client has a separate certificate purchased at the same time for each service. I'm wondering if it wouldn't be better to do a wildcard certificate such as: domain.com or: *.domain.com in the cert's commonname field? I'd prefer to only use one certificate for all services if possible and it also saves a considerable amount of money. Thanks. Dave. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins