Closed. This question is not about programming or software development. It is not currently accepting answers. This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered. Closed 8 hours ago. Improve this question ISSUE I've recently transferred a domain from Namecheap to iwantmyname and am using external nameservers to host my site on WordPress. The domain resolves and is accessible via Google Chrome on some networks, but Safari (and other browsers) often show the error "Can't establish a secure connection to the server." Furthermore, the site works on some Wi-Fi networks but fails to load on others. Upon running an SSL Labs test, I found that the certificate mismatch is causing the site to be untrusted by Mozilla, Apple, Android, Java, and Windows. The SSL certificate shows: Common Name: *.wordpress.com Alternative Names: *.wordpress.com, wordpress.com The issue seems to be related to the SSL certificate, as it is intended for *.wordpress.com, but my custom domain does not match this certificate. Additionally, I ran the domain through McAfee's domain lookup tool, and it categorized the domain as PUPs (Potentially Unwanted Programs)** and set the risk level to Medium. This could be contributing to network-specific blocking, but I’m not sure how to resolve this issue. Why is my custom domain still using a wildcard *.wordpress.com SSL certificate after the transfer, and how can I properly configure the SSL certificate for my custom domain across all browsers and networks? Could the McAfee domain categorization as a PUP be contributing to the issue, and what steps should I take to resolve that? What should be the next steps to resolve the mismatch and ensure secure access to my site across all devices and networks? I Have Done DNS Configuration Check: Verified that the domain's nameservers are correctly set to WordPress external nameservers. Used DNS propagation tools to confirm that DNS changes have propagated successfully. SSL Certificate Test: Ran an SSL Labs test and found a mismatch between the SSL certificate’s common name (*.wordpress.com) and my custom domain. This certificate works for WordPress subdomains but not for my domain. Browser and Network Specific Issues: The site works fine on Chrome but not Safari. The site is accessible on some Wi-Fi networks but not others. I’ve tried clearing caches, switching networks, and testing in incognito/private mode, all with mixed results. Testing DNS Settings: Changed DNS settings on the device to Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1), which sometimes resolves the issue but not consistently across all devices or networks. SSL/TLS Compatibility: Checked that TLS 1.2/1.3 is supported, but the issue persists with certain networks. VPN and Alternate Networks: When using a VPN or switching to mobile data, the site works, which leads me to believe it could be a network-specific issue. McAfee Domain Lookup: Looked up the domain in McAfee's domain lookup tool, which categorized it as PUPs (Potentially Unwanted Programs) with a Medium Risk level. This could be causing certain networks to block access to the site.