UDRP Complaint — Template

By Casey Scott McKay · 2026-01-15

This is a complete, filing-ready UDRP complaint with every variable bracketed, organized around the three elements a complainant must prove under Paragraph 4(a) of ICANN's Uniform Domain Name Dispute Resolution Policy. It opens with the decision that comes before drafting — when the UDRP is the right instrument, and the six situations in which a demand letter, a URS petition, an ACPA suit, a platform takedown, or a checkbook is the better answer. It then lists the dates, registration numbers, screenshots, and registration-data printouts you need in hand before you write a word, sets out the model complaint section by section from caption to certification and annex index, and follows with clause-by-clause notes tying each section to the rule that requires it and the panel doctrine that decides it. Alternative clauses cover the unregistered mark, the passive holder, the typosquatter, the former distributor, the multi-respondent consolidation, the language request, and the aggressive and conciliatory registers of the same case. Filing mechanics cover provider choice, fees, the registrar lock, the non-extendable five-day cure period, and the ten-business-day window in which a losing respondent can freeze everything by filing suit. A running example — a Pennsylvania cookware maker, a Seychelles shell company, and three domain names — carries the drafting from intake to transfer.

IP and Technology > Internet | Form | Published 15 January 2026 - Updated 16 July 2026 | Casey Scott McKay - marksy.us

Summary. A complete, filing-ready UDRP complaint with every variable bracketed, built around the three elements of Paragraph 4(a) of the Policy. Start with whether the UDRP is the right instrument at all — and the six cases where it is not. Then the intake list: dates, registration numbers, dated screenshots, registration-data printouts. Then the model complaint itself, caption to certification to annex index, in the form a provider actually accepts. Then clause-by-clause notes tying each section to the rule that requires it and the panel doctrine that decides it. Then the alternatives: unregistered mark, passive holding, typosquatting, former distributor, multiple respondents, language requests, aggressive and conciliatory registers. Then fees, filing, the five-day cure trap, and the ten-business-day window that can undo a win.

Keywords: udrp complaint · uniform domain name dispute resolution policy · icann policy paragraph 4(a) · confusingly similar domain name · rights or legitimate interests · registered and used in bad faith · wipo arbitration and mediation center · forum domain disputes · reverse domain name hijacking · mutual jurisdiction clause · domain name transfer remedy · registrar lock · whois privacy and proxy registrant · pay-per-click parking page · typosquatting · passive holding · oki data reseller test · wipo overview 3.0 · acpa 15 usc 1125(d) · annex index

Template — not legal advice. Replace every [BRACKETED] field. Marksy is not a law firm, and nothing here creates an attorney-client relationship. Have a licensed attorney review anything you intend to file.

What this template is, when to use it, and when not to

This is a model complaint under the Uniform Domain Name Dispute Resolution Policy — the administrative procedure ICANN approved on 24 October 1999 and made effective on 1 December 1999, run today under the Rules effective 31 July 2015 plus whichever provider's supplemental rules you file under. It is the instrument that recovers a domain name from a squatter in six to nine weeks for a four-figure fee, without a court, without discovery, and without personal jurisdiction over anybody.

Get the genre right before you start. A UDRP complaint is not an agreement, and it is not a federal pleading. Nobody signs it but you. There are no parties negotiating terms, no governing-law clause, and no signature blocks for two sides. It is a one-sided administrative submission to a private provider, decided on the documents by a panelist who will never hold a hearing, will never take testimony, and will almost never ask you a question. Everything the panel will ever know about your case has to be inside the four corners of what you file, with the evidence attached and indexed.

The whole document exists to prove three things, and only three things. Policy ¶ 4(a) requires the complainant to establish each of them:

| # | Element | Policy | What it actually turns on | |---|---|---|---| | One | The domain name is identical or confusingly similar to a mark in which the complainant has rights | ¶ 4(a)(i) | Standing plus a side-by-side string comparison. The easiest element. | | Two | The respondent has no rights or legitimate interests in the domain name | ¶ 4(a)(ii) | A prima facie case on negative facts, which then shifts the burden. | | Three | The domain name was registered and is being used in bad faith | ¶ 4(a)(iii) | Conjunctive. Timing. This is where cases are lost. |

Element Three is conjunctive in a way that decides most files before they are opened. Bad faith at registration and bad faith in use — both, separately proved. A domain registered in 2014 cannot have been registered in bad faith against a mark you first used in 2021, no matter how obnoxious today's use of it is. Check the creation date and any transfer date before you do anything else; a renewal is generally not a fresh registration for this purpose, while a transfer to a new holder generally is. WIPO Overview 3.0, § 3.2.1, collects the panel consensus on targeting and knowledge.

Use this template when the domain sits in a gTLD or a ccTLD that has adopted the Policy; your trademark rights predate the registration; and you want the name, not money.

Use something else when:

You want damages. The UDRP's only remedies are transfer and cancellation. Policy ¶ 4(i). Statutory damages of $1,000 to $100,000 per domain name live in the ACPA, 15 U.S.C. § 1117(d), on the claim created by 15 U.S.C. § 1125(d) — see Cybersquatting and the ACPA and, for the strategic comparison, UDRP vs. Federal Lawsuit.
You cannot reach the registrant and the name is valuable. The in rem action of 15 U.S.C. § 1125(d)(2) proceeds against the domain itself in the district of the registry or registrar.
The site is phishing right now. The Uniform Rapid Suspension System takes a new-gTLD name dark in about three weeks on a clear-and-convincing standard. It suspends; it does not transfer. Use it as triage, then bring the UDRP.
The problem is the content, not the name. Copied product photography and site copy come down faster under 17 U.S.C. § 512 — see the DMCA Takedown Notice Checklist and, if the copying justifies a lawsuit, the Copyright Infringement Complaint Checklist and Filing a Copyright Infringement Complaint in Federal Court. Whether you even hold the copyright in that photography is a chain-of-title question answered in the Copyright Fundamentals Toolkit.
The competitor is bidding on your brand, not registering it. That is a keyword problem with its own remedies and its own doctrine; start at the Keyword Advertising Compliance and Enforcement Checklist.
The registration predates your rights, or the respondent has a plausible story. Filing anyway invites a finding of Reverse Domain Name Hijacking under Rules ¶ 1 and ¶ 15(e) — a published finding, in a database clients and opposing counsel read. WIPO Overview 3.0, § 4.16.

The process around this document — provider selection, evidence capture, the go/no-go analysis, what happens after the decision — is in Filing a UDRP Complaint to Recover a Domain, with a pre-flight list in the UDRP Complaint Checklist. If you are on the other side of one of these, read Responding to a UDRP Complaint first. This form is the instrument; those are the operating manual.

Before you start

Have all of it in hand before the first sentence. A complaint drafted around missing evidence reads like one.

| Item | Why the panel needs it | Where it lands | |---|---|---| | Registration certificate and current status printout for every asserted mark | Element One standing; § 1057(b) presumption travels with it | Annex | | Chain-of-title documents if the mark was assigned | Panels reject complaints where the record owner is not the complainant | Annex | | Date of first use in commerce, with proof | Fixes the priority date against the domain's creation date | Section 6, Annex | | Registration data printout for the domain, pulled the day you file | Names the respondent; identifies the registrar and the mutual jurisdiction | Section 4, Annex | | Domain creation date and any transfer date | Decides Element Three before anything else | Section 7(c) | | Dated, full-page screenshots of the resolving page | The page will change the week after you file | Annex | | Internet Archive captures | Shows the use was continuous, not a one-day accident | Annex | | Reverse-registrant portfolio report | Proves the ¶ 4(b)(ii) pattern | Annex | | Prior adverse decisions against the respondent | Same | Annex | | MX and DNS records if email is configured | Supports phishing and impersonation allegations | Annex | | Corporate, trade-name, and assumed-name searches on the respondent's claimed name | Rebuts ¶ 4(c)(ii) in advance | Annex | | Any correspondence between the parties | Required disclosure; an unsolicited offer to sell is worth more than any argument you can write | Annex | | Declaration on use, advertising spend, and recognition — mandatory if the mark is unregistered | Element One standing for common-law rights | Annex |

Trap. Capture the evidence before you contact anybody. The single most common self-inflicted wound in this practice is a demand letter that causes the parking page to disappear, taking Policy ¶ 4(b)(iv) with it. If you are going to send a letter first, screenshot everything, archive it, and hash the files the same day. The Trademark Cease-and-Desist Letter Template and Sending an Effective Cease-and-Desist Letter cover the tone calibration; the Pre-Litigation Enforcement Checklist covers the sequencing.

The running example. Thrumwell Ironworks, Inc., a Lancaster, Pennsylvania cast-iron cookware maker, has used THRUMWELL since 2015 and registered it on the Principal Register in 2019 for cookware in Class 21. On 3 February 2026 its marketing lead finds thrumwell-outlet.com resolving to a parked page of pay-per-click links headed "Cast Iron Skillets" and "Dutch Ovens." Registration data shows a privacy service; the creation date is 11 November 2025. Two more names — thrumwel.com and thrumwell.shop — share the registrant email. That fact pattern runs through the drafting notes below.

The model complaint

Everything between the rules is the instrument. Adapt it; do not file it as written.

BEFORE [THE WIPO ARBITRATION AND MEDIATION CENTER / FORUM]

ADMINISTRATIVE PROCEEDING UNDER THE UNIFORM DOMAIN NAME DISPUTE RESOLUTION POLICY

[COMPLAINANT LEGAL NAME], Complainant

[RESPONDENT NAME EXACTLY AS SHOWN IN THE REGISTRATION DATA], Respondent

Disputed domain name[s]: [<domain-name.tld>]

Provider Case No.: [ASSIGNED ON FILING]

COMPLAINT

1. Submission. This Complaint is submitted for decision in accordance with the Uniform Domain Name Dispute Resolution Policy (the "Policy"), adopted by the Internet Corporation for Assigned Names and Numbers on 24 October 1999 and effective 1 December 1999; the Rules for Uniform Domain Name Dispute Resolution Policy (the "Rules"), effective 31 July 2015; and the [PROVIDER] Supplemental Rules, effective [DATE]. Rules ¶ 3(b)(i).

2. Complainant. Rules ¶ 3(b)(ii)–(iii).

(a) Name: [COMPLAINANT'S FULL LEGAL NAME, INCLUDING ENTITY TYPE] (b) Address: [ADDRESS] (c) Telephone: [NUMBER] (d) Email: [ADDRESS] (e) Preferred method for all case communications: email to [SINGLE MONITORED ADDRESS] (f) Complainant elects a [single-member / three-member] administrative panel. Rules ¶ 3(b)(iv). [If three-member: Complainant's three candidates, in order of preference, are [NAME 1], [NAME 2], and [NAME 3].]

3. Complainant's Authorized Representative. [NAME], [FIRM], [ADDRESS], [TELEPHONE], [EMAIL]. All communications should be directed to the representative. Rules ¶ 3(b)(ii)–(iii).

4. Respondent. Rules ¶ 3(b)(v).

(a) Name: [REGISTRANT NAME AS SHOWN IN THE REGISTRATION DATA, INCLUDING "REDACTED FOR PRIVACY," THE PRIVACY SERVICE NAME, OR "JOHN DOE" IF UNAVAILABLE] (b) Address: [AS SHOWN] (c) Telephone / Email: [AS SHOWN, INCLUDING ANY ANONYMIZED RELAY ADDRESS] (d) [Complainant's efforts to identify Respondent consisted of [DESCRIBE SEARCHES RUN AND DATES]. Complainant will amend this Complaint upon the Registrar's disclosure of the underlying registrant.]

5. Respondent's Authorized Representative. [NAME AND CONTACT DETAILS / Complainant is not aware that Respondent is represented.]

6. Disputed Domain Name, Registrar, and Complainant's Mark. Rules ¶ 3(b)(vi)–(viii).

(a) Disputed domain name[s]: [domain-name.tld], created [DATE], as shown in the registration data printout at Annex [N].

(b) Registrar: [REGISTRAR NAME], [ADDRESS], [TELEPHONE], [EMAIL].

(c) Complainant is the owner[, by assignment,] of all right, title, and interest in the [trademark / service mark] [MARK] (the "Mark"), including the following registration[s]:

| Mark | Jurisdiction | Reg. No. | Reg. Date | Class / Goods and services | |---|---|---|---|---| | [MARK] | [United States] | [NUMBER] | [DATE] | [NN] — [IDENTIFICATION] |

The registration is valid and subsisting[ and has become incontestable under 15 U.S.C. § 1065]. A certificate and current status printout are at Annex [N]. [Chain-of-title documentation is at Annex [N].]

(d) Complainant has offered [goods / services] under the Mark continuously since [DATE OF FIRST USE IN COMMERCE], and has spent approximately [$AMOUNT] promoting the Mark since [YEAR]. Complainant operates its principal website at [complainant-domain.com], registered [DATE]. Annex [N].

7. Factual and Legal Grounds. Rules ¶ 3(b)(ix).

(a) The disputed domain name is [identical / confusingly similar] to a mark in which Complainant has rights. Policy ¶ 4(a)(i); Rules ¶ 3(b)(ix)(1).

Complainant's registration establishes its rights in the Mark for purposes of Policy ¶ 4(a)(i). The disputed domain name [reproduces the Mark in its entirety / is a single-character misspelling of the Mark / incorporates the dominant element of the Mark] and adds only [the descriptive term "[TERM]" / a hyphen / the geographic term "[TERM]" / nothing]. Neither the added [term / punctuation] nor the "[.tld]" top-level domain distinguishes the domain name from the Mark; the top-level suffix is disregarded as a technical requirement of registration. The addition of a descriptive or geographic term to a complainant's mark does not avoid confusing similarity, and where the mark remains recognizable within the domain name the test of Policy ¶ 4(a)(i) is met. See WIPO Overview 3.0, §§ 1.7, 1.8, 1.11.1.

[[MARK] is a coined term with no dictionary meaning in any language, used by no one but Complainant.]

(b) Respondent has no rights or legitimate interests in the disputed domain name. Policy ¶ 4(a)(ii); Rules ¶ 3(b)(ix)(2).

Respondent registered the disputed domain name on [DATE] — [NUMBER] years after Complainant's first use of the Mark in commerce and [NUMBER] years after the Mark registered.

Respondent is not, and has never been, a licensee, distributor, reseller, affiliate, or agent of Complainant, and has never sought or received authorization to register or use the Mark in any form.

Upon information and belief, Respondent is not and has never been commonly known by the disputed domain name within the meaning of Policy ¶ 4(c)(ii). The registration data identifies Respondent as "[NAME]," which bears no resemblance to the domain name, and searches of [JURISDICTIONS SEARCHED] corporate, trade-name, and assumed-name registries return no entity by that name. Annex [N].

Respondent has made no use of, and no demonstrable preparations to use, the disputed domain name in connection with a bona fide offering of goods or services under Policy ¶ 4(c)(i). The domain name resolves to a parked page consisting exclusively of pay-per-click advertising under the headings "[HEADING]," "[HEADING]," and "[HEADING]" — the same [goods / services] Complainant sells under the Mark, and in several instances links to Complainant's direct competitors. Annex [N]. Internet Archive captures show the identical page from [DATE] through [DATE]. Annex [N]. Use of a domain name incorporating another party's mark to host pay-per-click links that capitalize on or compete with that mark is neither a bona fide offering under Policy ¶ 4(c)(i) nor a legitimate noncommercial or fair use under Policy ¶ 4(c)(iii). See WIPO Overview 3.0, §§ 2.9, 3.5.

Complainant has therefore made out a prima facie case that Respondent lacks rights or legitimate interests, and the burden of production shifts to Respondent. See WIPO Overview 3.0, § 2.1; Croatia Airlines d.d. v. Modern Empire Internet Ltd., WIPO Case No. D2003-0455.

(c) The disputed domain name was registered and is being used in bad faith. Policy ¶ 4(a)(iii); Rules ¶ 3(b)(ix)(3).

Registration. At the time of registration on [DATE], Complainant's Mark had been in continuous use for [NUMBER] years, was the subject of a [jurisdiction] registration issued [DATE], and appeared as the first organic result for a search of "[MARK]." [The Mark is a coined term; there is no plausible circumstance in which Respondent arrived at it independently.] Respondent registered the domain name with knowledge of the Mark and to target it. Policy ¶ 2 required Respondent to represent on registration that the domain name would not infringe the rights of any third party. See WIPO Overview 3.0, § 3.2.1.

Use. By using a domain name that incorporates the Mark to host advertising for [goods / services] competing with Complainant's, Respondent has intentionally attempted to attract internet users to an online location for commercial gain by creating a likelihood of confusion with the Mark as to source, sponsorship, affiliation, or endorsement. Policy ¶ 4(b)(iv). Respondent, or a party acting on Respondent's behalf, receives click-through revenue from those links; a registrant is responsible for the content appearing on a parking page whether or not it selected the individual links. See WIPO Overview 3.0, § 3.5.

[Pattern. Respondent, or the registrant email address associated with Respondent, holds at least [NUMBER] other domain names, of which at least [NUMBER] correspond to third-party trademarks unrelated to Respondent, including [domain] and [domain]. Annex [N]. Respondent has been ordered to transfer domain names in at least [NUMBER] prior proceedings. Annex [N]. This is a pattern of registering domain names to prevent mark owners from reflecting their marks in corresponding domain names. Policy ¶ 4(b)(ii).]

[Offer to sell. On [DATE], Respondent [offered to sell the domain name to Complainant for $AMOUNT / listed the domain name for sale at $AMOUNT], a sum plainly in excess of Respondent's out-of-pocket costs directly related to the domain name. Annex [N]. Policy ¶ 4(b)(i).]

Taken together, these circumstances admit of no plausible good-faith use of the disputed domain name by Respondent.

8. Remedy Sought. Complainant requests that the Panel issue a decision that the disputed domain name registration be [transferred to Complainant / cancelled]. Rules ¶ 3(b)(x); Policy ¶ 4(i).

9. Other Legal Proceedings. [There are no legal proceedings that have been commenced or terminated in connection with or relating to the disputed domain name. / DESCRIBE EACH PROCEEDING, INCLUDING PRIOR UDRP CASES, WITH CASE NUMBER, FORUM, AND STATUS.] Rules ¶ 3(b)(xi).

10. Mutual Jurisdiction. Complainant will submit, with respect to any challenges to a decision in this administrative proceeding cancelling or transferring the disputed domain name, to the jurisdiction of the courts at [the location of the principal office of the Registrar / the location of Respondent as shown in the Registrar's registration data at the time this Complaint is submitted], namely [CITY, STATE/COUNTRY]. Rules ¶ 3(b)(xii).

11. Certification. Rules ¶ 3(b)(xiii).

Complainant agrees that its claims and remedies concerning the registration of the domain name, the dispute, or the dispute's resolution shall be solely against the domain-name holder and waives all such claims and remedies against (a) the dispute-resolution provider and panelists, except in the case of deliberate wrongdoing, (b) the registrar, (c) the registry administrator, and (d) the Internet Corporation for Assigned Names and Numbers, as well as their directors, officers, employees, and agents.

Complainant certifies that the information contained in this Complaint is to the best of Complainant's knowledge complete and accurate, that this Complaint is not being presented for any improper purpose, such as to harass, and that the assertions in this Complaint are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument.

Respectfully submitted,

/s/ [NAME] [NAME], [TITLE] [Authorized Representative of Complainant] Dated: [DATE]

12. Annexes. Rules ¶ 3(b)(xiv).

| Annex | Contents | |---|---| | 1 | The Policy [or citation, per the provider's practice] | | 2 | Registration certificate and current status printout | | 3 | Registration data printout for the disputed domain name, dated | | 4 | Dated screenshots of the resolving page | | 5 | Internet Archive captures | | 6 | Corporate and trade-name search results | | 7 | Reverse-registrant portfolio report | | 8 | Prior adverse decisions against Respondent | | 9 | Correspondence between the parties | | 10 | Declaration of [NAME] on use and recognition of the Mark |

Clause-by-clause drafting notes

Section 1 — Submission. Rules ¶ 3(b)(i) requires the request; the dates are what get you a deficiency notice. Providers amend their supplemental rules, and a stale effective date is one of the most common administrative rejections in the practice. Pull the current supplemental rules from the provider's site the morning you file and copy the date from the document itself.

Section 2 — Complainant. Full legal name, matching the entity that owns the registration. If the mark sits in a holding company and the operating company is the one being harmed, the complainant is the holding company — or both, filed jointly with a sentence explaining the common grievance. A licensee can complain with the owner's authorization, but attach the authorization. Section 2(e) matters more than it looks: name one monitored inbox, because every deadline in the proceeding runs from provider email, and the response window is twenty days.

Section 2(f) is the panel election under Rules ¶ 3(b)(iv). Take the single member in the ordinary case. Buy three where the mark is descriptive, where the respondent has a colorable story, where the amount at stake justifies insurance against an outlier panelist, or where you need a reasoned decision you can cite later. Note the asymmetry in Rules ¶¶ 5(b)(iv) and 6(c): if you ask for one and the respondent asks for three, the cost is split; if you ask for three, you pay all of it.

Section 3 — Representative. Counsel is not required by the Policy, the Rules, or any provider's supplemental rules. Naming a representative routes all communications to counsel, which is worth doing for docketing reasons alone.

Section 4 — Respondent. Rules ¶ 3(b)(v). Copy the registration data verbatim, including "REDACTED FOR PRIVACY" or "Registration Private." Since the GDPR took effect in 2018 most gTLD registration data is masked, and ICANN's Temporary Specification for gTLD Registration Data expressly permits filing without the registrant's identity. Name the privacy or proxy service as respondent, describe the searches you ran, and expect to amend. In the Thrumwell example the original complaint names "Withheld for Privacy ehf"; the registrar's verification response discloses Cobalt Meridian Ltd., Mahé, Seychelles; the amended complaint names both.

Practice tip. Draft the amended complaint in skeleton form before you file the original. The disclosure arrives within about two business days, the cure period is five calendar days and is not extendable under Rules ¶ 4(d), and the amendment usually has to change three things at once: the respondent's name, the mutual jurisdiction clause, and any language request.

Section 5 — Respondent's representative. Usually omitted or answered in the negative. Include it where a lawyer answered your demand letter. This is also the right place to plead aliases if the respondent operates under several.

Section 6 — Domain, registrar, mark. Verify the registrar on the day of filing; names move, and a complaint naming the wrong registrar is a deficiency. Section 6(c) is where standing lives. A live registration in any jurisdiction satisfies Policy ¶ 4(a)(i) — the panel will not second-guess the registrability of a registered mark. Say if the mark is incontestable under 15 U.S.C. § 1065, and say if it is coined or arbitrary, because both facts do quiet work at Element Three. If the mark came by assignment and the register still shows the assignor, attach the executed assignment, the merger acknowledgment, or the name-change certificate; panels accept those even without recordation, but they will not simply take your word for it. The recordal mechanics are in the Trademark Assignment Recordal Checklist, and the deal-level chain-of-title problems in Trademarks in the Deal.

Section 7(a) — Element One. This is a string comparison, not a likelihood-of-confusion analysis. The multifactor federal test described in Trademark Infringement: Proving Likelihood of Confusion has no application here; panels ask only whether the mark is recognizable within the domain name. Two consequences. First, do not import DuPont or Sleekcraft factors — it signals unfamiliarity. Second, do not argue the respondent's website content at this element; it belongs at Elements Two and Three. Keep this section to three or four sentences. If it runs longer than a paragraph, something is wrong with the case.

Section 7(b) — Element Two. You are proving a negative, which is why the doctrine gives you a burden-shifting device: make a prima facie showing and the burden of production moves to the respondent. WIPO Overview 3.0, § 2.1. The four sentences that do the work are always the same — no license, no authorization, not commonly known by the name, no bona fide offering — and each needs an annex behind it. The corporate and trade-name searches are the piece people skip; running them costs an hour and forecloses the most common respondent defense under Policy ¶ 4(c)(ii).

Anticipate the defenses rather than waiting for them. If the domain contains a dictionary word, address why the use has nothing to do with the dictionary meaning. If the respondent is a reseller, address the Oki Data factors below. If the site is a criticism site, understand that you are in genuinely contested territory: panels split on whether a [mark]sucks.com gripe site can be a legitimate fair use, and U.S. courts have been protective of noncommercial criticism, as in Lamparello v. Falwell, 420 F.3d 309 (4th Cir. 2005), and Bosley Medical Institute, Inc. v. Kremer, 403 F.3d 672 (9th Cir. 2005). A UDRP against a genuine gripe site is a bad bet.

Section 7(c) — Element Three. Split it into "Registration" and "Use" under separate sub-headings, because the element is conjunctive and panels are looking for both. Then pick your ¶ 4(b) circumstance and plead it by number. The four enumerated circumstances are non-exhaustive; ¶ 4(b)(iv) — attracting users for commercial gain through confusion — carries the ordinary parking-page case, and ¶ 4(b)(ii) — pattern — is the one that turns a marginal case into a comfortable one when you can prove it.

The pattern paragraph is worth the research budget. A reverse-registrant search that shows forty-odd domains, eleven of them other people's brands, converts a squatter into a serial squatter, and serial squatters lose. So does a respondent with prior adverse decisions; provider databases are searchable and free, and Policy ¶ 4(j) means the decisions are published.

Section 8 — Remedy. Ask for transfer. Cancellation releases the name into the general pool, where the same person re-registers it through a different nominee and you pay the fee again. Choose cancellation only where the name is genuinely toxic — a string built for phishing that you never want associated with the brand — or where the registry's transfer mechanics create a problem.

Section 9 — Other proceedings. Disclose everything touching the domain, including earlier UDRP cases you lost. Rules ¶ 3(b)(xi). Under Rules ¶ 18(a) a panel may suspend, terminate, or proceed where litigation is pending. Concealment here is the fastest available route to an RDNH finding.

Section 10 — Mutual jurisdiction. The one line in the form with real strategic content. You are contractually consenting to be sued somewhere. Rules ¶ 1 gives you two options: the registrar's principal office, or the respondent's address in the registration data. Choose the registrar almost always — a U.S. registrar puts any challenge in a U.S. district court applying U.S. law. Choosing a Seychelles respondent's address hands a squatter the option of suing you in the Seychelles, which is a threat with real settlement value and no upside for you.

Section 11 — Certification. Both paragraphs, verbatim, then the signature. Rules ¶ 3(b)(xiii). People delete the second paragraph by accident when trimming a template, and providers catch it every time. The certification is also the hook for an improper-purpose finding, which is another way of saying that Section 11 is where a weak complaint becomes a sanctionable one.

Section 12 — Annexes. Rules ¶ 3(b)(xiv) plus the supplemental rules require an indexed set of exhibits filed as a separate document. Number the annexes, cite them inline, and make every screenshot show the URL and the capture date. An unindexed evidence dump earns a deficiency notice; an un-annexed registration certificate earns a denial on standing.

Alternative and optional clauses

Unregistered or common-law mark. Panels accept unregistered rights, but you must prove them, and a bare assertion fails. Replace Section 6(c) with a paragraph establishing secondary meaning as of the domain's registration date, supported by a sworn declaration:

Complainant has used the [MARK] mark continuously in commerce since [DATE] in connection with [GOODS/SERVICES]. Complainant's revenues under the Mark exceeded $[AMOUNT] in [YEAR]; Complainant has spent $[AMOUNT] advertising under the Mark since [YEAR]; the Mark has been the subject of unsolicited coverage in [PUBLICATIONS] (Annex [N]); and Complainant's social accounts under the Mark have [NUMBER] followers. By [DATE OF REGISTRATION OF THE DISPUTED DOMAIN NAME], the Mark had acquired distinctiveness and served to identify Complainant as the source of [GOODS/SERVICES]. Declaration of [NAME], Annex [N]. See WIPO Overview 3.0, § 1.3.

The evidence architecture is the same one the USPTO wants for acquired distinctiveness — see From Descriptive to Distinctive, the Secondary Meaning Evidence Checklist, and Claiming Acquired Distinctiveness at the USPTO. For the priority and territory proof, Establishing and Proving Common-Law Trademark Rights and the Common-Law Priority Evidence Checklist cover it. If you are reading this and the mark is not registered, the cheapest fix is usually to register it — start with the Trademark Clearance Search Checklist.

Passive holding. A domain that resolves to nothing can still be used in bad faith. Add to Section 7(c):

The disputed domain name does not resolve to any active website. Passive holding does not preclude a finding of bad faith where, as here, the Mark is [coined and well known], Respondent has provided [false / no] contact details, Respondent has concealed its identity behind a privacy service, and no plausible good-faith use of the domain name by Respondent is conceivable. See Telstra Corp. Ltd. v. Nuclear Marshmallows, WIPO Case No. D2000-0003; WIPO Overview 3.0, § 3.3. Configured MX records show the domain name is provisioned to send and receive email (Annex [N]), creating a standing risk of impersonation of Complainant.

Typosquatting. Where the domain is a misspelling, say so plainly and name the mechanism — transposed letters, dropped character, adjacent-key substitution, homoglyph:

The disputed domain name is a single-character deletion from Complainant's [MARK] mark and has no meaning in any language. Registration of a common misspelling of a mark to capture traffic intended for the mark owner is itself evidence of bad faith. See Hewlett-Packard Co. v. Zuccarini, FA 94454 (Nat'l Arb. Forum May 30, 2000).

Former distributor, reseller, or licensee. The hardest respondent to beat, and the case where the template has to change most. Under the Oki Data framework — Oki Data Americas, Inc. v. ASD, Inc., WIPO Case No. D2001-0903; WIPO Overview 3.0, § 2.8.1 — a reseller may hold a legitimate interest if it actually offers the goods, sells only those goods, accurately discloses its relationship with the mark owner on the site, and has not cornered the relevant domain space. Plead the failures, factor by factor:

Respondent's website does not accurately disclose Respondent's relationship with Complainant; it displays Complainant's logo and the statement "[QUOTE]," which falsely implies an authorized relationship. Annex [N]. Respondent also offers competing [GOODS] from [THIRD PARTY]. Annex [N]. Respondent's authorization terminated on [DATE] (Annex [N]), and any interest it may once have had ended with it.

If a written distribution or license agreement governs, ask whether this is a contract case rather than a UDRP case. Panels decline disputes that are really commercial disputes in costume. Drafting a Trademark License That Survives explains the domain-name and post-termination clauses that would have prevented this. On the defense side, Descriptive and Nominative Fair Use is the doctrine the respondent will invoke.

Multiple domains and multiple respondents. Consolidate. Provider fees are tiered by domain count, so five names in one complaint often cost what one costs. Multiple names held by one registrant consolidate as of right; multiple respondents require a showing under Rules ¶ 10(e):

The [NUMBER] disputed domain names are subject to common control. Each was registered through [REGISTRAR] within [PERIOD]; each uses the registrant email [address]; each resolves to a page served from IP address [ADDRESS] using an identical template; and each incorporates a third-party trademark. Annex [N]. Consolidation is fair and equitable to all parties and procedurally efficient. Rules ¶ 10(e); WIPO Overview 3.0, § 4.11.2.

Language of the proceeding. Rules ¶ 11(a) makes the registration agreement's language the default. If it is Chinese or Russian and the respondent plainly reads English, request English and give reasons — the site is in English, prices are in dollars, correspondence was in English — or budget for translation.

The aggressive register. Use where the respondent is a proven serial squatter: lead Section 7 with the pattern evidence rather than the string comparison, attach the prior decisions, plead ¶¶ 4(b)(i), (ii), and (iv) in the alternative, name every alias, and ask for three panelists so the decision carries citable weight. Where phishing or malware is involved, say it in the first paragraph and attach the security-vendor report.

The conciliatory register. Use where the respondent may be a genuine mistake — a fan, a small business with a coincidental name, a developer who registered a name for a client. Drop the pattern paragraph, drop adjectives entirely, plead ¶ 4(b)(iv) alone, and open a settlement channel through the provider. Rules ¶ 17 requires termination on settlement, and providers will suspend a case, typically for thirty days, to let a stipulated transfer close. A suspension plus a transfer is faster and cheaper than a decision and preserves part of your fee.

Filing mechanics

Where it goes. Any ICANN-approved provider: WIPO, FORUM, the Asian Domain Name Dispute Resolution Centre, the Czech Arbitration Court, or the Arab Center for Domain Name Dispute Resolution. WIPO and FORUM decide the overwhelming majority of cases. Filing is electronic through the provider's portal. Match the model complaint to the provider you choose — FORUM's model is more prescriptive and page-limited, WIPO's is more narrative and word-limited.

Limits. WIPO caps the Paragraph 4(a) argument section at 5,000 words. FORUM caps the complaint at fifteen pages excluding annexes. Nobody has ever lost a UDRP case for brevity.

Fees. Paid by the complainant at filing, tiered by domain count and panel size. Budget roughly $1,500 for a single-member WIPO case covering one to five domains and roughly $4,000 for a three-member panel; FORUM's single-member fees run somewhat lower. Fee schedules change — pull the provider's published schedule before you quote a client a number. Rules ¶ 19 governs; providers refund a declining share of the fee if the case settles before the panel is appointed, which is another argument for suspending early.

You do not serve the respondent. Rules ¶ 2(a) puts service on the provider. Under Rules ¶ 4(a)–(b), the provider asks the registrar to verify the registration and lock the domain within two business days, before the respondent is notified. The lock prevents transfer or deletion for the life of the proceeding — which is why the cyberflight problem that used to plague this practice has mostly disappeared.

The clock.

| Event | Authority | Timing | |---|---|---| | Complaint filed, fee paid | Rules ¶¶ 3, 19 | Day 0 | | Registrar verifies and locks | Rules ¶ 4(b) | 2 business days | | Provider forwards after compliance review | Rules ¶ 4(c) | 3 calendar days from fee receipt | | Deficiency cure | Rules ¶ 4(d) | 5 calendar days — not extendable | | Commencement | Rules ¶ 4(c) | All later deadlines run from here | | Response due | Rules ¶ 5(a) | 20 days | | Automatic extension on request | Rules ¶ 5(b) | + 4 days | | Panel appointed | Rules ¶ 6(b), (e) | 5 calendar days after response or lapse | | Decision to provider | Rules ¶ 15(b) | 14 days from appointment | | Decision communicated | Rules ¶ 16(a) | 3 calendar days | | Registrar implements | Policy ¶ 4(k) | 10 business days, absent a court filing |

Calendar these five things the day you file: the two-business-day lock confirmation; the five-day cure window; the commencement date when it arrives; the response deadline plus four days; and the ten-business-day implementation window after a favorable decision. The general docketing discipline is in Docketing Deadlines: Never Miss a Renewal.

After a win. Policy ¶ 4(k) gives the respondent ten business days to file suit in a mutual jurisdiction and freeze implementation. That right is real: 15 U.S.C. § 1114(2)(D)(v) creates a federal claim for a registrant whose domain was transferred under a policy like the UDRP to establish that its registration or use is not unlawful. Courts decide those cases de novo and give the panel decision no deference — Dluhos v. Strasberg, 321 F.3d 365 (3d Cir. 2003) (the Federal Arbitration Act does not apply); Storey v. Cello Holdings, L.L.C., 347 F.3d 370 (2d Cir. 2003); Sallen v. Corinthians Licenciamentos LTDA, 273 F.3d 14 (1st Cir. 2001). And a reviewing court applies U.S. law, not the law of the complainant's home jurisdiction, as the Fourth Circuit held in Barcelona.com, Inc. v. Excelentisimo Ayuntamiento de Barcelona, 330 F.3d 617 (4th Cir. 2003). Assume nothing is final until the ten days run.

Open a receiving account at the respondent's registrar during the response window, because most transfers push the name into an account at the same registrar and a missing account leaves the domain in limbo with dead nameservers. Then set auto-renew, add registry lock on anything with traffic, and redirect the name to the canonical site.

Common mistakes

Contacting the respondent before capturing the evidence. The parking page vanishes and Policy ¶ 4(b)(iv) goes with it.
Filing against a domain registered before your rights existed. Element Three is conjunctive; this loses, and it draws RDNH findings.
Naming a price. An unsolicited demand from the respondent is close to dispositive under ¶ 4(b)(i). An offer you solicited is worth nothing. Let them go first.
Importing federal likelihood-of-confusion analysis into Element One. Wrong test, wrong forum, and it reads as inexperience.
Asserting unregistered rights without a declaration. Standing fails on the papers.
Choosing the respondent's foreign address as the mutual jurisdiction. You have volunteered to be sued abroad for no benefit.
Missing the five-day cure. Not extendable, and it lands during the amendment scramble.
Asking for cancellation instead of transfer and watching the same person re-register the name.
Filing a bare complaint. Annexes, indexed, cited inline, with dates on every capture.
Winning the domain and losing the program. One recovery closes a file. Register the defensive variants, record the mark in the Trademark Clearinghouse, and run a domain watch — the full program is in the Online Brand Protection Toolkit, with the pre-launch version in the Website and App Launch IP Toolkit.