I have found a really strange thing I have not heard about.
If you visit a TLS enabled website under name "www.something.ext", but it provides certificate for "something.ext" only, I mean common name is "something.ext" and "www.something.ext" is NOT listed in alternate names, then Mozilla Firefox will report invalid certificate. Google Chrome and Internet Explorer show NO warnings. I've noticed this behavior first at https://www.vali.ge (actual content irrelevant), but pretty sure it is not web-site specific.
Usually "www.something.ext" is same site as "something.ext" but it does not have to. I consider this to be an intentional security vulnerability and really not happy about this.
Most will re-direct to the other. So if I chose to use www.domain.tld I may redirect domain.tld to www.domain.tld or vise-versa.
If you want a certificate that covers both domain.tld and www.domain.tld - those are called wild card certificates and can cover totallyrandom.domain.tld and superhappyfuntime.domain.tld and anything else you might need (email., webmail., catslol., etc...)
So a non-wildcard certificate placed on both www and non-www is in fact, not valid because a regular every day certificate is only valid for 1 url.