Hi @cofcqld. Thanks for being part of GoDaddy Community! The WWW host name for your domain will always be covered with any SSL Certificate you have through us. This shouldn't take up any of our SAN slots, though. If you're seeing that, then definitely give our support team a call so they can see what's going on. Hope that helps clear things up for you.
Hi. Thank you for your reply but you haven't answered the question.....
"I dont need or want this extra SAN and it does not show up in the Rekey/Manage-Add SAN console. How can I remove this SAN"
So after several days on this problem and many different agents, I can say for sure that the SAN SSL certificate does not cover both the www and non-www domains.
I referenced this post in a chat and was told this:
"it's both yes and no
common name, it will cover non-www and www
SANs, it does not."
It does on the main domain on that SSL Certificate (both www and non-www). But it doesn't work for the domains on the SAN.
For example I have:
I have the same question about the added www. to the certificate when the CSR I created did not have the www. We run periodic vulnerability scans on our systems and common name mis-match is something we get reports on because of the www. in the SAN of the certificate. I see this post was resolved but I don't see a resolution to remove the www. attribute. Is there a way I can remove the extra www. attribute?
Just got this to work. What I ended up having to do is request the access from the main account instead of having the users request access from their accounts. So if you have already delegated access to other users, delete their access and then initiate the invite from the account you want to delegate.