Sorry if this has been answered, I've googled and read several FAQs.

If I want to run several secured web sites on different ports on the
same web server (same IP), do I need multiple SSL certificates? What
I've read suggests that SSL is *only* associated with the FQDN of the
site, not any particular port, but I haven't seen this addressed and
wanted some confirmation.

Thanks,
Heath

I'm using IIS on Windows server 2003, if that makes any difference.

[ Post a follow-up to this message ]

htroberts@gmail.com wrote  on 13 May 2006 01:22:28 -0700:

> Sorry if this has been answered, I've googled and read several FAQs.
>
> If I want to run several secured web sites on different ports on the
> same web server (same IP), do I need multiple SSL certificates? What
> I've read suggests that SSL is *only* associated with the FQDN of the
> site, not any particular port, but I haven't seen this addressed and
> wanted some confirmation.
>
> Thanks,
> Heath
>
> I'm using IIS on Windows server 2003, if that makes any difference.

An SSL certificate is tied to a specific FQDN, or in the case of a wildcard
certificate a group of FQDNs with the same domain part. If each of your
sites to be secured has a different FQDN, and a wildcard certificate isn't
an option, you will need a separate SSL certificate for each one. The port
is irrelevant.

Dan

[ Post a follow-up to this message ]