#WATCH MY DOMAINS SSL CERTIFICATE WINDOWS#

I know that Apache and Tomcat also have support for SNI, but I am not familiar them enough to know what versions support it.ĭepending on your application/web server and what type of SSL certs you are able to obtain will dictate your options. If you use a single IP, then you can configure websites to respond to requests for specific hostnames. So the hostname (Server Name) that is used to make the request is used to indicate which SSL cert that IIS should use to for the request. SNI allows you to bind an SSL cert to a hostname, not to an IP. However, IIS8+ includes support for something called Server Name Indication (SNI). If you are running IIS8 or later, then the same applies. If you are using a multi domain cert or a wildcard cert, then you can get away with the single IP as you only have one SSL cert to begin with.

Greatly simplify your server's TLS/SSL Configuration: Using a Multi-Domain (SAN) Certificate saves you the hassle and time involved in configuring multiple IP addresses on your server, binding each IP address to a different certificate, and.

This causes you to need to have a different IP for each subdomain if you are using a dedicated SSL cert for each subdomain. Microsoft IIS and Apache are both able to Virtual Host HTTPS sites using Multi-Domain (SAN) Certificates. Clients get the public key to open a TLS connection from the server's SSL certificate. SSL/TLS encryption is possible via the public-and-private key pairing that facilitates SSL certificates. If you are running IIS7 or older, then you are forced to bind SSL certs to an IP and you can not have multiple certs assigned to a single IP. SSL certificates verify clients that owns the domain.

#WATCH MY DOMAINS SSL CERTIFICATE WINDOWS#

I am a Windows guy, so I will answer with IIS examples. If neither of these options work for you, then you would need to have two different SSL certs.ĭo I Need a Dedicated IP for Each Subdomain ?Īgain, this is a yes and no.it all depends on your web/application server. This would allow it to be used for both domain names. For example, you could tell an CA that you want a multi domain cert for domain.example and ws.mysite.example. It does this by using the Subject Alternative Name field of the cert. Your standard SSL certificate will be for single domain, say There are different types of certs you can aside from the standard single domain cert: wildcard and multi domain certs.Ī wild card cert will be issued for something like *.domain.example and clients will treat this as valid for any domain that ends with domain.example, such as or ws.domain.example.Ī multi domain cert is valid for a predefined list of domain names.

Do You Need an SSL Cert for Each Subdomain ?

Watch my domains ssl certificate