SSL Certificate Management for Websites: Inventory, Renewal, ACME, and CDN Configuration Guide
SSLTLScertificatesACMECDNDNSwebsite security

SSL Certificate Management for Websites: Inventory, Renewal, ACME, and CDN Configuration Guide

OOpenWebHosting Editorial Team
2026-11-19
8 min read

Use this practical checklist to inventory, renew, deploy, and troubleshoot SSL certificates across websites, subdomains, CDNs, and hosting providers.

Managing SSL certificates across several websites is less about installing one certificate and more about maintaining an accurate system. This guide provides a reusable SSL certificate inventory, renewal and installation checklists, ACME workflows, CDN and origin checks, and troubleshooting steps for hostname, chain, and mixed-content errors.

Overview

An SSL certificate enables encrypted HTTPS connections and helps a browser verify that a certificate is valid for the requested hostname. In practice, certificate management also involves DNS records, hosting configuration, private-key protection, renewal automation, CDN settings, redirects, and monitoring.

The main operational risk is not usually the first installation. It is losing track of which certificate covers which domain, where the private key is stored, who receives renewal notifications, or whether a CDN is presenting a different certificate from the origin server. A simple inventory and a repeatable renewal process reduce these failures.

Before changing a certificate, identify the traffic path:

  1. Does the visitor connect directly to the hosting server?
  2. Does a reverse proxy, load balancer, or CDN terminate TLS first?
  3. Does the origin server also require HTTPS?
  4. Which system controls DNS and which system controls the certificate?

Keep those answers with the site’s hosting and DNS documentation. For broader DNS ownership and registrar planning, see the best domain registrar guide for developers and agencies.

Certificate type comparison

Certificate typeTypical coverageUseful whenOperational consideration
Single-domainOne specific hostname, depending on the certificate orderA site has a small, stable hostname setAdditional hostnames require separate coverage or a new certificate
WildcardA domain and its matching subdomains at one label levelYou operate many predictable subdomainsIt does not automatically cover every deeper or unrelated hostname
Organization-validatedCertificate coverage selected during issuanceYour organization needs an additional validation process for its use caseValidation and renewal requirements may be more involved than an automated flow
Automated ACMEUsually single-domain or multi-domain coverage, depending on the client and orderYou want repeatable issuance and renewal through a supported ACME clientDNS or HTTP challenge access, permissions, and deployment hooks must remain reliable

Choose coverage based on actual hostnames and operational needs, not on the label alone. Confirm the certificate authority’s current validation rules, supported challenge methods, and browser compatibility before standardizing a workflow.

Checklist by scenario

1. Build an SSL certificate inventory

Record one row per certificate or certificate deployment. The following fields are enough for most small teams:

  • Primary domain and every covered hostname
  • Certificate type and issuing certificate authority
  • Issue date and expiration date
  • Renewal method: hosting panel, ACME client, CDN, or manual
  • Validation method: HTTP, DNS, or another supported method
  • Where the certificate is installed: CDN, load balancer, web server, or hosting panel
  • Where the private key is stored and which people or systems can access it
  • Renewal owner, backup owner, and notification destination
  • Last successful renewal test and the next review date

Do not store private keys in a shared document or public repository. The inventory should identify their location and owner without exposing secret material.

2. Renew through a hosting panel

  1. Confirm that the panel lists every required hostname, including the preferred and alternate versions of the site if both are used.
  2. Check that DNS points to the system expected to answer the validation request.
  3. Run the panel’s renewal or reissue process in advance of the expiration date.
  4. Verify that the new certificate and complete chain are installed on the correct virtual host.
  5. Test the public HTTPS endpoint from outside the hosting account.
  6. Record the result and update the inventory.

Panel automation can fail when a domain has moved, DNS is managed elsewhere, a validation path is blocked, or the panel renews a certificate that is not the one being served publicly.

3. Renew with an ACME client

ACME certificate hosting is most reliable when issuance and deployment are treated as two separate steps. The client must first prove control of the hostname, then place the renewed certificate and key where the web server, proxy, or load balancer can use them.

  1. List the exact hostnames required by the service.
  2. Select a supported ACME client and configure its account credentials securely.
  3. Choose an HTTP-based or DNS-based challenge according to the network design.
  4. Grant only the DNS or filesystem permissions needed for validation and deployment.
  5. Configure a renewal job and a deployment hook where the server needs a reload.
  6. Test renewal in a safe environment or with the client’s supported dry-run mechanism.
  7. Confirm that the running service presents the new certificate after deployment.
  8. Send renewal failures to a monitored destination rather than relying only on local logs.

For a wildcard certificate, DNS validation is commonly the relevant workflow, but the exact challenge support and DNS integration depend on the ACME client and provider. Review current documentation before granting API access to a production DNS zone.

4. Install a certificate manually

Manual installation may still be necessary during a migration, on a system without an ACME integration, or when a certificate is issued through a separate process. Match the certificate to its private key, install the required intermediate chain, assign it to the correct virtual host, and reload the service. Then test the public hostname rather than assuming a successful reload means the correct certificate is being served.

5. Configure a CDN and origin server

When a CDN terminates HTTPS, there may be two TLS connections: the visitor-to-CDN connection and the CDN-to-origin connection. Check both independently.

  • Confirm the CDN certificate covers every public hostname.
  • Confirm the CDN serves the intended certificate after DNS changes.
  • Choose an origin mode that matches the certificate and trust requirements on the server.
  • Ensure the origin certificate covers the hostname used by the CDN to connect.
  • Check that the origin firewall allows the CDN’s documented connection path.
  • Verify that redirects do not send HTTPS requests back to HTTP at the origin.
  • Renew CDN-managed and origin certificates separately unless the platform explicitly links them.

Document whether the origin is publicly reachable or intended to accept traffic only through the CDN. This distinction matters during troubleshooting and migration.

What to double-check

Hostname coverage

Check the exact hostname in the browser address bar, including subdomains. A certificate for example.com should not be assumed to cover www.example.com, and a wildcard should not be assumed to cover deeper levels or a different domain. Include staging, API, mail, and administrative hostnames only when they genuinely use the same certificate and security boundary.

Certificate chain

A server may have the correct leaf certificate but still produce trust errors if it does not send the required intermediate certificates. Confirm that the server or CDN is configured with the appropriate full chain. Test from more than one client or network when possible, because cached intermediates and local trust stores can hide an incomplete deployment.

Private-key pairing and permissions

Verify that the private key belongs to the certificate being installed. Keep key files readable only by the service or deployment account that needs them, and remove obsolete copies from temporary directories and old servers according to your retention policy.

Mixed content

HTTPS can be valid while a page still loads images, scripts, stylesheets, fonts, or API calls over HTTP. Use browser developer tools to identify blocked or upgraded requests. Update application settings, absolute URLs, database content, templates, and third-party integrations. A redirect alone does not rewrite hard-coded HTTP references inside page content.

Monitoring and ownership

Use external HTTPS checks to verify expiration, hostname coverage, response status, and certificate presentation. Pair those checks with an owner and an escalation path. An uptime monitoring system can help detect a failed deployment, but it should complement the certificate inventory rather than replace it; see the website uptime monitoring comparison for related operational checks.

Common mistakes

  • Tracking only expiration dates: A certificate can be unexpired but installed on the wrong virtual host or missing a required hostname.
  • Renewing without deploying: The renewal job may create a new file while the running web server continues using the old certificate.
  • Checking only the origin: Visitors may receive a CDN certificate that differs from the origin certificate.
  • Forgetting DNS ownership: An ACME DNS challenge fails when the automation account cannot update the authoritative zone.
  • Using a wildcard as a universal solution: Coverage boundaries and separate trust requirements still apply.
  • Leaving manual renewal undocumented: The process becomes a single-person dependency during an incident.
  • Testing only in one browser: Local caches and trust stores can conceal chain or hostname problems.
  • Changing certificates during a migration without a rollback: Keep the previous known-good configuration available until the new path is verified.

For a broader DNS cutover and rollback process, use the website hosting migration runbook. Certificate changes should be included in the migration plan, not treated as an afterthought.

When to revisit

Review the inventory before seasonal planning cycles, recurring security audits, domain renewals, hosting migrations, and major application releases. Also revisit it whenever a domain, subdomain, CDN, load balancer, DNS provider, or hosting panel changes.

Certificate authority policies, browser requirements, ACME client behavior, hosting-panel integrations, and CDN certificate options can change. Recheck those inputs at least when your organization’s workflow changes and on a regular review schedule, rather than assuming an old procedure remains valid indefinitely.

Use this short action list during each review:

  1. Export or inspect the current list of public hostnames.
  2. Compare every hostname with the SSL certificate inventory.
  3. Confirm renewal ownership, notifications, and DNS permissions.
  4. Test one renewal and deployment path before it becomes urgent.
  5. Check both CDN and origin certificates where applicable.
  6. Run an external HTTPS test and investigate chain, hostname, redirect, or mixed-content warnings.
  7. Record the result, next review date, and any corrective work.

A maintained inventory, automated renewal with visible failure alerts, and a two-layer CDN/origin check provide a practical foundation for reliable SSL certificate management across multiple websites.

Related Topics

#SSL#TLS#certificates#ACME#CDN#DNS#website security
O

OpenWebHosting Editorial Team

Technical 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.