Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Automate and verify TLS certificate renewal

    Issuance is only one step: the correct certificate must reach browsers on every relevant hostname and entry point. Organise that cycle without placing private keys or access details in the operational record.

    Go to the method

    Laptop and padlock beside technical equipment
    AI-generated illustration

    Separate three different deadlines

    Distinguish domain registration renewal, certificate expiry and proof of domain control. Record the authority, covered names, TLS termination point, owner and renewal procedure. A CDN, load balancer and origin server may use different certificates. Renewing a hosting subscription does not establish that each certificate is renewed.

    For public TLS certificates in scope of the Baseline Requirements, maximum validity is 200 days for issuance from 15 March 2026 through 14 March 2027, then 100 days through 14 March 2029, and 47 days from 15 March 2029. These are ceilings, not universal lifetimes. An authority may use shorter periods.

    Inspect the profile instead of assuming a lifetime

    Let’s Encrypt publishes its own schedule: tlsserver profile at 45 days since 13 May 2026; classic profile scheduled for 64 days on 10 February 2027 and 45 days on 16 February 2028. Check the configured profile and current documentation before defining alerts. Do not describe all Let’s Encrypt certificates as already having 45-day lifetimes.

    Choose an intervention margin suitable for observed validity and the actual response time of the team. A rule based on an old annual certificate could alert too late. Keep observed start and end dates in the inventory without including secrets. Expiry or a missing hostname is a concrete defect requiring action.

    Test issuance and installation separately

    Let’s Encrypt staging helps prepare an integration. Its certificates are not intended to be trusted by visitors’ browsers. Run that test in an appropriate environment, then verify the production journey with the expected certificate.

    Include a case where renewal produces a new file but the service still presents its old certificate. Check from outside the termination point after reload or deployment. With multiple servers, inspect the different destinations. Retain hostname, date, presented certificate and connection result; a successful renewal log alone does not establish installation.

    • Issuance tested in staging.
    • Installation and reload verified.
    • Visitor-facing certificate inspected.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Separate issuance from the certificate actually served
    Situation or settingWhat it meansUseful check
    Issuance succeededA new certificate was obtained.Check installation on the public service; an issued file may never be deployed.
    The main domain responds over HTTPSThat name has a reachable endpoint.Also check www and other relevant names without assuming a common certificate.
    The certificate varies by access pointSeveral servers or endpoints may serve different states.Compare names, dates, chain and checking location before closing the renewal.

    Make validation reproducible

    Let’s Encrypt ACME challenges demonstrate domain control: HTTP-01 uses an HTTP resource and DNS-01 a TXT record. DNS-01 also enables wildcard names. Identify DNS, routing and ACME-client dependencies before changing hosting.

    A redirect, an upstream protection layer or a DNS change can break a previously working mechanism. Repeat the documented test after such changes. Name the validation owner and environment without copying access details. Retain a clear test record for the next operator.

    For Let’s Encrypt, HTTP-01 validation must reach TCP port 80 and cannot issue a wildcard. DNS-01 uses a TXT record under _acme-challenge and supports wildcards. Choose according to actual routing and DNS permissions, restricting automation access to what is needed.

    CAA records define which certificate authorities may issue under the DNS policy. They prove neither certificate installation nor private-key security. When issuance is blocked, also check DNS resolution and CAA policy instead of routinely removing restrictions.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Let’s Encrypt validation: three separate checks
    MechanismDocumented conditionUseful verification
    HTTP-01HTTP resource reachable on TCP 80; no wildcardReach the token on every relevant frontend
    DNS-01TXT under _acme-challenge; wildcard possiblePublished value and DNS visibility before validation
    CAAAuthorities permitted to issue under DNS policyCompatibility with the selected authority; issuance and installation remain separate

    Monitor the served result and prepare recovery

    Let’s Encrypt’s integration guide includes support for ACME renewal information when available. Document the chosen mechanism, version, latest success and errors. Add an independent observation of the certificate actually served.

    Decide who receives an alert, the response window and escalation if nobody responds. Recovery should cover diagnosis, installation and post-fix verification. Connect it with the incident plan and pre-publication checks. Avoid discovering an unavailable validation owner on the eve of expiry.

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Issuance succeeds but the server presents the old certificate.External inspection detects the mismatch.Domain name, tested endpoint, received certificate and validity dates actually served.
    Routing changes block the validation path.Renewal testing reveals the fault before expiry.Repeat the configured challenge in staging.
    A subdomain uses another termination point.Each critical hostname presents a valid certificate.Compare the inventory with connections for the different names.

    Frequently asked questions

    Does domain renewal also renew the certificate?

    They concern different objects. Confirm the domain deadline with its contractual owner and inspect the expiry of the certificate presented by HTTPS.

    Must every certificate last 200 days in 2026?

    No. The ceiling depends on issuance date and the cited requirements’ scope. Authorities may issue shorter certificates; inspect the actual profile and certificate.

    Does a successful renewal log prove that browsers receive the new certificate?

    No. Issuance, copying, reload and presentation may diverge. Inspect hostname coverage and validity at the entry point visitors use.