One of the very nice features of IIS 7 is the use of host headers in combination with SSL. This is a fine feature and this works perfect in combination with a wildcard certificate.

When I ordered a certificate with three (sub)domains I found that this certificate could not be used in combination with a host header.

For me this was a big disappointment because I was hoping I could use only one IP on the internet to preserve my public IP’s therefor I warn/inform all of you with this blog it’s a waste of money to buy a SAN certificate if you’de like to use it in this way, multipe single certificates are much cheaper.

UPDATE:

It is possible to use a SAN certificate on a single ip address using host header names, the problem is the IIS GUI. When you use appcmd it works like a charm.

appcmd set site /site.name:”<IISSiteName>” /+bindings.[protocol=’https’,bindingInformation=’*:443:<hostHeaderValue>’]

Source:
http://www.sslshopper.com/article-ssl-host-headers-in-iis-7.html

In the binding properties windows you will see the host header specified but no ssl certificate specified, this is correct when you browse to the URL specified in the host header you’re SSL site you’re HTTPS website will work fine. Many thanks http://www.sslshopper.com