A domain registration is a renewable contractual right. It has dates, status codes, a sponsoring registrar, registry policy, and recovery rules. It is not permanent ownership, and it is separate from DNS hosting.
Scope matters before the timeline
The lifecycle below describes a typical generic top-level domain (gTLD) such
as a name under .com. Country-code top-level domains and sponsored or
restricted domains can use different policies and timelines.
ICANN’s lifecycle material is explicitly a typical gTLD model [1]. The registration agreement, registrar terms, and registry policy remain authoritative for a particular name.
A practical lifecycle
Registered
The registry records the name under a sponsoring registrar for a defined registration term. The registrant manages the registration through that registrar or its reseller.
During the active term, keep these controls current:
- registrant and account contact details;
- registrar account recovery and multifactor authentication;
- auto-renew setting and valid payment method;
- registrar and registry lock status where available; and
- intended authoritative nameservers.
Renewal
Renewal extends the registration term. Auto-renew is an operational convenience, not a substitute for monitoring the expiry date, billing method, and registrar notices.
Renew before expiry. Waiting for a recovery window adds availability, ownership, and cost risk.
Expiry
Expiry does not imply one universal sequence or instant public availability. The registrar may provide a post-expiration renewal period, interrupt DNS, park the name, auction an interest, or delete the registration according to its terms and applicable policy.
For covered gTLD registrations, ICANN’s Expired Registration Recovery Policy sets minimum notice and recovery requirements, while still leaving some timing and commercial behavior to registrars [2].
Website and email failures after expiry can result from registration or DNS interruption even when the old zone data still exists at the DNS host.
Redemption Grace Period
When a covered gTLD registration is deleted, the registry generally provides a 30-day Redemption Grace Period. During that period:
- DNS resolution is disabled at the registry level;
- an inter-registrar transfer is prohibited; and
- the registrant at expiration can request restoration through the registrar that deleted the registration.
Restoration can carry a separate fee. Treat redemption as emergency recovery, not a planned renewal strategy.
Pending deletion and release
After recovery rights end, a registration can proceed toward deletion and later become available for a new registration. At that point, the former registrant may have no special priority.
Do not promise an exact release time. Registry processing, registrar behavior, and TLD policy determine what happens for the specific name.
Transfer is not a DNS move
An inter-registrar transfer changes the sponsoring registrar. It does not inherently change:
- the registrant;
- the authoritative nameservers;
- zone records;
- the DNS hosting provider; or
- the website or email provider.
The current ICANN Transfer Policy defines authorization, AuthInfo codes, locks, and conditions under which a gTLD transfer can proceed or be denied [3].
A change of registrant transfers registration rights to another holder. A DNS-provider migration changes authoritative service. Keep these operations separate unless a reviewed plan explicitly coordinates them.
Before an inter-registrar transfer, capture:
- current registrar and registry status codes;
- expiry date and remaining registration term;
- registrant account and recovery access;
- authoritative nameserver set;
- DNS-zone export and DNSSEC state; and
- any active transfer or change-of-registrant lock.
The safest transfer leaves working delegation unchanged and verifies it again after completion.
RDAP is the current gTLD lookup protocol
As of January 28, 2025, ICANN identifies RDAP as the definitive source for gTLD registration information in place of sunsetted WHOIS services [4].
RDAP provides structured responses, standardized service discovery, internationalization support, and differentiated access. ICANN documents the protocol and lookup path [5].
“WHOIS lookup” remains common product language, and some non-gTLD registries may still expose WHOIS. For gTLD investigation, prefer RDAP and label any WHOIS fallback as legacy.
What registration data can establish
Depending on registry policy and access, RDAP can provide evidence about:
- whether a registration exists;
- sponsoring registrar;
- important lifecycle dates;
- registry status codes;
- delegated nameservers; and
- public or redacted registration entities.
It does not by itself prove:
- the identity of a person behind redacted data;
- control of the registrar account;
- control of the DNS host;
- ownership of website content or a trademark; or
- that the delegated DNS service works.
Record the RDAP service, response time, status codes, and redaction state.
Safe operating rule
Monitor renewal from more than one human contact, keep account recovery current, and renew before operational deadlines. If a name has expired, contact the sponsoring registrar immediately and avoid speculative DNS changes until the registration state is understood.
Next step
Once registration and delegation are clear, organize DNS records by the job they perform.