Defending Against a UDRP: The Respondent’s Playbook for Keeping Your Domain

· Last reviewed · 17 min read

A UDRP complaint lands as an email from a dispute provider telling you that a trademark owner wants your domain transferred to them. Defending against a UDRP means filing the response that keeps it, and the window to do that is short and fixed.

The honest position is this. A domain registered for a real purpose, with a clean documented history and a registration date that predates the complainant’s mark, is defensible, because the complainant carries the burden of proving three elements and the respondent only has to break one. A domain acquired to ride a known brand is not defensible, and no clever response fixes that. This guide teaches the defensible path with the exact rule citations, not a fear lecture.

It also draws the line every law-firm marketing page blurs. The strongest UDRP defense is built before the complaint arrives, in the diligence done at acquisition. SEO Domains operates the curated marketplace where an aged or expired domain’s registration history and prior use are screened before it is listed, so the provenance that defeats a bad-faith claim is documented from the day you buy.

What defending against a UDRP actually means

Defending against a UDRP means filing a response, as the respondent, that defeats at least one of the three elements the complainant must prove under the Uniform Domain Name Dispute Resolution Policy. The complainant carries the entire burden. The respondent does not have to prove ownership is deserved, only that the complaint fails on rights, on legitimate interests, or on bad faith.

The Uniform Domain Name Dispute Resolution Policy, written by ICANN and administered by providers such as WIPO and the Forum, is an administrative process, not a court case. It decides one question: whether the domain is transferred or cancelled. It cannot award damages, and a parallel court action remains open to either party.

The three elements the complainant must prove

Policy paragraph 4(a) sets out the three elements, and the complainant must establish every one of them. Under 4(a)(i), the domain is identical or confusingly similar to a mark in which the complainant has rights. Under 4(a)(ii), the respondent has no rights or legitimate interests in the domain. Under 4(a)(iii), the domain was registered and is being used in bad faith.

The word that decides the largest share of defenses is the conjunction in the third element. The complainant must prove bad faith in both the registration and the use. A respondent who breaks either half of that conjunctive test defeats the third element, and a complaint that fails any single element fails outright.

Respondent and complainant, defined

The complainant is the party filing to take the domain, almost always a trademark owner. The respondent is the registered domain holder defending it: you. The provider is the dispute body, such as WIPO, that administers the case and appoints the panel. The panel, one or three members, reads the submissions and issues a binding decision the registrar then enforces.

Because the panel decides on the documents alone, with no hearing and no live testimony, the response document is the whole defense. The case for keeping the domain is won or lost on what is written and the evidence attached, which is why the registration record matters as much as the legal argument.

The clock: deadlines, the response window, and the cost of default

The response window is 20 calendar days from the date the proceeding commences, set by UDRP Rules paragraph 5(a), with an automatic 4-day extension available on request. The response is capped at 5,000 words under the WIPO Supplemental Rules. Missing the deadline puts the respondent in default, after which the panel still decides the case and is free to draw adverse inferences from the silence.

The clock is the first thing to understand and the easiest thing to lose on. Everything else in this guide assumes the response is filed inside the window.

The 20-day response window and the extension

Under UDRP Rules paragraph 5(a), the respondent has 20 calendar days from the commencement of the administrative proceeding to submit a response to the provider. Paragraph 5(b) lets the respondent expressly request 4 additional calendar days, and the provider grants that extension automatically and notifies both parties. The window is calendar days, not business days, so weekends and holidays count against it.

The 5,000-word limit and what goes in

The response is capped at 5,000 words under the WIPO Supplemental Rules, paragraph 11(b). One portion is exempt: argument addressing a reverse domain name hijacking allegation carries no word limit, which leaves room to press a counterclaim against an abusive complainant. The response must respond to every statement and allegation in the complaint and annex the supporting evidence.

Procedural itemThe ruleSource
Response deadline20 calendar days from commencementUDRP Rules paragraph 5(a)
Extension4 additional calendar days, automatic on requestUDRP Rules paragraph 5(b)
Word limit5,000 words, no limit on the hijacking portionWIPO Supplemental Rules paragraph 11(b)
Panel compositionSingle member by default, three-member by electionUDRP Rules paragraph 6
DefaultPanel decides on the record, may draw inferencesUDRP Rules paragraph 14
Figure 1. The procedural frame for a UDRP response, cited to the ICANN Rules and the WIPO Supplemental Rules rather than asserted. The deadline and the word limit are hard. The defenses are where the case is decided.

What default costs you

Failing to respond inside the window puts the respondent in default. Default does not hand the complainant an automatic win, because the panel is still appointed and still decides the dispute on the available record. The practical danger is in UDRP Rules paragraph 14: the panel is free to draw such inferences as it considers appropriate from the failure to respond, so unanswered allegations are read in the complainant’s favour. A defensible domain has been lost to a missed email more than once.

Should you defend, settle, or let it go?

Three responses exist: file a defense, consent to transfer through a settlement form, or do nothing and default. The right call follows the evidence. A domain that predates the complainant’s mark, has a genuine use, or is a generic dictionary word is worth defending. A domain registered to target a known brand is a candidate for a negotiated exit, not a losing fight.

The decision is a sober reading of the record before any drafting starts. The trade press is candid that panelists are not bound by precedent and that fact patterns are read differently across cases, so the honest framing is probabilistic, not guaranteed.

Defensible position

Registration predates the complainant’s trademark rights, a real business or content use exists, the domain is a generic or dictionary term, the respondent is commonly known by the name, or the complaint reads as an attempt to seize a legitimately held domain.

Weak position

The domain was acquired with knowledge of the mark, it has been used to confuse or to sell back to the owner, it parks ads that target the brand, or there is no use and no preparation to use that is credible. Here a defense burns money it cannot recover.

Figure 2. The defensibility split. The deciding variable is the documented history of the domain and the intent it evidences, not the eloquence of the response.

Consent to transfer as a clean exit

A respondent who concludes the domain is not worth the fight does not have to default. The WIPO process provides a Standard Settlement Form: complete it, consent to transfer the domain to the complainant, and the case ends without a substantive response and without a panel finding against the registrant. It is the controlled way to walk away, and it avoids an on-the-record loss that then follows the registrant’s name.

The respondent’s defense menu: rights and legitimate interests

Policy paragraph 4(c) gives the respondent three express ways to demonstrate rights or legitimate interests, and proving any one defeats element 4(a)(ii). The three are a bona fide offering of goods or services before notice of the dispute, being commonly known by the domain name, and legitimate noncommercial or fair use. A generic or dictionary-word registration and the Oki Data reseller test extend the same ground.

This is the second element, and it is where a respondent with a real reason for the name wins. Each route is a documented fact, not a rhetorical claim.

The three paragraph 4(c) safe harbours

The Policy lists them in plain language. Under 4(c)(i), before any notice of the dispute, the respondent used the domain, or made demonstrable preparations to use it, in connection with a bona fide offering of goods or services. Under 4(c)(ii), the respondent has been commonly known by the domain name, even without owning a trademark. Under 4(c)(iii), the respondent is making a legitimate noncommercial or fair use of the domain, without intent for commercial gain to misleadingly divert consumers or to tarnish the mark.

The generic and dictionary-word defense

A domain that is an ordinary dictionary word or a descriptive phrase carries its own legitimacy. When the name is generic, the registrant can hold it for its inherent value, and the complainant struggles to show the registration targeted a specific brand instead of the common meaning. The defense weakens if the site’s actual content points at the trademark owner’s industry, so the use has to match the generic claim.

The Oki Data reseller test

Resellers and distributors get a defined route. The Oki Data test, from Oki Data Americas, Inc. v. ASD, Inc., WIPO Case No. D2001-0903, holds that a reseller using a mark in a domain can be making a bona fide offering when three cumulative conditions hold: the respondent is genuinely offering the goods or services, the site sells only the trademarked goods, and the site accurately and prominently discloses the registrant’s relationship to the mark holder. Fail one condition and the defense collapses, so the disclosure line is not optional.

DefenseWhat it provesThe evidence that carries it
Bona fide offering, 4(c)(i)Real use or prep before notice of the disputeDated site captures, invoices, business records predating the complaint
Commonly known by the name, 4(c)(ii)The respondent is identified by the nameTrade name filings, prior branding, public identification with the name
Noncommercial or fair use, 4(c)(iii)Commentary, review, or fan use without commercial diversionContent showing no intent to divert for gain or to tarnish
Generic or dictionary wordThe name has inherent, non-brand valueDictionary meaning, descriptive use, content matching the generic sense
Oki Data reseller test, D2001-0903A legitimate reseller offeringGenuine sales, single-brand site, prominent relationship disclosure
Figure 3. The legitimate-interest defenses under Policy paragraph 4(c) and the case law extending them, each tied to the documentary evidence that proves it. The argument is only as strong as the dated record behind it.

Rebutting bad faith: the registered-and-used test

Element 4(a)(iii) requires bad faith in both registration and use, a conjunctive test the respondent can break at either end. The single strongest rebuttal is a registration date that predates the complainant’s trademark rights, because a domain cannot be registered in bad faith against a mark that did not yet exist. Documented good-faith acquisition and the absence of targeting close the remaining gaps.

Policy paragraph 4(b) lists four non-exhaustive circumstances that evidence bad faith: registering primarily to sell to the mark owner above cost, registering to block the owner as part of a pattern, registering to disrupt a competitor, and using the domain to attract users for commercial gain through confusion. The respondent’s task is to show the facts fit none of them, or that the timeline makes them impossible.

The pre-dating registration: the structural trump card

The cleanest defense in the entire Policy is chronology. When a domain was registered before the complainant acquired trademark rights, panels routinely find that bad-faith registration is impossible, because the respondent cannot have targeted a mark that did not exist at registration. This is the defense that makes an aged domain with a long, documented history so durable: its registration date is a fixed fact in the public record, and that date does the legal work on its own.

Good-faith acquisition and the role of diligence

The timeline is not the only route. Trade analysis from the law firm Taylor Wessing, writing on bad faith in UDRP complaints in 2023, notes that panels have found no bad faith where a domain was acquired in good faith, including through drop-catch services, when the registrant made genuine due-diligence efforts and did not target the mark holder. Diligence at acquisition is evidence, because a record showing the domain was screened for trademark conflicts and bought for its generic or topical value rebuts the claim that it was chased for a brand.

This is the point where sourcing matters to a legal outcome. A domain bought from an unscreened drop list carries no provenance, so the registrant has nothing to show. A domain acquired through a process that documents its registration history and prior use before the sale arrives with the evidence already assembled. Browse curated aged and expired domains with screened registration histories on the SEO Domains marketplace, where the provenance that rebuts bad faith is read before the domain is listed.

No targeting and no confusion

The use half of the test turns on intent to exploit the mark. A site that operates in an unrelated field, parks no brand-targeted advertising, and makes no approach to sell the domain to the mark owner gives the panel nothing under paragraph 4(b). Descriptive marks help the respondent here, because a panel is reluctant to infer that a registrant knew of and targeted a weak or descriptive mark when registering a corresponding common word.

Going on offense: hijacking, delay, and the three-member panel

A respondent with a strong position can do more than defend. A finding of reverse domain name hijacking, under Rules paragraph 15(e), declares the complaint an abuse of the proceeding. Long delay by the complainant can weaken the case even though laches is not a standalone defense. Electing a three-member panel changes the decision-maker for a defined fee.

Reverse domain name hijacking

Reverse domain name hijacking is using the Policy in bad faith to try to deprive a registered holder of a domain. Rules paragraph 15(e) provides that where the panel finds the complaint was brought in bad faith, for example as an attempt at hijacking or primarily to harass the holder, it shall declare that the complaint was brought in bad faith and constitutes an abuse of the administrative proceeding. The finding carries no monetary penalty, but it is a public, on-the-record rebuke of the complainant, and the response portion arguing it carries no word limit.

The laches nuance

Delay is a frequent question and the answer is precise. The consensus view, recorded in the WIPO Overview of Panel Views, is that laches, the doctrine of undue delay, is not a standalone defense under the UDRP. The qualification matters: a long delay in bringing the complaint can make it harder for the complainant to establish the second and third elements on the merits, so delay is an evidentiary argument woven into rights and bad faith, not a procedural bar on its own.

Electing a three-member panel

Under Rules paragraph 6, a single-member panel is the default, but either party can elect a three-member panel. A respondent that makes the election pays half the applicable fees. At WIPO, a single-member case for one to five domains carries a USD 1,500 fee and a three-member case carries a USD 4,000 fee, so a respondent electing three members contributes roughly USD 2,000. The reason to spend it is risk management on a close case: three panelists dilute the impact of one outlier view in a system without binding precedent.

How to build and file your UDRP response, step by step

The response is built in seven stages: preserve the evidence, read the complaint against the three elements, assemble the registration-history record, draft the 4(c) and 4(b) rebuttal, decide on the panel, file inside the 20-day window, and monitor the decision. Each stage pairs the move that strengthens the case with the mistake that sinks it.

The pattern in every stage is the same: the defense rests on dated, documented facts, and the failure mode is reaching the deadline with an argument but no evidence. The sequence below is the build, and the evidence step is where the provenance of the domain decides the outcome.

  1. Preserve the evidence the moment the complaint arrives

    The done-right move is to capture everything before anything changes: dated screenshots of the site, registrar records, the WHOIS or RDAP registration date, invoices, and any correspondence. Read the registration-data context in the WHOIS & RDAP hub so the lookup is read correctly. Freeze the site as it stood; do not redesign it.

    The mistake: altering the site after the complaint to manufacture a use. Panels read post-notice changes as evidence of bad faith, and the change is timestamped against you.

  2. Read the complaint against the three elements

    Map every allegation in the complaint to element 4(a)(i), 4(a)(ii), or 4(a)(iii). The done-right move is to find the single element you can defeat with the cleanest evidence, then build the response around breaking that one leg instead of contesting everything equally.

    The mistake: a scattershot rebuttal that argues all three elements weakly instead of one decisively. A panel needs one element broken, not three half-answered.

  3. Assemble the registration-history record

    This is the stage that wins or loses the bad-faith element. The done-right move is to document the registration date and prior use, and to show the date relative to the complainant’s trademark filing. A domain sourced with screened provenance arrives with this record ready; the acquisition diligence is covered in the Expired Domain Fundamentals hub. Browse screened inventory on the SEO Domains marketplace when the defense depends on a documented clean history.

    The mistake: owning a domain with no provenance trail. Without dated records, the strongest legal argument has no evidence under it, and the panel weighs the unsupported claim against the complainant’s documented mark.

  4. Draft the 4(c) rights and 4(b) bad-faith rebuttal

    The done-right move is to assert the specific 4(c) safe harbour that fits the facts and to rebut each paragraph 4(b) circumstance the complaint raises, citing the WIPO Overview of Panel Views for the consensus position. Respond to every statement in the complaint; silence on a point is read as a concession.

    The mistake: ignoring an allegation because it seems weak. An unanswered claim under paragraph 14 can be taken in the complainant’s favour, so each one needs a line.

  5. Decide single versus three-member panel

    The done-right move is a deliberate choice. On a strong, clean case a single panelist is fine and cheaper. On a close case in a precedent-free system, electing a three-member panel for roughly USD 2,000 dilutes the risk of one outlier view, and the election must be made in the response itself.

    The mistake: defaulting to single-member on a genuinely close case to save the fee, then losing to a single idiosyncratic reading with no second opinion in the room.

  6. File inside the 20-day window, in the right form

    The done-right move is to file the response with the provider before the 20-day deadline under Rules paragraph 5(a), keeping inside the 5,000-word limit, with all evidence annexed and the required certifications. Request the 4-day extension early if the record is large.

    The mistake: treating the deadline as soft. It is 20 calendar days, weekends included, and a missed filing is a default the panel reads adversely.

  7. Monitor the decision and preserve court options

    The done-right move is to track the decision and remember the UDRP is administrative. A transfer order is usually held briefly before the registrar acts, leaving a defined window to file a court action that suspends the transfer if the case warrants it.

    The mistake: treating a loss as the end. The Policy does not displace the courts, and a respondent with a real legal claim can still act, though that path carries its own cost.

Figure 4. The seven-stage response build, each pairing the move that strengthens the defense with the mistake that sinks it. Stage three, the documented registration history, is the foundation the legal argument rests on.

Common UDRP-defense mistakes: the respondent checklist

The errors that lose a defensible domain are a short, repeatable list, and each has a documented fix. The fixes converge on one place: a dated, documented record of the domain’s registration and prior use, assembled before the dispute and not after. Use this as the scannable reference for what a losing response looks like.

The table consolidates the failure modes scattered through the procedure and the defenses into one view. The left column is the mistake, the centre column is why it loses, and the right column is the fix. Read top to bottom, the fixes describe a response built on documented evidence filed on time.

The mistakeWhy it losesThe fix
Missing the 20-day windowDefault lets the panel draw adverse inferences under Rules paragraph 14Calendar the deadline as 20 calendar days from commencement and file early
Arguing all three elements weaklyThe panel needs one element broken decisively, not three half-answeredIdentify the single element with the cleanest evidence and build around it
No registration-history recordThe pre-dating defense has no evidence under itDocument the registration date and prior use; source domains with screened provenance
Altering the site after noticePost-notice changes read as manufactured use and bad faithPreserve and capture the site as it stood the day the complaint arrived
Leaving an allegation unansweredSilence on a point can be taken in the complainant’s favourRespond to every statement and allegation in the complaint
Claiming reseller status without disclosureThe Oki Data test fails if the relationship is not prominently disclosedMeet all three Oki Data conditions, disclosure included, before relying on it
Relying on laches as a barLaches is not a standalone UDRP defenseFrame delay as evidence weakening the second and third elements
Skipping a three-member panel on a close caseOne outlier reading decides it with no second opinionElect three members in the response when the case is genuinely close
Hiring a general practitionerCounsel unfamiliar with UDRP practice misses panel-specific consensusEngage counsel experienced with UDRP and the WIPO Overview of Panel Views
Treating a transfer order as finalThe UDRP is administrative and does not displace the courtsPreserve the court window if a genuine legal claim exists
Figure 5. The respondent mistake checklist. Ten errors that lose a defensible domain, why each loses, and the fix. The right column converges on one move: hold the documented evidence before the dispute arrives, not after.

One pattern runs down the whole fix column. The recurring move is to hold a dated, documented record of how and when the domain was registered and used, assembled at acquisition instead of reconstructed under deadline. A domain with no provenance fails the third row and weakens every row after it, because the strongest legal arguments in the Policy still need evidence to stand on. That is why the documented domain, not the clever response, is the real defense.

UDRP defense frequently asked questions

The five questions domain holders raise when a UDRP complaint arrives, answered against the Policy, the Rules, and the WIPO Overview of Panel Views.

Q1How long do I have to respond to a UDRP complaint?

UDRP Rules paragraph 5(a) gives the respondent 20 calendar days from the commencement of the proceeding to file a response. Paragraph 5(b) allows an express request for 4 additional calendar days, granted automatically. The count is calendar days, so weekends and holidays are included.

Q2What is the single strongest UDRP defense?

A registration date that predates the complainant’s trademark rights. Element 4(a)(iii) requires bad faith in both registration and use, and a domain cannot be registered in bad faith against a mark that did not yet exist. A documented registration date breaks the registration half on chronology alone, and a complaint that fails one element fails outright.

Q3What happens if I ignore a UDRP complaint?

Ignoring it puts you in default. The panel is still appointed and still decides the case on the record, but under Rules paragraph 14 it is free to draw adverse inferences from the silence, and unanswered allegations are read in the complainant’s favour. A defensible domain is lost to a missed deadline.

Q4Does buying a domain at a drop or auction count as bad faith?

Not by itself. Trade analysis from Taylor Wessing notes that panels have found no bad faith where a domain was acquired in good faith, including through drop-catch services, when the registrant made genuine due-diligence efforts and did not target the mark holder. The diligence record at acquisition is the evidence that rebuts the claim.

Q5Can I counterclaim if the complaint is abusive?

Yes, through a reverse domain name hijacking argument under Rules paragraph 15(e). Where the panel finds the complaint was brought in bad faith or to harass, it declares the complaint an abuse of the administrative proceeding. The finding carries no monetary award, but it is a public rebuke, and the response portion arguing it carries no word limit.

The best defense is a documented domain, screened before you buy

Every UDRP defense in this guide converges on one variable: a dated, documented record of how and when the domain was registered and used. A registration date that predates the complainant’s mark and a clean, screened history are the evidence that wins on rights and on bad faith. A domain bought from an unscreened drop list has none of it. SEO Domains operates the curated marketplace where that provenance is documented before the sale.

Why provenance decides the outcome

The legal arguments are settled and public. The pre-dating registration breaks the conjunctive bad-faith test, the paragraph 4(c) safe harbours establish legitimate interest, and the WIPO Overview of Panel Views records the consensus on each. What separates a winning response from a losing one is whether the evidence behind those arguments exists. A domain with a documented history carries its own defense; an unvetted one does not.

What a screened acquisition gives you

A domain acquired through a documented process arrives with the record a UDRP response needs already assembled. The signals that matter to a panel are the same ones a careful acquisition reads before purchase:

  • A verifiable registration date, read from the public record, that fixes the timeline against any later trademark.
  • A prior-use history showing genuine, non-targeting purpose rather than brand exploitation.
  • A clean trademark-conflict screen, so the name was bought for its generic or topical value, not for a known mark.
  • A backlink and content history consistent with the legitimate use the registrant intends to continue.

A domain that passes these is an asset whose defense is written into its own record. A domain that fails them is a liability the moment a complaint arrives, because the response has nothing documented to stand on.

UDRP factorUnvetted drop (liability)Screened acquisition (asset)
Registration dateUnknown or undocumentedVerified against the public record
Prior useNo history to showDocumented, non-targeting purpose
Trademark conflictUnscreened at purchaseChecked before listing
Bad-faith rebuttalArgument with no evidenceEvidence already assembled
Outcome on a complaintExposed from day oneDefensible from the record
Figure 6. Unvetted versus screened, in UDRP terms. The screen is the difference between meeting a complaint with documented evidence and meeting it with an unsupported claim.

Browse aged and expired domains with documented histories

The defensible position behind every UDRP response is a domain you can prove was registered and used in good faith. That proof is a product of how the domain was sourced. SEO Domains operates the curated marketplace where aged and expired domains are screened across their registration history, prior use, and trademark exposure before they are listed and priced, so the provenance that defeats a bad-faith claim is in hand from the day of purchase.

Kalin Karakehayov, Chief Executive Officer at SEO Domains

Kalin Karakehayov

Chief Executive Officer @ SEO Domains · Founder

Kalin is the founder of SEO Domains, the world’s largest supplier of aged domain names across every country and niche. A former professional chess player with 18 years in SEO, he sets the company’s standards for sourcing and screening high-authority domains.

He leads SEO at the SEO Domains marketplace, which operates a 220,000+ curated catalogue from $100 entry-level domains through premium acquisitions, screened across the catalogue, with Managed Account expert support for premium-tier clients.

· Last reviewed