Website SSL Certificates for Small Business: Renewal, HTTPS and Common Failure Points

Your website SSL certificate protects the connection between your visitors and your site. This guide explains renewal, HTTPS and common failures involving DNS, hosting and mixed content.

HTTPS is now normal infrastructure

A website SSL certificate allows a browser to establish an encrypted HTTPS connection and verify the hostname it reached. For a business website, HTTPS should be the normal state rather than an optional security badge. Problems usually arise from renewal, DNS changes, hostname mismatches or conflicting configuration.

Your website SSL certificate must cover the right names

A certificate must cover the hostname visitors use, such as example.com and possibly www.example.com. Redirecting between those names does not remove the need for the initial HTTPS connection to be valid. Check which variants the site actually serves.

Monitor website SSL certificate renewal

Many hosts issue free certificates automatically, but renewal can fail if DNS no longer points correctly or validation is blocked. Do not assume automation means certificates can never expire. Monitoring expiry and testing HTTPS after infrastructure changes is sensible.

DNS must lead to the right server

A perfectly configured certificate on the new host does not help visitors who are still reaching the old server. After a migration, confirm DNS resolution and allow for caching. The DNS propagation guide explains why different networks can temporarily disagree.

Cloudflare adds another TLS layer

When Cloudflare proxies a site, there is a browser-to-Cloudflare connection and a Cloudflare-to-origin connection. Check the origin certificate before choosing an encryption mode. Cloudflare’s Full (strict) guidance requires a valid, unexpired origin certificate covering the hostname. Confirm those requirements before changing the setting to avoid connection errors.

Mixed content is different from an invalid certificate

A page may load over HTTPS but still request images, scripts or styles over HTTP. Browsers can block or warn about those resources. Fix the underlying URLs rather than disabling HTTPS. WordPress migrations are a common time for old absolute HTTP references to surface.

Redirects should be simple

Choose the canonical HTTPS hostname and redirect alternatives consistently. Avoid duplicate redirect logic across WordPress, the server and CDN unless there is a clear reason. If the browser reports too many redirects, see our redirect-loop guide.

Diagnose website SSL certificate warnings

Expired, untrusted and hostname-mismatch errors have different causes. Record the browser message and inspect the certificate before changing WordPress. Our SSL error troubleshooting guide covers the common patterns.

Treat SSL as part of hosting ownership

Know who manages the certificate and what happens during a host move. TempWebz provides website hosting and technical support for businesses that need HTTPS, DNS and WordPress checked together.

Website SSL certificate checks after a host move

Test the exact addresses your customers use, including the main domain, any www version and important subdomains. A working homepage does not prove every hostname has valid HTTPS. Keep the old hosting arrangement available during a planned transition until you have checked the new destination and allowed for DNS caching.

Record the certificate expiry date, the names it covers and the system responsible for renewal. If your site uses a proxy, distinguish the public certificate from the origin certificate. Their issuers and expiry dates may differ. Ask the host which renewal process it manages rather than assuming one dashboard covers both connections.

What to send your support provider

Send the exact affected URL, the browser error text, the time you saw it and whether another device or network has the same problem. Mention recent changes to DNS, hosting, redirects or proxy settings. These details help support distinguish a server issue from a local clock or network problem.

Do not send private keys, passwords or complete account exports in an ordinary email. Share a screenshot of the public warning if helpful, but remove unrelated tabs and account details. Never ask customers to bypass a browser security warning to complete a form or payment.

Verify recovery before closing the issue

After the provider fixes the cause, open the affected URL again in a fresh browser session. Check the certificate names and expiry, then follow the normal customer journey. Test the contact page and any embedded resources as well as the homepage. Use browser developer tools to check for remaining mixed-content errors if you have the technical skills.

Keep a short incident record with the cause, the correction and who owns future renewal checks. Review that record before the next hosting or DNS change. A website SSL certificate needs ongoing ownership even when the host automates most of the work.