Special subdomain name for https

https://secure.mywidgets.com vs https://www.mywidgets.com

[Morgenhund]

I'm going to add a subdomain "secure." to my domain name (say, "mybluewidgets.com") for all links, accessed through https.

"secure" will be just an alias for "www", but certificate will be issued for this name.

Reason is, to make customers more aware of site's security measures and thus improve site's credibility.

If there are any reasons I should not to?

Opinions welcome.

[RedWolf]

I'm not sure what your setup is for the subdomain, but that can have an impact on the pages you put there. On my host, subdomains are totally seperate accounts with their own IP address and security which means that anything on them including images need to be hosted there. It doesn't sound like this is the case in your setup, but it is something to think about. Either way, remember to call all images using https instead of http.

[Morgenhund]

Yes, in my case subdomain is just parked on top on my main domain.

Regarding images: why is it neccessary?

I already know, links under images should be https, to avoid pop-up messages "the page contains both secure and nonsecure items" by browser.