Features

Business Website HTTPS Renewal: Expiry Alerts and Handover Checklist

Assign HTTPS certificate owners, track CDN and origin expiry, verify issuance and deployment, and test alerts, language entries and supplier handover.

Assign a named operations owner for your business website’s HTTPS certificates. At handover, document the hostnames, the expiry of each certificate currently served, renewal and deployment methods, alert recipients and backup staff. Close a renewal task after procurement, issuance, deployment and public checks are complete. This guide covers self-hosted websites, agency maintenance and CDN deployments. Content staff can coordinate the checklist; authorized operations staff perform infrastructure changes.

1. Track five separate expiry items

Domain registration, hosting, a certificate subscription, an individual TLS certificate and CMS update entitlements have separate deadlines. Track the action and budget for each. HTTPS certificates support encrypted browser connections. Product approvals, test reports and downloadable certificate PDFs are business documents covered by the download center guide.

  • Domain registration: registrar, account ownership and registration expiry.
  • Hosting, CDN or load balancer: resource ownership, billing dates and TLS termination points.
  • Certificate subscription: purchased entitlement and service term, with later issuance subject to provider rules.
  • Deployed certificate: covered hostnames, validity timestamps and installation locations.
  • CMS updates and maintenance contracts: responsibilities for software updates, infrastructure work and incident response.

Alibaba Cloud’s renewal documentation treats subscription renewal, certificate application and deployment as separate steps. Check your own provider’s current plan and console. Use the actual issued certificate to establish its validity period.

2. Keep an operational register for every hostname

List the primary hostname, www entry, separate language domains, image or download hosts and administration entry. Language directories on the same hostname generally share its TLS certificate. Separate language hostnames each need verified coverage. Ask operations to inspect the certificate’s SAN entries for wildcard scope and multi-domain coverage.

For each entry, record its purpose, DNS account ownership, TLS termination point, live certificate expiry and time zone, issuance method, domain validation method, latest successful and failed renewal runs, owner, backup person, notification channel and last acceptance check. Transfer private keys, DNS credentials and server passwords through controlled credential storage. The register holds credential locations and authorized people.

With a CDN, visitors see the edge certificate. HTTPS connections from the CDN to the origin have their own connection and certificate requirements. Check both layers and cover deployed nodes using the provider’s supported process. Test visitor access through the public entry; check the origin through an authorized operations path.

3. Make four renewal actions verifiable

  1. Arrange procurement and issuance. Check quotas, balance, domain validation permissions and the renewal client or managed service. Recheck configuration after DNS hosting, account access or access rules change.
  2. Deploy to the serving location. Identify the web server, load balancer or CDN, follow its installation and reload procedure, and record the certificate identifier and deployment outcome.
  3. Read the live certificate externally. Verify hostname coverage, trust chain, validity and the expected new certificate identifier on the public domain. Check multiple nodes according to the coverage plan.
  4. Test business pages. Open the home page, important products, both languages, downloads and contact entry. Check HTTPS, redirect destinations and loaded resources. Test form submissions in an agreed window with a clear test marker.

Verify automatic issuance and installation against the actual tool or managed product. External monitoring provides another way to detect problems. Let’s Encrypt’s monitoring guidance discusses expiry notifications and related uses. Check monitoring coverage, delivery channels and account ownership when selecting a service.

4. Cover failures, approaching expiry and staff handover

Monitor renewal job failures and the remaining validity of the certificate actually served. Choose alert thresholds according to certificate lifetime, the provider’s issuance window and team response time, allowing time for verification, retries and manual action. Here is an illustrative team policy: open a check 14 days before expiry, escalate unresolved work to the backup person at seven days, and involve the project owner at three days. Shorter-lived certificates and different provider windows require their own thresholds.

Use a team channel with a named owner and backup. During handover, verify that both can receive an alert, open the register and obtain required access. Keep alert recovery records and public certificate checks after renewal. Staff departures, supplier changes, DNS migrations, CDN switches and billing changes should trigger a register review.

5. Example: subscription renewed, old certificate still deployed

Fictional delivery example: a manufacturer uses example.com and example.com/en. A CDN terminates public HTTPS and also uses HTTPS to the origin. Procurement renews the subscription, a new certificate is issued and the CDN is updated. Operations finds the old certificate still installed at the origin. The team updates and loads the origin certificate according to its origin encryption policy, checks the origin connection through authorized access, then verifies public Chinese and English product and contact pages.

The maintenance record includes the subscription receipt, new certificate identifier, CDN and origin deployment outcomes, both actual expiry times, acceptance URLs, issues and repairs, owner and completion time. Both language directories share the host entry and receive separate business checks. This example demonstrates the method; operations confirms the project’s actual origin policy.

6. Complete seven handover checks

  1. The hostname inventory covers every public entry, with an owner for each TLS termination point.
  2. Public certificates have expected hostname coverage, trust chains and validity, with timestamped evidence.
  3. Renewal jobs or managed settings are inspectable; the latest run corresponds to deployment records.
  4. Verify renewal in a test environment or a safe rehearsal mode supported by the tool. Simulate an alert and check delivery and handling by the owner and backup.
  5. Check home, product, download and contact pages in both languages, recording redirects, resources and applicable form acceptance results.
  6. Complete edge and origin checks, and verify historical entry points against the current redirect policy.
  7. The business has account ownership and takeover access. Record costs, response times and supplier handover materials in the contract or delivery record.

When certificate warnings are already visible, operations should inspect actual expiry, hostname coverage, the trust chain and deployment state, then apply the corresponding repair. Direct visitors to a trusted business contact channel and recheck critical entries after recovery. Record incident timing, affected hostnames and restoration evidence.

7. Divide responsibility in a CatchCMS project

CatchCMS provides site domain bindings, multiple sites and multilingual content management. The current official website has its content model and Chinese and English languages configured. HTTPS issuance, installation, renewal jobs, external monitoring and incident response belong to project infrastructure operations. Agree their configuration and delivery with the hosting, CDN or maintenance supplier. Record CMS publication acceptance and certificate operations acceptance separately; review software update entitlements against the current licensing information.

For your own server, use the deployment and maintenance checklist. Review multilingual configuration for language entries and arrange a backup and recovery drill for supplier handover. Bring your hostname count, CDN setup, language entries, renewal method and maintenance responsibilities to the contact page to confirm CMS implementation and operations scope.

Frequently asked questions

What follows a certificate subscription renewal?

Apply for the next certificate according to provider rules, complete domain validation, deploy it to the serving location, then verify the live public certificate and business pages. For managed services, inspect automatic issuance and deployment results too.

Do Chinese and English websites need separate certificates?

Coverage follows hostnames. Language directories on one hostname generally share its connection certificate. Separate language domains must each appear in the coverage and monitoring inventory. Operations should confirm procurement against your domain structure and certificate product.

What should the business retain when an agency maintains its website?

Keep domain and cloud account ownership, access handover procedures, the register, renewal and deployment records, alert recipients and backup staff, response commitments and the latest public acceptance evidence. Transfer secrets through controlled credential channels.