Question Plesk VPS not return correct SSLCheck result

[kaji_trade]

Server operating system version

CentOS 7

Plesk version and microupdate number

18.0.71 Update #2

I looking information and not sure the behaviour is correct on system
18.0.71 Update #2
We running Godaddy VPS, host name is x.x.x.x.host.secureserver.net
Plesk manage abcxx.com, abcxx.com has dns services also as name server.
DNS record
abcxx.com A(record type) x.x.x.x (IP Address)
abcxx.com MX(reacord type) mail,abcxx.com 10
mail.abcxx.com A (record type) x.x.x.x (IP Address)
abcxx.com use let encrypted SSL
when check with sslchecker of mail.abcxx.com , which will return x.x.x.x.host.secureserver.net
sslcheck with abcxx.com return is abcxx.com certificate
sslcheck with www.abcxx.com also return www,abcxx.com certificate.
Mail.abcxx.com nslookup and dig all display correct ip and ns server
so I question is Plesk hijack the domain name server setting

 

[scsa20]

When you issue a SSL certificate through Let's Encrypt, you have an option to make a wild card certificate, include www, secure webmail, etc. If you only left the default option of "secure the domain name" then it will only secure abcxx.com. If you want to secure everything else you should put a checkmark next to each one you want (if you choose the option to secure with a wildcard, it'll automatically secure everything else but the mail domain, you still need to select to assign the certificate to the mail domain or manually do that after the fact by going to the domain > mail > mail settings and selecting the wild card certificate).

Otherwise by default it will use the self-signed certificate which is usually the server name (x.x.x.x.host.secureserver.net in this case).

As for the question if plesk is hijacking the domain name server settings, plesk doesn't do anything like that, whatever DNS settings you have configured on the server is what it is, and if you updated the registrar to use your server for the DNS then sure, but in your case it doesn't matter which DNS service you use since it's a simple configuration change within the mail settings (if you had gotten a wild card certificate issued) or having it reissued with the wild card or choosing to make sure mail.whatever is secured as well.