Xcelerate
Menu
Get in touch
All articles on cloudflare and service protection

Cloudflare and service protection

Who renews the certificate behind Cloudflare?

Trace both TLS connections on a service behind Cloudflare and give your hosting and web suppliers a clear certificate renewal and handover brief.

An engineer checks a certificate renewal timeline on a monitoring console.
AI-generated editorial image.

A visitor can see a secure connection to Cloudflare while the web team is approaching a separate certificate deadline at the hosting provider. For each public service, record both connections and name the people responsible for renewing and checking them.

Draw the two connections on the service record

The first connection runs from the visitor’s browser to Cloudflare. The second runs from Cloudflare to the origin server that hosts the site. Cloudflare’s Full (strict) mode checks the origin certificate, including validity and the hostname it covers. Confirm which setting the service actually uses and which certificates the hosting arrangement supports.

A council may operate the main website while an external supplier runs the library portal. Even if both names appear in the same account, their origin certificates can have different owners and expiry dates. Give each hostname its own line in the register. Store references to the protected credential system, keeping private keys out of the register itself.

Agree the renewal window with the host

Ask the supplier to show how an approaching expiry becomes a task that someone must acknowledge. Include a deputy and a contact path for school holidays or the Christmas closure. Give the owner enough time to coordinate a change with the person responsible for the application.

Write down which team orders or issues the certificate, who installs it and who verifies the result from outside the hosting environment. If renewal is automated, ask where a failed run is reported. A green task for issuing the new certificate tells you little about which certificate the running service is presenting.

Prove that the service can complete a renewal

Use a non-production hostname with the same ownership arrangement for a renewal rehearsal. Have the hosting operator record the new validity period and the web team confirm that the proxied page and a representative user journey still work. Record where the certificate identifier and change ticket can be found.

On the live service, include a follow-up check after the change window. If either supplier leaves, the incoming operator should be able to identify the next renewal, find the agreed verification method and reach the service owner. Include that handover exercise in the support agreement.

Sources and further reading