Skip to content
LookupOwl

Certificate lifetime readiness

Check whether the certificates on your hosts are ready for the shorter lifetimes that start in 2027.

We check this name and, below, any other hosts you list.

Up to 20 hosts, one per line, as host or host:port. Wildcards such as *.example.com are not hosts; list the real names. Each host is one TLS connection: about 5 seconds, up to 20 for a long list.

More options

Looks at how often each host's certificate is replaced. Without it we judge only from the certificate being served now.

Add each registered domain's own expiry date, when the registry says it.

Days left at or below which a certificate counts as expiring soon.

Results for mediawiki.org

Checked live lookup447 ms

JSONCheck again

Lifetime readiness

mediawiki.org's certificate is valid for 47 days more.

A 90 day certificate: ready for the 100 day limit in 2027, and needs automatic renewal for 47 days in 2029.

Days left

2027-01-02 · 90-day certificate

  • From 2029-03-15 certificates may be valid for 47 days at most, so renewal has to be automatic.
  1. 200 daysThe limit today (since 2026-03-15)
  2. 64 daysLet's Encrypt default from 2027-02-10. A CA programme, not a limit
  3. 100 daysFrom 2027-03-15, in 119 days
  4. 47 daysFrom 2029-03-15, in about 28 months

Add more hosts

Structured result (JSON) · 2.3 KB
{
  "domain": "mediawiki.org",
  "mode": "readiness",
  "asOf": "2026-11-16T19:55:04.597Z",
  "limits": [
    {
      "from": "2026-03-15",
      "maxDays": 200,
      "inForce": true,
      "kind": "cab"
    },
    {
      "from": "2027-02-10",
      "maxDays": 64,
      "daysAway": 86,
      "kind": "ca-program"
    },
    {
      "from": "2027-03-15",
      "maxDays": 100,
      "daysAway": 119,
      "kind": "cab"
    },
    {
      "from": "2029-03-15",
      "maxDays": 47,
      "daysAway": 850,
      "kind": "cab"
    }
  ],
  "summary": {
    "hosts": 1,
    "checked": 1,
    "failed": 0,
    "expiringSoon": 0,
    "expired": 0,
    "readyFor100": 1,
    "readyFor47": 0,
    "verdict": "ready"
  },
  "hosts": [
    {
      "host": "mediawiki.org",
      "port": 443,
      "status": "ok",
      "issuer": {
        "name": "Let's Encrypt",
        "cn": "YE2"
      },
      "notBefore": "2026-10-04",
      "notAfter": "2027-01-02",
      "lifetimeDays": 90,
      "daysLeft": 47,
      "ageDays": 43,
      "ipsDiffer": false,
      "ips": {
        "checked": 3,
        "differ": 0
      },
      "readiness": {
        "now": "pass",
        "by2027": "pass",
        "by2029": "fail",
        "automation": "unknown",
        "evidence": {
          "source": "ct",
          "renewalsSeen": 2,
          "medianLifetime": 90,
          "medianDaysBeforeExpiry": 80
        }
      },
      "ca": {
        "ari": "yes",
        "acmeDirectory": "https://acme-v02.api.letsencrypt.org/directory"
      },
      "caa": {
        "present": true,
        "accountBound": false,
        "validationMethods": false
      },
      "dns01": {
        "acmeChallengeCname": null
      },
      "domainExpiry": {
        "date": "2027-08-09",
        "status": "ok"
      },
      "stored": null,
      "issues": [
        {
          "code": "NEEDS_AUTOMATION_2029",
          "severity": "info",
          "message": "From 2029-03-15 certificates may be valid for 47 days at most, so renewal has to be automatic.",
          "fix": null
        }
      ]
    }
  ],
  "notChecked": [],
  "ctHistory": {
    "status": "ok"
  },
  "recommendations": [
    {
      "id": "automate",
      "title": "Renew automatically, so 47 day certificates are routine",
      "hosts": [
        "mediawiki.org"
      ]
    }
  ],
  "feed": null
}

Next step

The new limits

The longest lifetime a publicly trusted TLS certificate may have is set by the CA/Browser Forum, where browsers and certificate authorities agree the rules (ballot SC-081). It is counted from the day a certificate is issued, so a certificate you already have keeps its full life. What changes is what your authority may issue the next time you renew.

Issued fromLongest lifetimeSet by
Before 2026-03-15398 daysCA/Browser Forum
2026-03-15200 daysCA/Browser Forum
2027-02-1064 days (default)Let's Encrypt, its own programme
2027-03-15100 daysCA/Browser Forum
2029-03-1547 daysCA/Browser Forum

The Let's Encrypt row is a default that one authority chooses, not a rule for everyone, so the result draws it with a dashed outline. The time an authority may reuse a proof that you control a domain shrinks on the same dates, which is one more reason renewal has to be automatic by 2029.

What this check tells you

  1. List your hostsType one name in the first box and up to 20 more below it, one per line, as host or host:port. Use real names, since a wildcard such as *.example.com is a certificate, not a host.
  2. Read the verdictThe top of the result says how many hosts pass the 2027 rule and how many could cope with 47 days. A host that is expired, not trusted or answering for another name is counted as checked, with a problem. A host that did not answer is left out of the verdict and says so.
  3. Open the rows that need actionRows are sorted with the hosts that need action first. Each shows the lifetime, the days left, two marks for 2027 and 2029 and, when you open it, the renewal evidence, the dates and what to change.

How to read the lifetime bars

Every host gets a bar on the same axis, from 0 to 200 days. The darker part is the time the certificate has already been in use and the light part is the time left. Three thin lines mark 47, 100 and 200 days. A certificate of 90 days ends between the 47 and 100 lines, which is where most automated certificates sit. One of 198 days ends just short of the 200 line and passes the 100 line, so you can see the problem without reading a number.

A certificate longer than 200 days is drawn to the edge of the axis and the row says its real length. The words under each bar say the same thing as the picture, because a drawing is never the only place a fact appears.

Is renewal automatic?

A 90-day certificate is ready for the 100-day rule today, but 47 days comes round so often that only automatic renewal works. The check looks for evidence in four places and shows each one in the row.

  • Renewal history. Public Certificate Transparency logs show every certificate issued for a name. At least three certificates of 100 days or less, each issued before the last one ran out, read as automated. Long certificates replaced about once a year, or a replacement that came after the old one ended, read as manual. Anything else is "can't tell".
  • A delegated _acme-challenge name. A CNAME at _acme-challenge.<host> hands the DNS-01 proof to a service built for renewing, which is a good sign.
  • CAA with accounturi and validationmethods. These parameters (RFC 8657) tie issuance to your own ACME account and method. They are not required, and they are what an automated setup tends to use.
  • Renewal information (ARI). Some authorities publish when a certificate should be renewed (RFC 9773). We read the authority's ACME directory and report "yes", "no" or "unknown", and unknown is never counted against you.

Renewing when about a third of the lifetime is left is a common practice and what Let's Encrypt suggests. It is advice, not a requirement, so the page never treats a host as late for renewing at another time.

What to do before 2027-03-15

  • Move every long certificate to automation first. Hosts of 198 days or more are the ones the check flags for 2027. Ask your authority for certificates of 90 days or less and renew them with an ACME client.
  • Test a renewal end to end. Run one on purpose, confirm the new file was written and that the service reloaded to use it.
  • Find the hosts nobody owns. Staging, mail, VPN and admin hosts often have a hand-installed certificate. The subdomain finder helps you list them, then paste the names here.
  • Watch for a server that serves an old certificate. When a name has several addresses, one stale node still reaches visitors. The row says how many addresses differ and uses the lowest days left.
  • Plan for 47 days now. Delegate _acme-challenge, bind CAA to your account and make sure a failed renewal raises an alert well before expiry. A CAA check shows who may issue for you today.

How the check works

For each host LookupOwl resolves the name, checks that every address is public, completes one TLS handshake with the right server name and reads the certificate. It then reads the other addresses of the name to see if they serve the same one. Up to 21 hosts are checked, five at a time, each with a few seconds to answer. Private names and addresses are never contacted. The rest, which is CAA, the _acme-challenge name, the authority's directory, the logs and the registration date of each domain, is read only when it adds something and is skipped when it cannot be read.

The host list is sent to our server to run the check and is not stored. The certificate details come from the SSL checker, and renewal history comes from the same logs as the certificate search.

Questions people ask

Do the new limits apply to every certificate?

They apply to publicly trusted TLS certificates, the ones browsers accept from public authorities. Certificates from your own private authority are not covered, and a host that uses one shows up here as not trusted rather than as a readiness problem.

Will my existing certificate stop working in 2027?

No. The limit applies on the day a certificate is issued, so a certificate keeps working until it expires. What changes is that your next certificate may be at most 100 days long, then 47 days from 2029, and renewal has to keep up.

How do you know if renewal is automatic?

We look at how often a host's certificate was replaced in public logs, and whether replacements came before the old one ended. Without that history we judge only the certificate being served now and the row says "can't tell".

Why is a 90 day certificate marked "not yet" for 2029?

Because 90 days is longer than 47. It is fine today, and it can be fine in 2029 if renewal is automatic and the authority issues shorter ones. The mark says what the certificate is now, and the renewal evidence says whether it can change.

What does an unknown or "can't tell" mean?

It means we could not see enough to say, for example when the logs are down or a name has few certificates. It is never counted as a pass or as a fail.

Why is the Let's Encrypt line dashed?

Because it is that authority's own default, not a rule of the CA/Browser Forum. Other authorities keep issuing up to the Forum limit, which is why the strip lists both.

Can I check hosts on a port other than 443?

Yes, as host:port, on 465, 587, 636, 853, 993, 995 and 8443 as well. Mail submission on 587 asks the server to switch to TLS first. We never send a message or log in.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is cert_expiry_check. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/cert-expiry-check?q=lookupowl.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp