Whoa, acronyms :) So according to this question you can have multiple SSL subdomains on one IP address as long as your server supports TLS (which Apache 2.2x does).

Another answer to that question points out that the client browser must have SNI support to work, which IE doesn't have on Windows XP. So, what happens to people with that browser is a warning message saying that the SSL cert doesn't match the domain.

Can one resolve this issue for those client browsers without SNI support? Does a wildcard (for subdomains) do the trick? Are there other (cheaper) options?


Clients with no SNI support will get the first certificate loaded by Apache on that port.

So, yes, a wildcard certificate will not rely on client Server Name Indication support. If your resources all have a common parent domain, this is probably the way to go. The other option (with no common parent domain) is to use a certificate that provides Subject Alternate Names.

Both are expensive; an Alternate Names cert is a bit cheaper (but limits the number of sites you can cover, and needs to be re-issued when those sites change).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.