Then it is no my solution!
I need of MULTIPLE ssl certificate for multiple non related site under the same IIS application

IIS APPLICATION A (all in the same folder)
> aaa.com   >SSL1 personalized for aaa.com
> bbb.com   >SSL2 personalized for aaa.com
> ccc.com    >SSL3 personalized for aaa.com

I already work with one SSL in the same IP for  multiple site, but now my problem is that my multiple site are the same for IIS (1 dotnetnuke installation may have multiple site on the same installation), one IIS application with multiple non-related sites.
Now I have explained myself better?

Yes, I agree with You to use multiple single domain certs with one IP per cert. But if I'm not mistaken, IIS can install only one certificate for each application.

Here is my setup: DNN 5.5.1 //IIS 7.5 behind a firewall; a single NIC on the server

• http://Portal.domain.com
• 6 "child" sites (all Aliased to www.child1.com; www.child2.org etc.
• SSL Cert issued to "portal.domain.com"
• Installed cert to IIS and bound to 443; turn on SSL in DNN; no pages set to require SSL yet site slows to a crawl
• Restart IIS and login issues result
• Pages seem to "loop" from the internal/private IP (10.10.40.100)  to the external/public IP (#.#.#.110)

Also, from SQL query some "null" sites have SSL "required"- probably old early DNN 4 pages from experiments
Second point of interest: I have another (ASPX) site on another server (IIS5) behind the same firewall configuration. I can browse that site using HTTPS (not required) as well as HTTP, but the DNN site cannot be browsed using HTTPS: even when SSL is turned off.

1. Why is this so difficult?
2. Is my configuration so poor that looping results?
3. Should I remove all "null" sites and their tabs from SQL table?