web dev//domain//registrant

The registrant is the person or organisation recorded as the holder of a domain, the party that has the right to it for as long as it is renewed. It is a legal role, written in the registration data at the registrar, and it matters most at the moment it was never thought about: when a company wants to change provider and discovers whose name the domain is in.

The registrant is the person or organisation recorded as the holder of a domain, the party that has the right to it for as long as it is renewed. It is a legal role, written in the registration data at the registrar, and it matters most at the moment it was never thought about: when a company wants to change provider and discovers whose name the domain is in.

Four roles around a domain are easy to merge and should be kept apart: the registrant (who holds the right), the account holder (who can log in to the registrar's panel), the administrative or technical contact (who receives the notices), and whoever operates the DNS and the hosting. In a healthy setup the company is the registrant and owns the registrar account, and an agency works through delegated access.

The common trap is an agency, a freelancer or a former employee registering the client's domain under their own name or account. Everything works for years; then the relationship ends, and changing the nameservers or transferring the domain needs the cooperation of someone with no reason to give it.

Control in practice follows the account more than the record. Whoever logs in to the registrar can change the delegation and start a transfer, so the registrar login is protected like a bank account (the company's own email, two-factor authentication), and the registrant data is kept accurate because transfers and disputes are decided on it.

Changing the registrant is a formal step. Under the ICANN transfer policy in force in 2026, a change of registrant for a generic domain is confirmed by both parties and can lock the domain against moving to another registrar for 60 days unless the holder opts out (a revision of the policy, still being implemented, replaces that lock with notifications).

Whoever holds the registrar account holds the website's fate.

Hosting, DNS and code can all be rebuilt in an afternoon; a domain in someone else's name cannot.

The registrant is distinct from the provider roles: the registrar rents the name, the DNS provider answers for it, the host serves the site, and the registrant is who all of them ultimately answer to.