Registering a domain can look simple from the outside: search for a name, pay a registrar, and the domain appears in your account. Behind that checkout screen, however, several different organizations and systems work together to make one registration possible.
Understanding those roles makes it easier to know who actually manages what, where a domain's official record lives, what happens when you renew or transfer it, and who to contact when something goes wrong.
This guide follows a domain through the registration system. It introduces the registrant, reseller, registrar, registry, ICANN, and IANA; walks through registration and registration records; explains the domain lifecycle and transfers; and ends with practical ways to keep control of a registration.
Website hosting, email service, and broader DNS-provider choices are separate topics, so they are only mentioned here when needed to explain the registration system.
When you register a domain, you are not creating a name in isolation. You are asking for a specific name under a top-level domain, such as example.com, to be entered into the registration system for that extension.
The customer-facing company is usually the registrar, but the registrar does not operate the system by itself. The registrar is where you normally search for a domain, complete the registration, renew it, update its settings, and manage many of the controls connected to it. Behind the scenes, the registrar passes registration requests and changes to the appropriate registry.
The registry maintains the authoritative registration database for the top-level domain and processes the requests it receives from registrars. It keeps track of which names are registered under that extension and helps ensure each stays unique. Above that level, ICANN helps coordinate the broader domain name system, and the IANA functions help manage the DNS root zone that connects top-level domains to the wider internet.
ICANN stands for the Internet Corporation for Assigned Names and Numbers. It helps coordinate the global domain name system.
IANA stands for Internet Assigned Numbers Authority. Rather than being a registrar or registry, the IANA functions handle some of the core technical coordination that keeps the internet consistent. In the domain name system, that includes managing the DNS root zone and maintaining authoritative records for top-level domains, so that each TLD can be reached reliably. The IANA functions also coordinate global IP address and protocol number registries.
The registration establishes the domain in the appropriate registry and identifies the registrar responsible for managing it. It creates the official registration record for that name and can remain active even if no website, email, or other service is connected.
A website, email, DNS hosting, forwarding, and other services can be connected to the domain, but they are separate from the act of registering the domain name itself.
A useful way to think about the system is this. The registrar is normally where you manage the domain and submit registration-related changes. The registry maintains the authoritative database of registrations under that top-level domain and processes requests from registrars.
Above that, ICANN and the IANA functions help coordinate the broader naming system and the DNS root zone so top-level domains and their delegations remain unique and consistent. Each layer has a different responsibility, but together they allow a domain to be managed through a registrar while its registration remains part of a much larger global system.
With the basics in place, the next step is to take a closer look at the key players in the domain registration system and the role each one plays.
Registry, registrar, registrant, reseller, and ICANN are terms you may encounter when working with domain names. IANA is another important part of the system, although its name is less commonly encountered by everyday domain owners. Each plays a different role in how the domain registration system works, and the terms are not interchangeable.
The easiest way to understand these participants is to look at each one separately. The sections below explain who each participant is, what role it plays, and how it connects to the overall domain registration process.
The registrant is the individual or organization that registers the domain. The registrant enters into a registration agreement and is responsible for keeping the registration in good standing. This includes keeping the registration information up to date and renewing the domain when required.
Some companies sell domain registrations through another registrar rather than operating as the registrar themselves. You may deal directly with the reseller for the purchase and management of the domain, while an underlying registrar remains the registrar of record.
The registrar accepts registration requests, collects required information, maintains the customer relationship, and sends supported registration commands and updates to the registry.
The registry operator maintains the authoritative registration database for its top-level domain and accepts requests from registrars that are authorized to register names in that TLD.
ICANN accredits registrars, contracts with registry operators, supports the development and implementation of domain name policies, and oversees contractual compliance. ICANN is not the company you normally buy a domain from.
The IANA functions coordinate the DNS root zone and maintain records about top-level domain delegations, including which organization manages each TLD. IANA works at the root level rather than handling individual domains.
Country code top level domains such as .US, .UK or .CA are delegated to their own managers. Each ccTLD is administered under its own policies, and the rules can vary from one country code domain to another. Some may have different eligibility requirements, registration or transfer procedures, renewal rules, or expiration practices than the generic top level domains discussed throughout most of this guide.
If you are ever unsure who actually holds which role, the domain registration record can help identify the registrar of record. IANA's root zone information identifies the organization responsible for each top-level domain.
The names of these roles can sound very similar, especially registrar and registry, but they refer to different parts of the system. A simple way to remember the distinction is that the registrant holds the domain, the registrar handles the registration, and the registry maintains the records for the top-level domain.
Once the roles are clear, the next step is to see how they work together during an actual domain registration. That process begins with the initial search and continues through registration with the registry.
A domain is not truly yours to manage just because a search page says it is available; the registration has to make it through the registrar and into the registry.
The exact checkout screens vary by provider, but the basic path is similar. You choose a name, agree to the registrar's terms, provide the information required for the registration, and the registrar sends the request to the appropriate registry.
The important thing to remember is that an availability search is only the starting point. The registration is complete when the registry accepts the registrar's request and records the domain.
A registry may reserve certain labels or apply eligibility rules, so a name may not be generally available even when it is not registered to another person.
Some registries classify certain names as premium, which can change the registration or renewal price without changing the basic registration process.
Availability can change between a search and the final registry transaction. The successful registry creation is what matters, not an earlier search result.
Some TLDs require extra information or verification. A registrar may also need to validate contact details or complete other checks before the registration is fully usable.
Once the domain exists, the registrar can send later updates supported by the registry, such as renewals, nameserver changes, contact updates, transfer-related commands, or deletion requests. The details depend on the TLD and the type of change.
Completing checkout does not by itself guarantee that the domain has been registered; the registry still has to accept the registration request.
Once a domain has been registered, the system must keep track of the information connected to that registration. Those records identify the domain, its registrar, its status, and other details needed to manage it.
A registration is more than a name and an expiration date. Several pieces of information help identify its registrar, status, technical delegation, and history.
When a domain is registered, the registrar and registry maintain the records associated with it. Those records help show who manages the registration, how the domain is configured, and what actions or restrictions currently apply to it.
The registration record helps answer questions such as who the registrar is, whether the domain is locked, when it was created, and which name servers are delegated. It does not, by itself, tell you everything about the website or email services using the domain.
Keeping registration data is only part of the picture. There also needs to be a standard way to retrieve the portion of that information that is available for public access. That is where RDAP comes in.
For generic top-level domains, RDAP — the Registration Data Access Protocol — is now the standard way to retrieve registration data. It replaced the older WHOIS (pronounced “who is”) protocol as the definitive source for gTLD registration information in 2025, although the word “WHOIS” is still commonly used and some TLDs continue to offer WHOIS services.
RDAP provides a more standardized way to request and return registration data, with features designed to support more secure and controlled access to that information.
Not every piece of registrant information is necessarily public. Privacy laws, ICANN requirements, registry policies, and registrar practices can limit or redact personal data while still making important technical and registrar information available.
One part of the registration data you may encounter is a domain’s status code. These codes help show what actions are currently allowed, restricted, or required for the domain. The examples below are some of the more common statuses you may see.
clientTransferProhibitedA common registrar-applied lock that helps prevent the domain from being transferred to another registrar until the lock is removed.
clientHoldA registrar-applied status that can remove the domain from DNS publication, which can stop normal website and email resolution until the hold is cleared.
serverTransferProhibitedA registry-applied restriction that blocks registrar transfer while the server-side status is in place.
redemptionPeriodA status used when a deleted gTLD registration enters the registry’s Redemption Grace Period, during which the domain may still be restored through the registrar.
These records are not necessarily static. The registrar, name servers, status codes, expiration date, and other details can change as the domain is managed over time.
The information connected to a registration can change as the domain moves through different stages of its life. That leads naturally into the domain life cycle, from an active registration through expiration, recovery, and eventual deletion.
A domain registration lasts for a defined term. If it is renewed, the term is extended. If it is allowed to expire, several different stages may follow before the name eventually becomes available for someone else to register.
The stages that follow expiration can vary, but the examples below show the general path a domain registration may take as it moves toward recovery or eventual deletion.
The period between expiration and final release is where things can become less predictable. During that time, renewal options, recovery costs, and the risk of losing the domain can change as the registration moves through each stage.
Registrar grace periods and post-expiration practices can vary. A registrar may offer a post-expiration renewal period, auction or reassign an expired domain, or follow other procedures permitted under its policies and the applicable TLD rules. Do not assume every registrar handles expiration the same way.
Restoring a domain during the Redemption Grace Period can involve an additional restoration fee on top of the normal renewal cost. These restoration fees can be significantly more expensive than a standard renewal.
Website and email services may be interrupted after a domain expires, even while the registration can still be renewed or recovered.
Once a domain becomes available for registration again, the previous registrant has no guarantee or special right to register it first. Someone else may register the name.
These stages can provide opportunities to recover an expired domain, but they should not be relied on as part of a normal renewal routine. The safest approach is to keep the registration current before those recovery stages are ever needed.
The lifecycle examples above describe common patterns for generic TLDs. Country-code domains and some specialized TLDs may follow different expiration, renewal, recovery, and release rules. For that reason, the registrar and registry policies for the specific extension always matter.
While the domain lifecycle explains how a registration can change over time, a domain does not have to stay with the same registrar. A registrant may choose to move the domain to another registrar, which introduces its own process, safeguards, and restrictions. Moving a domain from one registrar to another is known as a domain transfer.
Moving a domain to another registrar does not require registering it again. Instead, the existing registration is transferred from the current registrar of record to the new registrar through a controlled process.
The transfer changes which registrar manages the domain registration. The domain itself remains the same while responsibility for managing the registration moves to the new registrar.
The domain remains the same, but a different registrar becomes responsible for managing its registration with the registry. For generic TLDs, the transfer requires an authorization code, and if the domain has a transfer lock in place, it must be unlocked before the transfer can proceed.
The registrar stays the same, but the person or organization recorded as the registrant changes. This follows a separate approval process and generally results in a 60-day inter-registrar transfer lock, unless the registrar allows the prior registrant to opt out of the lock before the change.
Changing the services connected to a domain does not transfer the domain to another registrar. These services can include the website, email, hosting, and name servers.
Before a domain can move to another registrar, the transfer has to be properly authorized, and the domain has to be eligible to move. These safeguards help prevent a domain from being transferred without the domain holder's permission.
The exact steps can vary by registrar and domain extension, but most transfers rely on several common pieces. Understanding those pieces makes the transfer process easier to follow and helps explain why a transfer may sometimes be delayed or blocked.
An Auth-Code, sometimes called an EPP or transfer code, helps verify and authorize a transfer between registrars for generic top-level domains.
A registrar lock can block an unauthorized transfer. The domain normally has to be eligible and unlocked before a legitimate transfer can proceed.
Generic TLD transfer policies include situations where a transfer restriction may apply, such as shortly after initial registration, after a recent registrar transfer, or following certain changes to the registrant.
After a successful registrar transfer, registration data will identify the new registrar as the registrar of record. The registry continues to maintain the domain under the same TLD.
A domain transfer can become more complicated when other registration changes are made at the same time. Because some changes can affect transfer eligibility or trigger a temporary lock, it is important to consider the order in which those changes are made.
A properly handled registrar transfer normally does not require you to change the domain name itself. Keeping registration and service changes conceptually separate makes migrations much easier to understand.
Before starting a transfer, review the domain’s current status and any recent registration changes. Taking a moment to check these details beforehand can help prevent unexpected delays or transfer restrictions.
When a transfer is not in progress, the domain should normally remain locked to help protect against unauthorized movement. Transfer security is only one part of maintaining control of a domain, which leads into the next chapter: keeping control of the registration itself.
The most important part of understanding the system is knowing where your authority comes from and protecting the account and information that keep the registration under your control.
A domain can become central to email addresses, websites, sign-ins, business identity, or family history. Losing control of the registration can therefore affect much more than the domain itself.
Keeping control of a domain starts with knowing who manages the registration, securing the account used to manage it, and making sure the registration information stays accurate and accessible.
If you bought through a reseller, know which underlying registrar actually holds the registration.
Use a strong unique password and multi-factor authentication when the registrar supports it.
Renewal, transfer, security, and verification notices depend on accurate contact information connected to the registration.
Know when the domain expires and do not rely on a grace or redemption period as your normal renewal process.
Auto-renew can help, but it only works if the setting, payment method, and registrar account information remain valid.
A transfer lock can add protection against unauthorized registrar transfers when you are not actively moving the domain.
Knowing the delegated name servers helps separate a registration problem from a DNS or service-provider problem.
Keep enough account and identity information available to prove control if you ever lose access to the registrar account or need to prove control of the domain.
Different domain-related issues are handled by different parts of the domain system. Knowing who is responsible for each type of issue can help you find the right place to start when something needs attention.
Start with the registrar or the reseller you purchased through. They are normally the customer-facing path for managing the registration.
Use a current registration data lookup, such as RDAP, the modern replacement for WHOIS, to identify the registrar of record when you are unsure.
The registry operator manages the TLD, while IANA's root zone records identify the organization responsible for that top-level domain.
This may involve a different provider. First, determine whether the registration is in good standing. Then look at the specific service connected to the domain.
The easiest way to stay in control is to know three things at all times:
Once those three pieces are clear, the rest of the system becomes much less mysterious. The registrant manages the registration through the registrar. The registrar communicates with the registry. The registry maintains the TLD's authoritative registration data, and ICANN and the IANA functions help coordinate the broader system around it.
Understanding this structure makes it easier to keep control of a domain as it moves between registrars or connects to different websites, email services, and other providers. The services around a domain may change over time, but maintaining control of the registration helps keep the domain itself under your authority.
Keep the domain locked whenever a transfer is not actively being performed, and keep the registration and account information accurate and up to date. Protect the registrar account with a strong, unique password and multi-factor authentication when available, and make sure the contact information and recovery methods connected to the account remain accessible.
Regularly check the domain’s expiration date, renewal settings, and payment information rather than assuming everything will continue automatically. These simple precautions can help prevent unauthorized transfers, missed renewals, and loss of access while making it much easier to prove and maintain control if a problem ever occurs.
Pay attention to email, text messages, and other notices related to your domain, and check your spam or junk folders so important messages aren't missed. Be cautious of renewal, transfer, security, or account notices, even when they appear legitimate. Do not use links in these messages. Instead, go directly to the registrar's website or account and verify the notice there.