Registrar vs Registry
What a Registry Does for a Top-Level Domain
Registrar vs registry is a question of roles. The registry runs the official database for a top-level domain such as .com, while the registrar sells and manages individual names for the public.
Each top-level domain (TLD) has one registry operator, which keeps the central record of every name registered under that extension. The registry decides which names exist, keeps the record of who holds them and sets the rules for the extension, including its wholesale fees. Registries generally do not sell to individual customers. Instead they work through accredited registrars, which connect to the registry and submit requests on behalf of their customers.
What a Registrar Does for the Customer
The registrar is the company the customer deals with. It checks availability, takes payment, collects the registrant's details and sends the registration to the registry. After that it manages the name, handling renewals, transfers, nameserver changes and support requests.
Registrars compete on price, service and features, and they can differ widely in renewal costs and support quality. A customer usually chooses a registrar directly. The registry for a given extension is fixed, so the choice of registry is not one most customers make.
How the Two Work Together in Practice
When a registration is made, the registrar sends a request to the registry using a standard protocol, usually EPP. The registry checks that the name is free and records the registration. If the registry accepts the request, the registrar confirms the result to the customer. The same pattern applies to renewals, transfers and changes to nameservers or contacts.
The registry holds the authoritative record, which is why registrations can be moved to another accredited registrar under ICANN procedures if a registrar stops operating. The customer's day-to-day contact is the registrar, but the registry remains the place where the name is officially recorded. The full sequence from search to active name is described in how domain registration works.
Two Roles, One Domain: A .org Example
A nonprofit registers a .org name through a registrar in its own country. The registrar is its point of contact for renewals and contact changes. The .org registry, meanwhile, keeps the official record and applies the rules for the extension, including the wholesale fee it charges registrars for each registration.
If the nonprofit later moves the name to a different registrar, the name stays in the same registry under the same .org rules. Only the company managing the name changes, and the registry record is updated to show the new sponsoring registrar.
Frequently asked questions
Can a registrar and a registry be the same company?
Yes, in some cases. Some country-code registries sell names directly to the public, with no separate registrar involved, so the two roles are combined in one organisation. Most generic extensions separate the two roles, with registries and registrars operating as different businesses under ICANN's rules.
Who should I contact about a problem with my domain?
Start with your registrar, since it manages your account and the records it sent to the registry. Most customers never contact the registry directly. Registries mainly handle policy questions and top-level technical matters, while ICANN handles complaints about the accredited companies themselves.
Why does a WHOIS lookup show both a registry and a registrar?
Many lookup results list the registry, which operates the extension, and the registrar of record, which manages the name. Seeing both is normal and reflects the split of roles described above. The fields in these results are explained in what WHOIS is.