An SSL certificate for a website enables HTTPS, helps visitors verify they are connecting to the intended hostname, and encrypts traffic between the browser and server. This practical checklist explains how to choose the right certificate, install it on common hosting setups, complete validation, renew it safely, and troubleshoot HTTPS certificate errors without overlooking DNS or application settings.
Overview
“SSL certificate” remains the common term, although modern websites use TLS protocols. The certificate is one part of HTTPS: it contains identity information for one or more hostnames, while the web server uses it with TLS to establish an encrypted connection. A valid certificate does not make an application secure by itself. You still need secure software, strong access controls, current dependencies, backups, and sensible DNS management.
Before buying or installing anything, list the exact hostnames your website uses. A certificate for example.com may not automatically cover www.example.com, and neither hostname necessarily covers shop.example.com. Check the certificate’s subject alternative names (SANs) and confirm that every public hostname is included. A wildcard certificate such as *.example.com commonly covers one level of subdomain, such as shop.example.com, but not the bare domain or a deeper name such as api.shop.example.com. Confirm the provider’s coverage rules before relying on a wildcard.
Certificate types at a glance
| Type | Typical coverage | Useful when | Check before choosing |
|---|---|---|---|
| Single-domain | One specified hostname or domain, according to the certificate terms | A small site has a clearly defined public address | Whether both the bare domain and www are included |
| Multi-domain (SAN) | Several listed hostnames, which may use different domain names | One service operates across multiple domains or subdomains | The hostname list and how additions are handled |
| Wildcard | Many subdomains at one level beneath a domain | A platform creates multiple first-level subdomains | Whether the bare domain and deeper subdomains require separate coverage |
| Organization-validated | Hostname coverage plus organization validation, subject to the issuer’s process | An organization needs a certificate issued through a business validation workflow | Validation records, ownership responsibility, and renewal effort |
For many websites, the practical decision is not the label but the coverage, installation method, renewal support, and control you need. Automated certificates can be convenient when your hosting platform supports automated validation and renewal. Manually managed certificates may be appropriate for controlled infrastructure, but they require a documented renewal process and an owner who can replace the certificate before it expires.
Checklist by scenario
Before installation
- Write down every public hostname: the bare domain,
www, application subdomains, API endpoints, and any names used by staging or customer-facing services. - Confirm which server, load balancer, CDN, or hosting platform terminates HTTPS. Installing a certificate on the origin server does not help if a different edge service handles visitor connections.
- Check DNS records and make sure each hostname points to the intended service. If validation uses DNS, identify who can create the required record.
- Confirm that you have an administrative route to the hosting panel, server, container, or deployment platform.
- Record the current certificate’s expiration date, covered names, issuer, and renewal method. Keep this information with your domain and hosting records.
Shared hosting or a hosting control panel
- Open the hosting panel’s SSL, Security, or Domains area and select the domain or hostname.
- Choose the platform’s managed certificate option if it supports automated issuance and renewal, or prepare the certificate, private key, and intermediate chain supplied by your certificate provider.
- Complete the requested validation. Email, file-based, and DNS validation methods may be offered; follow the exact hostname and record instructions shown by the issuer or host.
- Install or activate the certificate for every required hostname, not only the default domain.
- Test both the bare domain and
www, then verify that the intended HTTP-to-HTTPS redirect works. - Check the panel for a renewal status or deployment log. A certificate that is issued but not deployed to the active site still produces an error.
Cloud hosting, a virtual server, or a reverse proxy
- Identify the TLS termination point. It may be a web server such as Nginx or Apache, a reverse proxy, an ingress controller, a load balancer, or a CDN.
- Store the private key with restricted permissions and keep it out of public repositories, images, tickets, and chat messages.
- Install the certificate chain in the order required by the platform. A missing intermediate certificate can cause some clients to reject an otherwise valid certificate.
- Configure every listener or virtual host that serves the covered hostname. Multiple sites on one server can otherwise present the wrong certificate.
- Reload the service using its documented configuration command, and inspect logs if the reload fails.
- Test from outside the server or network. A local browser test can hide DNS, firewall, proxy, or CDN configuration issues.
- Automate renewal only after testing the deployment hook. Renewal should replace the certificate and reload the correct service, not merely create a new file on disk.
During a website migration
Install and test the certificate on the destination before changing DNS. Verify the destination with a temporary hostname, controlled DNS record, or the hosting provider’s preview method. Confirm that the new server contains the complete certificate chain, supports all required hostnames, and redirects consistently. Keep the old HTTPS service available until traffic has moved and monitoring shows that the new endpoint is responding correctly.
For a broader move, use the website migration checklist alongside this certificate checklist. It covers related DNS, data, and traffic considerations that HTTPS alone does not address.
For business email
Website certificates and email authentication are separate. Installing HTTPS does not configure MX, SPF, DKIM, or DMARC records. When changing DNS during a certificate or hosting project, review your mail records carefully so a website change does not interrupt business email. The custom email setup guide provides a separate DNS checklist.
What to double-check
Renewal and validation checklist
- Confirm the renewal method and its owner. Automated renewal still needs working DNS, validation permissions, and a successful deployment step.
- Check that the validation record or file is available to the issuer when renewal runs. Do not remove a DNS validation record if the platform needs it for future renewals.
- Verify that the account has permission to update the certificate on the active endpoint.
- Test renewal in a safe environment when the platform provides a dry run or staging option.
- Set monitoring for expiration and certificate-name changes. Check from outside your hosting environment.
- Keep a short recovery procedure: where the certificate is stored, how to restore the previous configuration, and who can approve an emergency change.
Mixed-content warnings
Mixed content occurs when an HTTPS page requests an asset over HTTP. Typical sources include images, stylesheets, JavaScript, fonts, embedded media, analytics scripts, API calls, and hard-coded links in a database. Browsers may block active content or show a security warning even when the main certificate is valid.
- Open the browser developer tools and inspect the Console and Network panels for HTTP requests.
- Search application templates, content fields, environment variables, and scripts for
http://URLs. - Change internal absolute URLs to HTTPS or use relative or configuration-based URLs where appropriate.
- Confirm that third-party resources support HTTPS before changing the reference.
- Clear application, page, CDN, and browser caches, then retest in a private window.
Do not use a blanket redirect as a substitute for fixing every asset reference. The redirect may hide the source of the problem and can fail for APIs, fonts, or blocked resources.
Browser error troubleshooting
| Browser symptom | Likely area to inspect | First action |
|---|---|---|
| Certificate expired | Renewal job, deployment, server clock, or CDN edge | Inspect the certificate presented by the public hostname and renew or deploy it at the active endpoint. |
| Hostname mismatch | Certificate SANs or virtual-host routing | Compare the requested hostname with the names on the presented certificate. |
| Certificate not trusted | Incomplete chain, incorrect certificate, or client trust store | Install the required intermediate chain and test from more than one client. |
| HTTPS works on one hostname but not another | DNS, redirects, or separate listeners | Test each hostname independently and confirm each one reaches the intended TLS endpoint. |
| Page is not fully secure | Mixed content | Use developer tools to find and replace HTTP asset and request URLs. |
If only some visitors see an error, compare DNS responses, IPv4 and IPv6 endpoints, CDN locations, and cached configurations. A certificate can be correct on one server while an older endpoint still presents an expired or mismatched certificate.
Common mistakes
- Covering only one hostname: A certificate installed for
example.comdoes not prove thatwww.example.comor a new subdomain is covered. List names before issuance. - Confusing HTTP redirects with certificate coverage: A redirect cannot repair a certificate error on the original HTTPS connection. The certificate must be valid before the redirect is processed.
- Installing at the wrong layer: If a CDN or load balancer terminates TLS, updating only the origin server will not change what visitors see.
- Forgetting the intermediate chain: Some clients may fail when the server sends only the leaf certificate.
- Assuming issuance equals renewal: A newly issued certificate is not useful until it is deployed, and a renewal is incomplete until the live endpoint serves it.
- Exposing the private key: Treat the key as a secret. If it may have been disclosed, follow the issuer or platform’s replacement and revocation procedure.
- Changing DNS without checking email: Website and mail records can coexist, but an unplanned DNS change can affect both. Record existing records before editing them.
- Testing only from inside the network: Proxies, split DNS, and cached responses can make an internal test appear successful while public visitors receive a different configuration.
When to revisit
Use this checklist before a certificate renewal, after adding a subdomain, when moving web hosting, or whenever a browser reports an expired, invalid, or insecure connection. Revisit it after changing a CDN, reverse proxy, load balancer, DNS provider, deployment pipeline, or web server configuration.
Review the process at least during each planned infrastructure cycle and whenever your hosting platform changes its certificate workflow. Certificate authority validation requirements, browser behavior, supported TLS settings, and control-panel procedures can change, so verify current instructions in your issuer and hosting documentation rather than relying on an old screenshot or script.
For a practical final pass, schedule these actions:
- List every public hostname and its TLS termination point.
- Check the live certificate’s names, chain, and expiration from outside your network.
- Run or simulate renewal and confirm that deployment reaches the active endpoint.
- Test redirects, forms, APIs, assets, and third-party integrations over HTTPS.
- Record the result, owner, renewal method, and recovery steps in your domain and hosting documentation.
Keep this article with your broader SSL certificate errors and renewal checklist so the next migration or renewal starts with verified information rather than guesswork.