Auto-renewal charges your card before the domain expires. It is one setting, it takes ten seconds, and on a domain it is not a convenience. It is the difference between a renewal you forget and a business name someone else registers.
Turning it on
In the client area, open your domain list, select the domain, and enable auto-renewal in its settings.
Renewal is normally attempted a few weeks before expiry, which leaves room for a failed payment to be noticed and fixed before anything breaks. That margin is the point: charging on the expiry date itself would leave none.
Two things that make it actually work
Enabling the setting is not sufficient on its own. Both of these fail quietly.
The card's expiry date. A card that expires before the renewal is the most common cause of a failed auto-renewal, and there is no error until the charge is attempted. Check that the card on file outlives your next renewal date.
Where notices go. Renewal reminders and failure warnings go to your account email. If that is an address on the domain being renewed, the domain expiring takes the warning with it; the exact moment you need it. Use an address on a different domain.
Why it matters more for a domain than for hosting
Both renew, and the consequences of failure are not comparable.
A hosting account that lapses is suspended, then eventually terminated. Unpleasant, and recoverable from your own backup.
A domain that lapses stops resolving, moves into a redemption period with a substantial recovery fee, and is then released for anyone to register. Recovery becomes expensive and then impossible, and it takes with it every email address on the domain, plus any account elsewhere that used one of those addresses for password resets.
That last consequence is the one people do not anticipate, and it surfaces months later.
Renewing your domain name walks through the full sequence and the stages within it.
Domains and hosting renew separately
Different products on different cycles, even when bought together and even when auto-renewal is on for one of them.
Check both. A perfectly paid hosting account does not keep a domain alive, and this is a genuinely common way a working site disappears.
When a renewal fails anyway
You will normally receive a notice. Update the card in the client area and the charge is retried, or you can pay the invoice manually.
Do this promptly. The domain is still fine while the invoice is outstanding, and it stops being fine at the expiry date, and each stage after that is worse than the last.
Turning it off
Reasonable if you are deliberately letting a domain go. A variation you registered defensively and no longer want, or a project that ended.
Two things worth doing before you do.
If content lives there, redirect it while you still control it, so inbound links keep working for as long as possible. There is more in domain forwarding.
And check nothing uses an email address on that domain. Any account elsewhere with a password reset pointing at it becomes unrecoverable once the domain lapses.
Multi-year as an alternative
Renewing several years at once removes the annual failure point entirely. Registries generally allow up to ten years.
Worth doing for a domain the business depends on. It costs the same money slightly earlier, and it means a lapsed card cannot cost you the name.
Worth checking once a year
Alongside the renewal date, confirm three things: auto-renewal is still enabled, the card on file is current, and the account email still reaches you.
All three drift over time, and all three fail silently. Five minutes annually is cheap against the alternative.
Auto-renewal fails quietly when a payment card expires, which is why it is not a substitute for a list. How to Manage a Portfolio of Domains and Renewals goes into keeping one.
Verify it from outside the registrar
The setting in the account is a promise. The public record is what actually happened, and checking it costs seconds.
whois example.com | grep -iE 'expiry|expiration|renewal|status' dig example.com SOA +short
Read the expiry date and confirm it is where you expect. A domain renewed last month and still showing last year's date means the renewal did not reach the registry, whatever the account says.
Worth doing on a schedule rather than on a reminder, particularly for the domains that matter most. A monthly check against a list is the arrangement that catches the failure while it is still cheap to fix. Managing a portfolio of domains and renewals explains keeping the list.
Two dates, and when the charge actually happens
Automatic renewal does not fire on the expiry date, and the gap is where the confusion lives.
Most registrars attempt the charge somewhere between a week and a month beforehand, precisely so a failure leaves room to retry. So a card that expires between the attempt and the expiry date still causes a problem, and a card replaced after the attempt has already been declined does not fix it by itself.
The other date is the registry's in place of the registrar's, and they can disagree briefly after a renewal while the change propagates. A public record that has not updated an hour after a renewal is normal; one that has not updated the following day is not. Renewing your domain name explains doing it deliberately when the automatic attempt failed.
The timeline after it does expire
Expiry is not deletion, and knowing the stages tells you how much time a mistake actually costs.
Immediately after expiry, the domain typically stops resolving. The site and the mail both stop, which is usually how anyone finds out.
For a period afterwards, it can be renewed at the normal price. This is the window worth acting in, and it is shorter than most people assume.
Then a redemption period, where recovery is still possible and carries a substantial fee, frequently many times the renewal cost.
Then release, at which point anybody can register it and desirable names are taken within seconds by services that watch for exactly this. There is more on each stage in detail in what happens when a domain expires.
Whose domain is it, in the account
Automatic renewal protects against forgetting. It does not protect against nobody being able to reach the account.
A domain registered by a departed employee, in a personal account, with a personal card and a personal email address, renews automatically until the card expires, and then nobody can renew it, recover the account, or prove ownership.
whois example.com | grep -iE 'registrant|admin email|organization'
The registrant should be the organisation instead of a person, the account address should be one more than one person can read, and the payment method should be the company's. Fixing this while everything works is administrative; fixing it after the person has gone is a dispute. Moving a domain between registrar accounts walks through the correction.