A registrar is an accredited organization that registers domain names with top-level domain registries on behalf of customers and manages those registrations throughout their life cycle. In domain names, the registrar is the retail and technical intermediary: the customer, called the registrant, deals with the registrar, and the registrar submits orders, renewals, contact data and name server changes to the registry that operates the TLD.
For generic TLDs such as .com, .org or .shop, registrars are accredited by ICANN and bound by the Registrar Accreditation Agreement, plus a separate agreement with each registry they sell. Country-code TLDs set their own rules, and many accredit registrars directly. The separation between registry and registrar exists to create competition at the retail level while keeping one authoritative database per TLD.
How a registrar works within the domain system
When a customer searches for a domain, the registrar queries the registry to check availability, usually over the Extensible Provisioning Protocol (EPP). If the name is free, the registrar sends a create command with the registration period, the registrant contacts and the name servers, and the registry charges the registrar a wholesale fee.
The registry then publishes the delegation in the TLD zone, so the domain begins resolving through the chosen name servers. The registrar keeps the customer relationship, billing and contact data, and it must make registration data available through RDAP, which has replaced WHOIS as the required lookup protocol for generic TLDs.
Responsibilities are divided among several parties, as the following overview shows.
| Party | Main responsibility | Example action |
|---|---|---|
| Registrant | Holds the right to use the domain | Chooses name servers, renews |
| Reseller | Sells under a registrar’s accreditation | Bundles domains with hosting |
| Registrar | Submits and manages registrations | Sends EPP create and renew commands |
| Registry | Operates the TLD database and zone | Publishes NS records in the TLD zone |
| ICANN or ccTLD authority | Sets policy and accreditation | Enforces transfer and data rules |
The domain life cycle managed by a registrar
A generic TLD registration runs for one to ten years and passes through defined status phases. The registrar is responsible for renewal reminders, expiry handling and deletion, under policies that leave the registrant several chances to recover a lapsed domain.
| Phase | Typical duration | What is possible |
|---|---|---|
| Active registration | 1 to 10 years | Normal use, renewals, updates |
| Add grace period | 5 days after creation | Deletion with refund to the registrar |
| Expiry and auto-renew grace | Up to 45 days, registrar dependent | Renewal at the normal price |
| Redemption grace period | 30 days | Restore for an additional fee |
| Pending delete | 5 days | No recovery; name is then released |
Country-code TLDs often follow different timelines and terminology, and some delete names quickly after expiry. Owners of valuable domains should check the specific policy rather than assume generic TLD rules apply.
Registrar compared with registry and other providers
The registrar is frequently confused with the registry, the hosting company and the DNS provider, partly because one company may offer all of these services. They remain distinct roles with distinct contracts and control points.
| Role | What it controls | Can it be changed independently |
|---|---|---|
| Registrar | Registration, contacts, name server settings | Yes, by domain transfer |
| Registry | The TLD database and wholesale rules | No, fixed per TLD |
| DNS hosting provider | Zone contents such as A and MX records | Yes, by changing name servers |
| Web hosting provider | Servers that deliver the website | Yes, by changing DNS records |
| Reseller | Customer interface and billing | Yes, often via the parent registrar |
Keeping the registrar separate from the hosting provider is a common resilience practice: if a hosting relationship ends badly, the owner can still move the website by changing name servers, without depending on the hosting company’s cooperation.
Transfers, locks and choosing a registrar
A domain moves between registrars through a transfer authorized by an auth code, also called an EPP code or transfer key. The losing registrar must provide it on request, and the domain must not carry a transfer lock. Transfers of generic TLDs usually add one year of registration and are commonly blocked for a period after a new registration or a previous transfer.
Security features differ widely between registrars and matter more than small price differences. Registrar lock sets the clientTransferProhibited status, while the stronger registry lock requires a manual, verified process at the registry before any critical change.
| Criterion | What to look for | Why it matters |
|---|---|---|
| Account security | Strong multi-factor authentication | Account takeover means domain takeover |
| Lock options | Registrar lock, registry lock support | Blocks hijacking and unauthorized moves |
| Renewal pricing | Transparent renewal, not only first year | Prices often rise after the first term |
| DNS features | DNSSEC support, custom name servers | Enables secure and flexible setups |
| Transfer policy | Easy auth code access, no exit fees | Avoids lock-in |
Common problems and risks
Most domain losses are administrative failures, not technical attacks. A domain registered under an employee’s personal account or tied to an expired credit card can lapse quietly, taking a website and email offline at once.
- Outdated contact email: renewal notices and transfer approvals never arrive.
- Auto-renew disabled: the domain enters expiry while the owner assumes it renews.
- Registration under a third party: an agency or former employee legally appears as the registrant.
- Weak account protection: phished registrar credentials allow name server changes and hijacking.
- Bundled lock-in: some providers make auth codes hard to obtain or charge transfer-out fees.
Organizations reduce these risks by registering domains in the company name, using a shared role-based email address, enabling auto-renew with multi-year terms and applying registry lock to critical domains.
Explained without jargon
A registrar is the shop where you rent a website name. The official list of names for each ending, such as .com, is kept by a separate organization. You cannot write into that list yourself, so the registrar does it for you.
The registrar also reminds you to renew, keeps your contact details and lets you point the name to your website. You can move to another registrar if you are unhappy. Your name stays yours as long as you keep paying the rent.
A typical use case
A family-owned manufacturer discovers that its main domain was registered years ago by a former web agency, under the agency’s own registrar account. The agency has closed, and renewal notices go to a dead mailbox.
The company contacts the registrar, proves its rights with business registration documents and has the registrant data corrected. It then requests the auth code, transfers the domain to a registrar that supports registry lock and multi-factor login, and renews it for five years with auto-renew enabled.
Contact details now point to a shared IT address, and name server changes require a verified manual process. The company finally controls its most important digital asset, and the website and email no longer depend on a vanished third party.