Hi vitkoz,

No, that is not possible unless you use a wildcard IIS certificate.  I would not use a wildcard certificate for two different physical entities, but it can be done technically.

A shared SSL certificate like you described would still be implemented with a wildcard SSL cert.  It would just be setup on a shared domain.

There are lots more problems than just trust when using a shared SSL host.  For one, you can't use it for login or registration on your site because it is on a different host.domain name.  Another problem is getting the details of the transaction back from the domain that is hosting the shared certificate.

If anyone is thinking about a shared SSL solution for e-commerce, they would be much better off using a trusted third-party payment provider like PayPal.  in fact, using PayPal would probably be a good option to give your customers for any site.  Even GoDaddy and many other widely known sites offer PayPal as a form of payment.

Well, on one of the sites I maintain for a client, I have a shared SSL but only on one page - the one that collects CC info and passes it to LinkPoint. There is not need for login, etc. Just that kind of site. So, shared SSL works out fine for that scenario.

Of course, you are completely correct in your statements - I was just bringing an example of a shared SSL being a legit solution. :)

As far as PayPal and Google checkout - I love to be able to just login and pay instead of pulling my credit cards and, especially, submitting that info on some site I know nothing about. Just think about what happens if a merchant implements that Email Payment Provider that's available in Core Store module, for example. That email gets sent via unsecured connection in an unencrypted format - read-and-use for all...

I wish sites like Amazon would already start accepting PayPal and Google...