Website SSL Certificate Guide: HTTPS Setup, Renewal, and Common Errors
SSL certificatesHTTPSwebsite securityTLScertificate renewalbrowser warnings

Website SSL Certificate Guide: HTTPS Setup, Renewal, and Common Errors

mmodest.cloud Editorial Team
2026-11-15
7 min read

Use this practical SSL certificate checklist to set up HTTPS, prevent browser warnings, verify renewals, and fix common TLS errors.

An SSL certificate enables HTTPS between a visitor’s browser and your website, but installing one is only the first step. This reusable checklist explains how to choose a certificate, complete an HTTPS setup, verify renewals, resolve common browser warnings, and know when your configuration needs another review.

Overview

An SSL certificate is used with TLS, the encryption protocol that protects data exchanged over HTTPS. Although people still commonly say “SSL certificate,” modern websites use TLS. A correctly configured certificate helps a browser verify that it is connecting to the intended hostname and allows the connection to be encrypted.

HTTPS does not replace secure application design, strong passwords, software updates, backups, or access controls. It is one layer of website security and trust. It also needs to cover every hostname that visitors or site components use, such as example.com, www.example.com, and relevant subdomains.

Certificate types at a glance

Certificate typeWhat it validatesTypical useWhat to check
Domain Validation (DV)Control of the domain or hostnamePersonal websites, blogs, applications, and many small business sitesWhich exact hostnames are included and how validation is completed
Organization Validation (OV)Domain control plus organization informationOrganizations that want additional identity validation for their certificate recordsWhether the organization details are accurate and kept current
Extended Validation (EV)A more detailed organizational validation processCases where an organization has a specific identity-validation requirementHow browsers and the chosen certificate provider present the validation
WildcardA base domain and eligible subdomains, subject to certificate rulesSeveral related subdomains under one domainWhether the required level of subdomains is covered
Multi-domain (SAN)Multiple named hostnames in one certificateSites using several domains or unrelated hostnamesThe complete hostname list and its renewal process

The right choice depends on your hostnames, infrastructure, validation requirements, and renewal process. A basic certificate may be appropriate for one website, while a platform with many subdomains may need a different certificate design or automated certificate management.

Checklist by scenario

Before installing an SSL certificate

  • List every public hostname that should use HTTPS, including the root domain, www, application subdomains, staging addresses, and API endpoints where applicable.
  • Confirm where DNS is managed and where the website is hosted. The certificate may be installed at a hosting panel, reverse proxy, load balancer, content delivery layer, or web server rather than on the application itself.
  • Check that each hostname resolves to the intended service. If you recently changed nameservers or DNS records, use a DNS checker to compare results from multiple locations.
  • Identify who controls the certificate account, domain DNS, hosting account, and renewal notifications. Avoid a setup that depends on one inaccessible personal mailbox.
  • Record the certificate’s covered names, issuer, expiration date, installation location, and renewal method in your infrastructure documentation.

If the domain is not yet connected to hosting, first review how to point a domain to web hosting. Correct DNS and certificate coverage are related but separate tasks: DNS directs traffic, while the certificate authenticates and encrypts the HTTPS connection.

Installing HTTPS on a hosting account

  1. Choose the certificate and validation method. Your hosting provider may offer managed issuance, or you may need to provide a certificate, private key, and intermediate certificate chain. Follow the provider’s current instructions.
  2. Complete domain validation. Depending on the provider, this may involve a DNS record, an HTTP file, or an email process. Make sure validation is performed for the correct hostname and that temporary DNS or web-server changes do not remove existing records.
  3. Install the certificate with its private key and chain. Never publish the private key in a repository, ticket, chat message, or client-side code. If a hosting panel manages the private key, use the panel’s access controls and documentation.
  4. Test each covered hostname. Open both the root domain and alternate hostnames over HTTPS. Check that the certificate subject or SAN list includes the hostname visitors are using.
  5. Redirect HTTP to HTTPS. Use a permanent redirect where appropriate, after confirming that the HTTPS version works. Update canonical URLs, sitemap URLs, application settings, and public links to use HTTPS directly.
  6. Check the application. Sign-in forms, payment flows, images, scripts, fonts, embedded content, webhooks, and API calls should use HTTPS where required.

For WordPress and other content management systems

  • Update the site URL and home URL through the approved administration method rather than making an untested database change.
  • Review theme, plugin, media, custom CSS, and JavaScript references for hard-coded http:// URLs.
  • Clear relevant caches only after confirming the HTTPS version is available. Test an incognito or separate browser session to avoid relying on an old cached redirect.
  • Check administrative login, forms, feeds, image URLs, and any external integrations separately.

For a broader site launch or migration, pair this checklist with a staging environment and a tested backup. The cloud hosting staging guide and backup and restore testing checklist can help reduce avoidable production changes.

For renewal

  • Confirm the renewal method is active and that its validation records, credentials, and permissions still work.
  • Verify that notifications go to a monitored address and are not limited to a former administrator.
  • Check whether the renewed certificate will retain the same hostname list. New subdomains may require a new certificate configuration.
  • Test renewal in a non-production environment when your provider supports it, or schedule a controlled check after renewal.
  • After renewal, inspect the certificate served by every public endpoint, including proxies, load balancers, and separate application servers.

What to double-check

Redirects and canonical URLs

Visit the HTTP and HTTPS versions of the root domain and common variants. The intended HTTP version should reach the intended HTTPS URL without a redirect loop. Check that the application does not alternate between HTTP and HTTPS because it is behind a proxy that is not passing the original protocol correctly.

Update canonical tags, structured data URLs, XML sitemaps, robots directives, advertising or analytics settings, and internal links where they contain absolute URLs. A redirect can protect visitors, but direct HTTPS references reduce unnecessary requests and make the preferred URL clearer.

Mixed content

Mixed content occurs when an HTTPS page requests a resource over HTTP. Browsers may block active content such as scripts and frames or warn about other resources. Use the browser’s developer tools to identify the exact URL, then update the source, plugin, theme, CMS setting, or third-party integration that created it. Do not solve an unknown mixed-content issue by blindly changing every URL in a database.

Certificate details

  • Hostname: The certificate must cover the exact hostname in the address bar.
  • Validity: Confirm the start and expiration dates, along with the server’s clock.
  • Chain: The server should provide the required intermediate certificates so clients can build a trusted chain.
  • Endpoint consistency: Different servers or network layers should not present different, outdated certificates unintentionally.
  • TLS configuration: Use the hosting provider’s current recommendations for protocol versions, cipher settings, and key management. Avoid copying an old configuration without checking that it remains supported.

Common mistakes

The certificate is expired.
Check the renewal job, validation record, account permissions, and notification history. Installing a new certificate is not enough if a proxy or secondary server still serves the expired one.
The hostname does not match.
The certificate may cover www.example.com but not example.com, or it may omit a newly created subdomain. Review the certificate’s SAN list and issue a certificate that covers the required names.
The certificate chain is incomplete.
The server may have the site certificate but not the required intermediate certificate. Use the hosting provider’s full-chain installation format and test from more than one client type.
HTTPS works on one hostname but not another.
Compare DNS targets, virtual-host configuration, proxy routes, and certificates for each hostname. Do not assume that a certificate installed for one endpoint is automatically available on another.
A redirect loop appears.
Inspect application URL settings and proxy protocol forwarding. A server may think every request is HTTP even after the visitor connected through HTTPS.
The browser still shows a warning after installation.
Test in a fresh session and inspect the exact warning. It may indicate mixed content, an expired certificate, an untrusted chain, a hostname mismatch, or a certificate being served by the wrong endpoint.

For a focused diagnostic sequence, see the SSL certificate troubleshooting guide. Avoid disabling browser security checks as a permanent workaround; determine which certificate, DNS, server, or application layer is responsible.

When to revisit

Review this checklist before the certificate’s renewal window, after any domain or DNS change, and whenever hosting infrastructure is migrated. It should also be part of the launch process for a new subdomain, application, staging environment that becomes public, or business email and web-domain change.

Revisit the configuration after changing a hosting panel, reverse proxy, CDN, load balancer, WordPress installation, certificate provider, or automated deployment process. A workflow that worked on one server may not transfer correctly to another.

As a practical recurring check, keep a small certificate inventory with these fields:

  • Hostname or hostname group
  • Certificate type and covered names
  • Installation endpoint
  • Renewal and validation method
  • Expiration date and notification owner
  • Last successful HTTPS and renewal test

Before closing a maintenance task, open the principal HTTPS URLs, test a form or login where appropriate, inspect the browser certificate details, and confirm that no mixed-content errors remain. If DNS has changed, compare authoritative records and resolver results using a DNS propagation checker guide. This final review turns HTTPS from a one-time installation into a maintained part of your website security process.

Related Topics

#SSL certificates#HTTPS#website security#TLS#certificate renewal#browser warnings
m

modest.cloud Editorial Team

Technology Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.