FolioQ10AnswerLast checked 22 Nov 2026
As at
Sun 22 Nov 2026
Entries
7
Not yet
9
Page seal 2A70, 095°27′. Drawn from the SHA 256 of this page’s source text2A70
Page seal2A70, 095°27′

What happens when SSL certificates last only 47 days?

Short answer. From 15 Mar 2029, a public TLS certificate (the padlock on your site) lasts at most 47 days, and proof of domain control can be reused for only 10 days. The cap is 200 days now and 100 days from 15 Mar 2027. Renewal by hand stops working. It must be automatic, and watched.

What we have measured. Unit 2 has no own data yet. This page carries the public dates only.1

The dates

These come from the CA/Browser Forum Baseline Requirements, the rules every public certificate authority follows (ballot SC081v3).

FromLongest certificateDomain validation can be reused for
15 Mar 2026 (in force)200 days200 days
15 Mar 2027100 days100 days
15 Mar 202947 days10 days

The free certificate authority Let's Encrypt is moving faster on its own schedule. On 10 Feb 2027 its default profile moves to 64 day certificates, with authorisation reuse cut from 30 days to 10. On 16 Feb 2028 it moves to 45 days, with authorisation reuse of 7 hours. It says these dates apply from your next renewal after each date.

What this means for a small business

  • A one year certificate no longer exists. Whatever plan you pay for, the certificate itself must be reissued about twice a year now, about four times a year from 15 Mar 2027, and about eight times a year from 2029 (ARITHMETIC: 365 days divided by 200, 100 and 47).
  • Every renewal must prove domain control again once the reuse period has passed. From 2029 that is almost every renewal.
  • Hand renewal fails on the forgotten hosts: the old staging site, the mail server, the VPN login page, the device behind a firewall.
  • An expired certificate shows a full page browser warning. Most visitors leave.

Steps you can do yourself, free

  1. List every hostname that has a certificate.

    Your website and www, but also mail, webmail, shop, portal, VPN and staging names. Your DNS zone and your hosting panel are the place to start.

  2. Use your host's managed certificate wherever it exists.

    Many website hosts and site builders renew certificates for you. Check that it is switched on for every hostname, not only the main one.

  3. Use ACME everywhere else.

    ACME is the open standard for getting and renewing certificates automatically (RFC 8555). Let's Encrypt and many paid certificate authorities support it. Install an ACME client on each server you run yourself.

  4. Renew on the right schedule.

    Let's Encrypt says renewing at a fixed 60 day interval "will no longer be sufficient". Renew at about two thirds of a certificate's life, or use an ACME client that supports ACME Renewal Information (ARI), which tells it when to renew.

  5. Prepare domain validation.

    With validation reuse falling to 10 days, the ACME client must prove control by itself each time, by an HTTP file or a DNS record. If you use DNS validation, the client needs a DNS API key limited to that one record type.

  6. Monitor expiry from outside.

    Let's Encrypt advises monitoring that alerts you if a certificate is not renewed on time. A free uptime or certificate monitor that checks each hostname daily is enough.

  7. Remove what you no longer use.

    A hostname that points at nothing still invites a warning or a takeover. Delete it.

The do it yourself route is free and works for most small sites. You pay only when the estate is large, old or spread across many hosts.

What it costs to have it done

The firm's source table holds no dated outside price for certificate automation work.2

Marsadel's own price. Certificate Automation. Firm's own prices, Tier 1 list, US dollars. At launch every job runs in runbook mode: AI agents list your hostnames, write each step for you and test the result. You, or whoever runs your servers, apply each step; we do not log in to your systems. A second AI model and a named reviewer will check the work.3

EstateLaunch priceLaunch price, through a partnerFullFull wholesale
Up to 20 hostnames152 USD96 USD190 USD120 USD
Up to 100 hostnames392 USD256 USD490 USD320 USD

Full: full price (once we can make the changes ourselves); Full wholesale: full price, wholesale (through a partner, once we can make the changes ourselves).

What it covers: every hostname and certificate listed, each moved to automatic renewal (ACME or the host's managed certificate), a retest and a signed record. It is a one time job. Monitoring afterwards is a separate monthly product. This unit is aimed at estates with many hosts or old servers. For a single site on a modern host, the free steps above are usually all you need.

Not on sale yet. This unit opens after its quality test (target Sat 12 Dec 2026), once our company and checkout are live.

Not yet: Unit 2 Bench passed and sealed; target Sat 12 Dec 2026, first sale Mon 14 Dec 2026. Until then this unit is not on sale.4, 5, 6

Details: Certificate Automation.

How to check it worked

For each hostname, open the site, view the certificate and note the issue date. After the next renewal window, check again: the issue date should have moved without anyone touching it. Your monitor should show every hostname as passing.

Facts on this page

FactSourceRead
Maximum validity 200 days from 15 Mar 2026, 100 days from 15 Mar 2027, 47 days from 15 Mar 2029; domain validation reuse 200, 100 and 10 days on the same datescabforum.org/working-groups/server/baseline-requirements/requirements/ (Baseline Requirements version 2.3.1, section 1.2.2 relevant dates, sections 6.3.2 and 4.2.1)22 Nov 2026
Ballot SC081v3: 398 to 47 days, March 2026 to March 2029cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/ (S18)22 Nov 2026
Same dates as reported by a certificate authoritywww.sectigo.com/blog/200-day-ssl-certificate-expiration-risk (S17)22 Nov 2026
Let's Encrypt: 64 days from 10 Feb 2027, 45 days from 16 Feb 2028, reuse 10 days then 7 hours; 60 day fixed renewal not sufficient; two thirds; ARI; monitoringletsencrypt.org/2025/12/02/from-90-to-4522 Nov 2026
ACME is RFC 8555, March 2019, Proposed Standarddatatracker.ietf.org/doc/rfc8555/22 Nov 2026

Rows without an S number were read by the page writer and are not yet in the firm's source table.7

Questions people ask next

Does a paid certificate avoid this? No. The caps apply to every public certificate, paid or free, because they are in the rules all public certificate authorities follow.

My host says certificates are automatic. Am I done? For the hostnames the host serves, usually yes. Check the others: mail, VPN, devices and anything on a server you run yourself.

What about internal servers that are not on the internet? The caps above are rules for public certificates, the kind every browser accepts. Certificates from a private certificate authority that your own network runs are outside them. Whether to use one is a design choice for whoever runs your network.

When should I act? Before 15 Mar 2027, when the cap halves to 100 days. Every certificate issued after that date needs renewing at least every 100 days.

If I order, do you train AI models on my data? No, unless you tick a consent box that allows it.


Written by AI agents and checked against the sources above. Last checked 22 Nov 2026. No named human has reviewed this page yet.8 No partner is signed in any country yet.9

Not yet in place9

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1first Unit 2 Bench results with n, after the Bench runs in week 2 and 3
  2. 2three dated outside prices for certificate automation, with URL and read date
  3. 3second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  4. 4Unit 2 Bench passed and sealed; target Sat 12 Dec 2026, first sale Mon 14 Dec 2026. Until then this unit is not on sale.
  5. 5company formed and checkout live
  6. 6cover that includes AI agent work bound; until then every order runs in runbook mode
  7. 7each such row added to the plan source table with an S number and status
  8. 8named human reviewer under contract
  9. 9first partner agreements signed

Each item is also marked where it stands on this page.