SSL/TLS Certificates: Coverage, Hosting Setup and HTTPS Checks

An SSL/TLS certificate helps a browser authenticate the hostname of an HTTPS server. Modern HTTPS uses TLS, not the obsolete SSL protocols. Its purpose is protected transport; a certificate does not prove that a website is honest, malware-free or compliant with every security requirement.

What the certificate does

The server presents a certificate during connection setup. The browser checks the hostname and trust chain, along with validity and other applicable checks. The endpoints establish keys to protect subsequent traffic. The certificate is one part of that process, not a file that encrypts every stored item on the website.

Private keys must remain private. A CSR can be submitted to a certificate issuer, but its matching private key must not be posted in a ticket, comment or public directory.

Choose coverage, then validation

• Named hosts: check the certificate’s subject alternative names. Do not assume example.com includes www.example.com.
• Wildcard: *.example.com can cover names such as shop.example.com, but not the bare example.com or a deeper name such as a.shop.example.com without additional coverage.
• Multiple domains: a certificate can list several distinct names; verify the actual list and renewal requirements.
• Validation: DV checks domain control; OV and EV add organization identity checks. Price and validation level do not by themselves determine stronger encryption.

Use the route that matches your hosting service

In managed hosting, check the actual panel’s certificate status and available issuance options. Automatic issuance may require correct DNS and domain validation. The old claim that all InterServer plans automatically install free certificates, and its generic Advanced/SSL menu path, were not verified and are not repeated here.

For cPanel, use the account’s SSL/TLS or certificate-status interface if enabled. On a self-managed server, use a maintained ACME client or the issuer’s supported installation process for your web server and operating system. Do not install a second certificate automation system over a panel-managed one without understanding who owns renewal.

Check the complete HTTPS change

1. Test the certificate and chain on every public hostname before redirecting visitors.
2. Check HTTP-to-HTTPS redirects, forms, media and other resources for loops or mixed content.
3. For WordPress, back up first and confirm its deployment URLs. URL constants, multisite and reverse proxies may require a different procedure from editing Settings alone. Use serialization-aware replacement when stored content needs updating.
4. Monitor expiry and test renewal through the mechanism that actually manages the certificate.

Browser indicators vary: Chrome replaced its old lock icon with connection/site controls. Use those controls and the address, not a green-padlock screenshot, to inspect the connection. Do not bypass certificate warnings to sign in.

Limits and search visibility

HTTPS does not fix application vulnerabilities or certify payment compliance. It is important for safe delivery but does not guarantee Google rankings. See HTTPS and search visibility and how TLS protects a connection.

References: cPanel certificate coverage; ACME validation methods; Chrome connection indicators; WordPress serialization-aware replacement.

Reviewed October 14, 2026. No certificate issuance, production redirect or WordPress URL change was performed.