Responding to a UDRP complaint: what a strong response contains

Why the response matters

A UDRP complaint can feel urgent and one-sided when it arrives. The complainant has already framed the dispute, selected exhibits and presented a theory of bad faith. The response is the respondent’s only formal chance to correct the record and give the panel a complete factual picture.

A strong response does not try to say everything. It says the right things in the right order, tied closely to the Policy. Panels are accustomed to exaggerated rhetoric, speculative claims and hindsight arguments. What tends to help a respondent most is a disciplined submission that is factual, evidenced and legally relevant.

In practical terms, the response should help the panel answer three questions. Is the domain name identical or confusingly similar to a mark in which the complainant has rights. Does the respondent have rights or legitimate interests. Was the domain name registered and used in bad faith.

The first element is often the easiest for a complainant to establish, and in many cases it will not be the main battleground. The response usually matters most on the second and third elements. That is where a respondent can often show that the complainant’s account is incomplete, overstated or simply wrong.

Start with the Policy, not with outrage

Respondents sometimes open with indignation. They may accuse the complainant of overreach, bullying or trying to seize a valuable domain name through pressure. Those points can occasionally matter, especially where reverse domain name hijacking is in issue, but they should not be the foundation of the response.

The foundation should be the structure of the UDRP itself. A well-built response follows the elements of the Policy and makes it easy for the panel to map each factual point to the required legal test. Panels read many cases. They appreciate submissions that are organised, restrained and easy to verify.

A useful response usually includes:

• a short introduction stating the core defence theory
• a concise factual timeline
• a point-by-point answer to the complainant’s allegations
• a section on rights or legitimate interests
• a section on the absence of bad faith registration and use
• properly labelled annexes with source documents

If there are procedural issues, those should be raised clearly but without letting them overwhelm the merits. Examples might include language issues, multiple complainants, defective evidence or late-filed material. Procedure matters, but a response should not assume that technical objections alone will carry the case.

Build a credible factual record

A panel can only decide on the written record. That makes evidence central. A response that merely denies bad faith, without documents or objective context, often leaves the panel with little to work with.

The strongest responses build a timeline from contemporaneous materials. These may include business plans, archived webpages, correspondence, domain portfolio records, company registrations, product drafts, branding explorations, invoices, screenshots and historical WHOIS evidence where available. The aim is not to produce volume for its own sake. The aim is to show what the respondent knew, intended and did at the relevant times.

Timing is particularly important in UDRP disputes. A respondent will often want to show that the domain name was registered for a reason unrelated to the complainant, especially where the term has a descriptive, geographic, acronymic or dictionary meaning. If the complainant’s trade mark rights were weak, local, newly acquired or not reasonably likely to have been known to the respondent at registration, that context should be set out carefully.

Evidence should also address use, not just registration. If the complainant relies on a parked page, an offer for sale or a period of inactivity, the response should explain the surrounding circumstances. Panels know that domain names may be held pending development, used in portfolio management or resolved through registrar-generated pages without bespoke respondent intent. Those facts do not automatically excuse harmful conduct, but they can be highly relevant where intent is disputed.

Show rights or legitimate interests with specifics

The second element is often where a well-prepared respondent can be most persuasive. The Policy recognises that a respondent may have a legitimate basis for holding and using a domain name even where a complainant has trade mark rights.

A strong response should identify the precise basis relied upon. That basis may differ from case to case, but common themes include demonstrable preparations to use the domain in connection with a bona fide offering of goods or services, being commonly known by the domain name, or making legitimate non-commercial or fair use without intent to mislead or tarnish.

Generality is the enemy here. It is not enough to say that the domain is a dictionary word, or that the respondent invests in domain names, or that development was planned. The response should connect the facts to the claimed interest.

For example, if the domain consists of a common term, the respondent should explain that ordinary meaning and show why it was commercially sensible to register it for that meaning rather than for any association with the complainant. If the respondent is a domain investor, the response should demonstrate portfolio consistency. A panel may look more favourably on a portfolio of genuinely descriptive, generic or acronym-based names than on a pattern of domains corresponding to distinctive brands.

Likewise, if there were preparations for a site, annexing drafts, naming notes, supplier emails or development invoices can be far more useful than asserting that plans existed. If the respondent has traded under a corresponding name, then corporate records, customer materials or press references may help establish that it is commonly known by the term.

The practical question is simple. Can the panel see an independent reason why this respondent registered this domain name. If the answer is yes, the complainant’s case becomes materially harder.

Rebut bad faith with a coherent alternative narrative

Bad faith is where many complaints are won or lost. A complainant will often try to infer intent from surrounding facts such as the fame of the mark, website content, pay-per-click links, prior communications, concealment, passive holding or a sale asking price. A strong response addresses each point and then offers a coherent competing narrative.

That narrative should explain why the domain was not registered to target the complainant. In many cases, targeting is the central issue. Panels often look beyond the bare text of the domain name and ask whether the respondent likely had the complainant in mind.

Several factors can help rebut that allegation:

• the term has an obvious descriptive, dictionary, acronym or geographic meaning
• the complainant’s mark was not well known in the respondent’s market or at the relevant date
• the respondent has a consistent pattern of registering names of a similar generic character
• there is no evidence of content aimed at the complainant’s sector, customers or brand
• any parking links were automated and not selected to exploit the complainant specifically
• sale discussions were initiated by the complainant or a broker rather than by the respondent

None of these points is a silver bullet. Panels assess the totality of the circumstances. A respondent should therefore avoid overclaiming. If there are awkward facts, they should be addressed directly.

For instance, if a page displayed links related to the complainant’s industry, the response should explain how the page was generated, whether the respondent controlled keywords, what steps were taken when the issue came to light, and why that does not prove targeting at registration. Similarly, if privacy services were used, the response should treat privacy as a common protective measure rather than as a concealment tactic, while recognising that context matters.

The panel does not need a perfect story. It needs a credible one, supported by evidence, that fits the chronology better than the complainant’s account.

Deal carefully with sale offers, parking and silence

Three recurring issues deserve special attention because complainants often rely on them heavily.

First, offers to sell. The UDRP does not prohibit domain ownership as an asset class, nor does it make every sale discussion suspicious. What matters is why the domain was registered and whether the respondent targeted the complainant or its mark. If there were negotiations, the response should exhibit the correspondence and show who approached whom, what was actually said, and whether the price discussion reflected a general asset sale rather than an attempt to extract value from the complainant’s trade mark position.

Second, parking pages and pay-per-click links. Panels frequently distinguish between automated monetisation and deliberate targeting, but respondents should not assume that automation will excuse everything. The safer course is to explain the parking arrangement, address the link categories shown, and, where true, show lack of control over ad selection. If the links were problematic, evidence of prompt remedial action may assist.

Third, silence or delay. A domain name may sit unused for years. That does not by itself establish bad faith, but neither does it automatically help the respondent. Passive holding cases turn on context. A strong response therefore explains why the domain was held, what plans existed, whether the term has an independent meaning, and why the respondent would have had no reason to target the complainant at registration.

Avoid common mistakes in UDRP responses

Many respondents weaken otherwise defensible cases through avoidable errors. Some focus on moral arguments rather than the Policy. Others submit lengthy narratives with few exhibits. Some attack the complainant so aggressively that the response begins to look evasive.

Common mistakes include:

• failing to address all three elements of the Policy
• relying on bare denials without contemporaneous evidence
• ignoring damaging screenshots or correspondence attached to the complaint
• making exaggerated claims that annexes do not support
• confusing present-day use with registration-date intent
• assuming that generic meaning alone ends the analysis
• omitting a clear chronology

Another frequent problem is inconsistency. If a respondent says the domain was acquired for one purpose, but archived pages, broker outreach or portfolio patterns suggest another, the panel may view the entire defence with scepticism. Internal coherence matters.

Tone matters too. The best responses are measured. They correct errors without theatrics. They acknowledge what is obvious, dispute what is unsupported, and avoid turning a commercial disagreement into a personal contest. Panels tend to respond better to precision than to indignation.

Consider reverse domain name hijacking, but do not force it

Where a complaint is plainly weak, abusive or brought despite clear facts showing the respondent’s legitimate position, a request for a finding of reverse domain name hijacking may be appropriate. Such a finding can be useful. It signals that the complaint should not have been brought in the way it was.

Still, this should usually be a secondary point rather than the central defence. A panel will normally only consider reverse domain name hijacking after dealing with the merits. The response should therefore first show why the complainant failed under the Policy.

If the point is made, it should be grounded in specifics. Examples might include a complainant ignoring obvious dictionary meaning, withholding material chronology, asserting fame without support, or proceeding despite evidence that the respondent registered the domain before the complainant had relevant rights. The argument should be firm but not theatrical.

An overreaching request can distract from stronger substantive points. As with the rest of the response, credibility is the objective.

What a strong final submission looks like

By the end of the response, the panel should be left with a simple and believable conclusion. The complainant may own trade mark rights, but that does not automatically entitle it to this domain name. The respondent had an independent reason for registration, a credible legitimate interest, and no bad faith intent directed at the complainant.

In structure, a strong response is usually clear enough that a panel could lift its logic directly into the decision. It does not bury key facts. It does not ask the panel to infer too much. It makes the chronology easy to follow, ties each argument to the relevant UDRP element, and supports important assertions with documents.

In substance, the strongest responses do three things well. They explain the domain’s ordinary meaning or independent rationale. They show legitimate conduct through evidence rather than conclusion. And they dismantle the allegation of targeting by offering a more persuasive account of registration and use.

Respondents are often at a disadvantage because the complaint arrives as a finished story. The purpose of a strong response is not merely to disagree with that story. It is to replace it with a better one, rooted in record evidence and the actual requirements of the Policy.

If you are assessing the strength of a draft response or the underlying domain facts, Westmore can provide a confidential review.