.net website using certificate with .com

I found a website where all browsers navigate to just fine and do not complain about the certificates. When i inspect the certificate i noticed something i hadn't thought i would see. the website foo.net is using a certificate that was issued to common name .foo.com . Is this normal to do? I found it because i was using python to check the certificate expiration and it resulted in a "ssl.CertificateError: hostname 'foo.net' doesn't match either off '.foo.com', 'foo.com'".

I am not a certificate expert so not sure what the pro's and con's or when this is normally done if at all.