What is Respondent? Definition and meaning

A respondent is the party named in a domain-name dispute proceeding – such as a UDRP complaint, a Nominet DRS filing, or a comparable ccTLD procedure – who holds the disputed domain registration and must answer the complainant's allegations within the prescribed time.

Under the UDRP, the respondent is identified by the registration data (WHOIS/RDAP record) associated with the domain at the time of filing. The respondent's role is procedurally distinct: the complainant bears the initial burden of proof on all three elements of Paragraph 4(a), and the respondent may rebut each element or invoke the Paragraph 4(c) safe harbors to demonstrate a legitimate interest. Receiving a complaint does not determine the outcome; the three UDRP elements must still be proven even if the respondent never files a reply.

This page defines the term precisely, traces it to the governing rules, and describes the patterns in which the respondent's position most commonly arises in practice.

What does respondent mean in a domain dispute – and what it is not

The respondent is the domain holder who answers the complaint. That is the complete, working definition. It is not a synonym for cybersquatter, infringer, or bad-faith registrant – those conclusions follow only from a panel's analysis of the facts, not from the act of being named.

The term readers most often confuse with respondent is registrant. The two overlap almost entirely in practice, but they are not identical. Registrant is the contractual role: the entity or individual named as the domain holder in the registration agreement with the accredited registrar. Respondent is the procedural role: the party the complaint is directed at in the dispute proceeding. In most cases the registrant and the respondent are the same person or entity. They diverge when, for example, a privacy or proxy service is listed in the registration record – the proxy is technically the registrant, yet the underlying beneficial owner is typically named as the respondent once the registrar discloses its identity.

The distinction matters because the panel must determine who is actually controlling the domain. Panels have consistently held that a registrant who uses a privacy service to conceal identity cannot use that service as a procedural shield to avoid being properly served.

Where does the term come from in the rules?

The UDRP Rules define the respondent as the holder of a domain-name registration against which a complaint is filed. That definition is functional: it assigns procedural standing and obligations without making any judgment about the merits. Once a complaint commences, the respondent has 20 days to file a response. Missing that deadline does not waive the complainant's burden – the panel still evaluates whether all three elements of Paragraph 4(a) are satisfied before ordering any remedy.

The safe harbors in Paragraph 4(c) belong to the respondent. A respondent who can show bona fide use before notice of the dispute, a name by which they are commonly known, or legitimate noncommercial or fair use has established a defense that defeats the complaint on element two, regardless of how strong the complainant's trademark rights may be. These are the core instruments of respondent defense, and they turn entirely on the respondent's own conduct and records.

In ccTLD procedures the label varies. Under the Nominet DRS for .uk domains – now administered by the WIPO Arbitration and Mediation Center following the transition on 7 July 2026 – the responding party is also referred to as the respondent. The DRS test differs from the UDRP: it asks whether the registration was "abusive," and crucially reads "registered or used" abusively rather than the UDRP's cumulative "registered and used in bad faith." That lower threshold affects which arguments matter most for a respondent defending a .uk name.

How does the respondent's position play out in practice?

Three recognizable patterns define most respondent situations in our practice.

Pattern one: the generic or descriptive domain. A registrant acquires a common English word or descriptive phrase as a domain name, uses it for years in connection with a genuine business, and later receives a complaint from a brand owner whose mark incorporates the same term. The respondent here typically has a strong Paragraph 4(c) defense: the registration predates any notice of the dispute, and the use is tied to a real product or service. Panels have consistently found for respondents on these facts when the evidentiary record is assembled properly.

Pattern two: the passive or parked domain. A domain sits undeveloped after registration – no active website, no commercial activity. The complainant argues that passive holding constitutes bad faith. The respondent's position is more precarious here. Panels apply a totality-of-circumstances test, looking at the strength and distinctiveness of the complainant's mark, the respondent's apparent awareness of it, and whether any plausible good-faith use could be made of the domain. The absence of a response in this pattern frequently results in a transfer, not because default is automatic, but because the panel has only the complainant's record to assess.

Pattern three: reverse domain name hijacking. A complainant files a complaint knowing the respondent has a legitimate interest – perhaps to pressure a sale or to manufacture a dispute. Where the respondent demonstrates that the complaint was brought in bad faith, panels may issue a finding of Reverse Domain Name Hijacking (RDNH). RDNH carries no monetary penalty, but it is a formal, published finding against the complainant's conduct. In our work defending respondents, an RDNH argument is assessed early, because it frames the entire response strategy.

Why does the respondent's status matter to a domain owner?

Being named as a respondent is time-sensitive. The 20-day response window under the UDRP is strict; extensions are granted sparingly, and only before the window closes. A default does not produce an automatic transfer – the complainant's evidence still governs – but a respondent who defaults surrenders the ability to put forward any Paragraph 4(c) defense, any evidence of good-faith registration, and any RDNH argument. The panel decides on the record it has.

Many respondents receive a complaint and assume, incorrectly, that the process is a foregone conclusion. That is the myth that most damages legitimate domain owners. The three elements must each be proven by the complainant. If element two or element three fails – if legitimate interest exists, or if bad faith is not made out – the complaint fails. A well-prepared response can and does defeat meritless filings.

Identification of the respondent also shapes evidence strategy. If a privacy service is the named registrant, the respondent should engage immediately: registrar disclosure, procedural recognition as the proper respondent, and control of the record all depend on acting within days of receiving notice. For any respondent who received a complaint, the starting point is confirming standing and calculating the response deadline before anything else.

For an assessment of a UDRP complaint and whether a defense or RDNH argument is available in your situation, contact info@cognomenlaw.com.

COGNOMEN focuses only on domain-name disputes – recovery, defense, and transactions. We act for registrants named as respondents before WIPO, the Forum, CAC, ADNDRC, and national ccTLD procedures, and we pursue RDNH findings where the complaint record warrants it. To discuss a defense, reach us at info@cognomenlaw.com.

Related at COGNOMEN

• respondent rdnh – UDRP and ccTLD defense, RDNH findings, and registrant strategy
• What is Trademark rights for UDRP purposes? – how panels assess the complainant's rights under element one
• case defend fair use dev – anonymized defense matter involving fair use and legitimate interest

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). 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.