What is Registrant? Definition and meaning
A registrant is the person or entity that holds the contractual right to use a registered domain name under an agreement with an accredited registrar, making them the named holder of record in the domain's registration data.
The registrant is the party who controls the domain – not the registrar (who processes the registration and holds accreditation), not the reseller (who may have sold it), and not the technical contact or administrative contact listed in the registration record. In any domain dispute under the UDRP, the Nominet DRS, or any comparable procedure, the respondent is the registrant: the party who must answer the complaint. All rights, obligations, and dispute exposure attach to the registrant of record at the time a complaint is filed.
This page defines the term precisely, locates it in the rules that govern domain disputes and transactions, and identifies the fact patterns where getting the registrant identity wrong costs real money.
What does registrant mean – and what it is not
The registrant is the contractual counterparty to the registrar – the entity named in the registration agreement as the holder of the domain. That relationship is what the UDRP calls a "registrant" and what the registration data (formerly WHOIS, now RDAP since January 2025) exposes to the public, subject to applicable data-protection redaction.
The term readers most often confuse with registrant is registrar. The registrar is the ICANN-accredited company that processes domain registrations and maintains the technical records. The registrant is the customer – the person or business that pays the annual registration fee and holds the right to use the name. A registrar may also act as a registrant if it registers domains in its own name, but the two roles are legally distinct.
A second source of confusion is the beneficial owner. Privacy services and proxy registrations place a third-party name in the registration record on behalf of the true owner. The proxy is the registrant of record; the beneficial owner is the underlying party whose instructions control the domain. In a domain dispute, panels look through proxy arrangements when sufficient evidence is supplied, treating the beneficial owner as the functional registrant. In a transaction, the beneficial owner is the party whose consent actually releases the domain.
Where does the term registrant appear in the governing rules?
The UDRP defines the parties to every proceeding as the complainant and the respondent, where the respondent is the registrant – the current holder of record. Paragraph 4(a) of the UDRP requires the complainant to establish three elements against that registrant: confusing similarity to a mark, absence of the registrant's legitimate interest, and registration and use in bad faith. The registrant is the subject of all three. A respondent who is not the registrant of record has standing problems; a complainant who names the wrong registrant may see a case dismissed on that basis.
Under the Nominet DRS for .uk domains – now administered by WIPO since 7 July 2026 – the registrant is equally central: the complainant must show that the registrant's registration or use is abusive. The Nominet test reads "registered or used" abusively, a meaningful difference from the UDRP's cumulative standard, but the registrant remains the party at the center of the dispute.
For domain transactions, the registrar's transfer policy (based on ICANN's Inter-Registrar Transfer Policy for gTLDs) requires the current registrant's authorization to move a domain to a new holder. The authorization code – sometimes called the auth code or EPP code – is issued to the registrant. Without it, or without a change-of-registrant process, a transfer cannot complete through normal channels.
How is registrant identity established or challenged?
As of 28 January 2025, ICANN no longer requires registrars to maintain a public WHOIS service. RDAP is the current standard. For individuals, registration data is redacted by default under data-protection rules, so a public RDAP lookup often returns only the registrar, the registration date, and the expiry date – not a name.
To identify a non-disclosed registrant, a party must submit a request through ICANN's Registration Data Request Service (RDRS) or equivalent registrar-specific channels. ICANN extended the RDRS pilot beyond its original two-year term; confirm the current status before relying on it. Each request is assessed by the registrar individually, and disclosure is not guaranteed or automatic. This process can add days or weeks to a pre-dispute investigation – or to domain due diligence before a purchase.
In practice, registrant identity matters most in three situations. First, in a UDRP complaint, the complainant must name the respondent correctly; an incorrect name can create procedural delay or a technical defect. Second, in domain due diligence for a purchase, a prospective buyer must verify that the seller is actually the registrant of record and that no competing claim – a prior dispute, a DENIC DISPUTE entry, or a lock – encumbers the name. Third, in brand-protection monitoring, tracking which registrant holds a portfolio of confusingly similar domains can reveal a coordinated pattern of bad-faith registrations across zones.
Why the registrant identity matters to a buyer or brand owner
Purchasing a domain without verifying the registrant of record is the single most common error in domain transactions. The payment may go to a party who is not the registrant and who cannot authorize the transfer. The domain stays with the original registrant, and the buyer's recourse is in general contract law – a slower and more expensive path than the UDRP.
Consider a scenario: a brand owner receives an offer to sell a domain that matches a competitor's trademark. The seller presents themselves as the owner. The RDAP record shows a privacy-service proxy as the registrant. A proper domain due diligence exercise identifies the beneficial owner, confirms the registrant of record, checks for prior dispute history, and verifies no lock or legal hold is in place – before money moves. Without those steps, closing is a blind transaction.
For complainants in UDRP proceedings, identifying the correct registrant after January 2025 often means filing the RDRS request first, then building the complaint. The timeline for RDRS disclosure is outside the complainant's control, so the investigation phase now requires planning.
For registrants themselves, the key risk is failing to maintain accurate registration data. An out-of-date email address means the registrant misses a UDRP commencement notice. A default – no response filed within 20 days of commencement – almost always results in a transfer against the registrant, regardless of the underlying merits of the dispute.
COGNOMEN handles domain disputes and transactions exclusively. We assess registrant identity, conduct domain due diligence, and advise on transaction structure across gTLDs and ccTLDs. For an assessment of a domain you are buying, selling, or defending, contact info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What is registrant?
A registrant is the person or entity holding the contractual right to a domain name under a registration agreement with an accredited registrar – they are the named holder of record. The registrant is distinct from the registrar (the company that processes registrations) and from any privacy proxy that may appear in the public record in place of the true holder. In a UDRP proceeding, the registrant is the respondent – the party who must answer the complaint or face a default decision.
How is registrant proven or established?
Registrant identity is established through RDAP, the registration data protocol that replaced WHOIS as the standard as of January 2025. Where data is redacted under privacy rules, a disclosure request must be submitted to the registrar through ICANN's Registration Data Request Service or a comparable channel. In disputes, panels may also draw inferences from email addresses, DNS configurations, and evidence submitted by the parties to identify the beneficial owner behind a privacy-service registration.
Why does registrant matter to my domain?
The registrant controls the domain. Only the registrant of record can authorize a transfer, renew the registration, or update DNS. In a domain dispute, the registrant is the party exposed to a transfer or cancellation order. In a transaction, verifying the registrant is the foundation of domain due diligence – paying a seller who is not the registrant of record leaves you without the domain and without a straightforward remedy. Keeping registration data current is equally important: a missed commencement notice due to an outdated email can result in a default judgment under the UDRP.
Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.