The expiry date in a registration record is the most consistently misread field in the whole system. It is not the date a name becomes available, and reading it that way costs a wait of around two and a half months for a name that appeared to be free immediately. The domain lifecycle after expiry runs through five distinct windows, each governed by different rules and each visible in the record as a different status code.
Five windows, in order
From expiry to release
| Window | Typical length | Who can act |
|---|---|---|
| Registered | The paid term | The holder. Normal operation.Status ok, or more usually a registrar lock such as clientTransferProhibited. |
| Auto-renew grace | 0–45 days after expiry | The holder, at the normal renewal price.Status autoRenewPeriod. The registrar sets its own, shorter deadline inside this. |
| Redemption grace | 30 days | The holder only, at a redemption fee.Status redemptionPeriod. The registration has been deleted; the name is not yet available. |
| Pending delete | 5 days | Nobody. The outcome is fixed.Status pendingDelete. This is the only reliable countdown in the process. |
| Released | Instant | Anyone, in practice whoever is fastest.The name returns to the available pool in a registry batch operation. |
Country-code registries diverge from this, sometimes considerably: some have no redemption window at all, some quarantine names for months. The five-window shape above is the generic top-level domain pattern, and it is the one most tooling assumes.
What expiry actually changes
On the expiry date itself, remarkably little happens. The registry does not delete anything. In the overwhelming majority of cases it auto-renews the registration provisionally and bills the registrar, which is why an expiry date in the past is entirely compatible with a working site. The record is still there, the delegation is still published, and resolution continues.
What changes is who is on the hook and how long they have. The registrar now holds a provisional renewal it can reverse, and it will begin its own escalation: notices to the holder, then usually a parking page in place of the site, then withdrawal of the delegation. Those steps are registrar policy rather than registry rule, which is why two names expiring on the same day at different registrars behave completely differently. An expiry date tells you the term ended; it does not tell you what the registrar intends to do about it.
The auto-renew grace period
This first window is the longest and the least defined. The registry permits up to forty-five days during which the registrar may reverse the provisional renewal at no cost. Registrars use that latitude very differently: some carry a name for the full period, some delete after a fortnight, some sell the expiring registration through their own auction platform rather than letting it proceed at all.
That final state is worth knowing about, because it removes a name from the public part of the domain lifecycle entirely. A registration sold at a registrar's expiry auction is transferred to the new buyer directly. It never enters redemption, never reaches pending delete, and never drops. It simply changes hands, with the registry record showing a transfer rather than a new creation. Names with any commercial value frequently end this way.
The redemption grace period
When a registrar does delete the registration, the redemption grace period begins. This is the thirty-day window that people are most surprised by, because the name behaves as though it were gone: the delegation is withdrawn, the site is down, and mail bounces. But the registry still holds the record, and nobody else can register it.
Only the previous holder can act during the redemption grace period, and doing so costs a
redemption fee set by the registry: commonly in the region of eighty to a hundred and fifty times
a renewal, depending on the extension. The status code is redemptionPeriod, and it is
the clearest single signal in the record that a name has been let go rather than merely lapsed.
Why the site is already down
The delegation is withdrawn at deletion, not at release. That means the entire redemption grace period is served as NXDOMAIN: the same answer a resolver gives for a name nobody ever registered. A name in redemption looks available to every checker that works by resolution, and is not.
Pending delete and the drop
After redemption closes, the record moves to pendingDelete for five days. Nothing can
change during this window: the previous holder can no longer restore, and nobody can pre-register.
It is the one genuinely predictable stretch of the whole process, and it is what makes the drop
date knowable to within a day.
The drop itself is a registry batch operation. For extensions with meaningful demand it is contested by automated buyers submitting registration attempts in volume at the moment of release, which is what a drop-catch service sells. The consequence for reading records is simple: a name with any residual value will very rarely sit unregistered after the drop for long enough to be noticed, so finding one that has is usually a sign that its value is not what it appears.
Reading the domain lifecycle from a record
The status codes locate a name in the domain lifecycle precisely, and they are the only field that
does. An expiry date in the past with status autoRenewPeriod means the first window;
redemptionPeriod means deleted but recoverable by the previous holder;
pendingDelete means five days out. Read those from a
whois record or an
RDAP response, never from a resolution check, because
three of the five windows are indistinguishable from resolution alone.
Afterwards, the creation date becomes the tell. A new registration following a drop carries a new creation date and a new registry handle, and loses the old ones entirely. That is why a name with a decade of inbound citations can show a creation date of last week: the registry is describing the current registration, not the name. If you have an expiry date and want the windows worked out for you, the lifecycle calculator returns all five dates in the browser.
