We are hosting multiple ASP.Net applications on an IIS web server. All the applications are under the same 'Default Web Site' parent. Most of them have their separate application pool.


The default website is bounded to a SSL certificate and all applications use the same certificate. Now, I have to provide a different SSL to one of the applications. My questions are:

  1. Is it possible for the application under 'Default Web Site' to have a different binding for SSL?
  2. If not, what are some of the options?

If your IIS is version 8.0 or higher (Windows Server 2012 or newer), it supports an extension to the TLS protocol called SNI (Server Name Indication). Here are some IIS specific instructions on using it.

If you have anything earlier than IIS 8.0, you will either need to get a re-issued certificate that contains all of the names you need in it using the Subject Alternative Name field. Or you will need to host the alternate certificate in a new website bound to a different IP:port combination.

  • We are using Server 2012 with IIS8. – SJaka May 25 '16 at 18:13

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.