JOIN OUR AFFILIATE NETWORK

Join our affiliate network and become a local SSL expert

♦ learn more about our program ♦
Menu
picture of tbs certificates
picture of tbs certificates
Certificates
Our products range
Partners
Support
Focus


On IIS: configure one certificate for several sites

For a Wildcard (Omnidomain) or Multiple-Site certificate

In order to use a certificate securing several web sites, such as wildcard or multiple-site server certificates, the server must be able to handle the HTTP 1.1 standard. It enables the management of several web sites under a IP address/Port number pair.

Only IIS6 version or higher are compatible under Windows 2003 Server with SP1. See the official note.

If you are using a lower version, then hosting several SSL websites with the same IP address/Port number pair is not possible. You'll need to use several IP addresses with the same port number (443) or the same IP address with several port numbers.

See here for Site Identifier

With IIS6 W2003 SP1+

In order to use the Host field with SSL, set up the Securebindings metabase and define a host field for your website. Example for host ssl1.example.com:
cscript.exe adsutil.vbs set /w3svc/<site identifier>/SecureBindings ":443:ssl1.example.com"

With IIS7+

In order to use the Host field with SSL, set up the Securebindings metabase and define a host field for your website. Example for host ssl1.example.com:
appcmd set site /site.name:"<site identifier>" /+bindings.[protocol='https',bindingInformation='*:443:ssl1.example.com']
See Microsoft official documentation
See also

To summarize:

  • under IIS5: one IP address per site is requires, even with a wildcard certificate
  • under IIS6: one IP address per site is requires, even with a wildcard certificate
  • under IIS6 SP1 and IIS7+: it can be done with one IP address by filling in the SecureBindings metabase manually as explained on Microsoft website.

Linked documentation