Thanks for your time. I’ve secured the mail layer via Plesk and fully reissued the SSL certificate for yieldandco.com. During the reissue, I made sure to check all available boxes—including coverage for both webmail and mail services—to ensure complete domain-level protection.
Despite that, the issue persists due to a mismatch between the certificate domain and the server hostname. The certificate is valid for yieldandco.com, but the server is identifying itself as johnny.heliohost.org. This discrepancy is causing the CRM’s email integration to fail during SSL validation. It’s the same mismatch flagged in the SSL Labs report, which I’ve reviewed in detail—though the full output exceeds the attachment size limit.
In the meantime, I’ve already initiated the nameserver change back to Porkbun—so I can route email independently. This allows me to begin propagation and make necessary changes today.
I’d prefer to move email back to HelioHost once the SSL and routing issues are resolved, but I needed the propagation window to begin so I can keep things moving.
To that end, I’d appreciate it if you could provide the necessary DNS details—such as the correct A record or IP address—so I can continue hosting the website on HelioHost while managing email routing externally.
Also, could you confirm whether HelioHost supports SNI? If so, I’d like to understand how to configure the server to present the correct domain-specific certificate during the TLS handshake. That would likely resolve the mismatch and restore integration.
Thanks again for your support—I’m happy to provide any additional logs or test results if helpful.