Does auto-renew mean I do not need to track domain expiry?

No. Auto-renew fails when the stored card expires, billing details change, the domain moves registrar, or renewal notices go to a departed employee's address. The date is still worth holding independently.

How much notice should I set for an SSL certificate?

Thirty days is comfortable for a manually issued certificate. For automated short-lived certificates, monitor the automation instead — a date-based reminder tells you little there.

What happens if a domain expires?

It typically stops resolving immediately, then passes through a grace period and a redemption period with an escalating recovery fee before becoming available to anyone. Email stops working too, which is often the more expensive half.

← All guides

How to track SSL certificate and domain expiry

Updated September 2026

Short answer

Record the registrar, the renewal date, the payment method's own expiry, and the person responsible — then set a reminder even for items on auto-renew. Auto-renewal fails for mundane reasons: the card on file expires, the billing address changes, the domain moves registrar, or the renewal email goes to someone who left.

Auto-renew is not the same as handled

Most outages of this kind happen on domains and certificates that were set to auto-renew. The renewal did not fail technically; the payment did, or the notice went to an address nobody reads any more.

Treat auto-renewal as a convenience, not a control. The control is knowing the date and having a person attached to it.

What to record

For domains: registrar, renewal date, auto-renew status, the account the payment card belongs to, and the owner. For certificates: issuer, common name, expiry date, and where it is deployed.

Where it is deployed is the field that saves the most time. A wildcard certificate installed on four servers has four points of failure, and the one nobody documented is the one that keeps serving an expired certificate after the others are updated.

How much notice

Thirty days for certificates, sixty for domains. Domains get the longer window because a lapsed domain can enter a redemption period with a substantial recovery fee, and because transfers away from a registrar are blocked close to expiry.

Short-lived certificates that renew automatically every ninety days are the exception worth monitoring rather than reminding on — there the useful alert is that the automation stopped, not that a date approaches.

Name a person, not a team

Domains and certificates are the classic orphaned asset: registered by whoever set the project up, renewing to a card that belongs to someone who left. Attaching a current owner to each one is what prevents the outage that nobody expected because everyone assumed it was handled.

Common questions

Does auto-renew mean I do not need to track domain expiry?: No. Auto-renew fails when the stored card expires, billing details change, the domain moves registrar, or renewal notices go to a departed employee's address. The date is still worth holding independently.
How much notice should I set for an SSL certificate?: Thirty days is comfortable for a manually issued certificate. For automated short-lived certificates, monitor the automation instead — a date-based reminder tells you little there.
What happens if a domain expires?: It typically stops resolving immediately, then passes through a grace period and a redemption period with an escalating recovery fee before becoming available to anyone. Email stops working too, which is often the more expensive half.

Let the dates chase themselves

ExpiryLedger tracks every renewal and emails you — and the person holding the document — before it lapses. Free for 25 items, no card.

Track your first renewal — free