Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Post History
Relevant to you A single certificate is easier to manage, rotate, etc. Borderline Before Server Name Indication (SNI), you could only bind one certificate to each IP/Port combination on ...
Answer
#1: Initial revision
by
Michael
·
2024-03-29T14:14:41Z (8 months ago)
## Relevant to you - A single certificate is easier to manage, rotate, etc. ## Borderline - Before Server Name Indication (SNI), you could only bind one certificate to each IP/Port combination on a particular server. SNI had to be supported both on the server and on the client. If you have IE8 users visiting your web server for some reason, you'd need to use a single certificate. - If you add more domains later, separate certificates are cheaper because you don't have to re-request a CSR for an old- and new-domain cert before the normal expiration/renewal of your old one. The monetary cost isn't a factor for you, but it's up to you whether it's easiest to add a new site with its own cert or to rebind everyone. ## Not relevant to you - Multiple domains on a single certificate are expensive, just like multiple certificates are expensive. And wildcards cost more, too. You'd have to look up the pricing structure of your particular CA to price out the most affordable CSR scheme. - With several sites on the same cert, it might be weird for one site to be associated with the domain of the other. This is pretty unremarkable, though. Someone could still determine that they were both on the same IP.