Is it necessary to have a site answer on HTTPS non-www? Do visitors go there?
Background on why I am asking: I have a client which have bought a new multi-domain certificate for their website. It includes the
www.example version for multiple different TLDs. The certificate does not include the domains without www so the site won't be accessible without www if the request is on HTTPS.
I have recommended the client to buy a new certificate that include the non-www domain addresses as well but they are hesitant to do so. A new certificate including twice as many domains will cost them quite a lot of money. Free certificates using Let's Encrypt is unfortunately not an option on their server.
- They have been online for 10+ years.
- They've been using HTTPS for both www and non-www before.
- The site has had redirection from non-www to www.
- They don't appear to have any important external links on HTTPS non-www.
https://www.a.tld. So I'm having a hard time answering that question. I'm looking for some general input, perhaps some insight new to me.
example.comas SAN when you buy it for
www.example.comor the opposite. You may need to shop around CAs. Also "They've been using HTTPS for both www and non-www before" so they have (or had) a certificate for the naked domain also. If they want to keep this access (only up to them and all existing inbound links) they need the appropriate certificate...