Summary. The working documents of a domain practice, annotated.
Template 1 — Evidence log
Owner: the associate running the investigation. Built before any contact.
| Field | Entry |
|---|---|
| Disputed domain | |
| Registrar of record and location | |
| Registration date (original) | |
| Transfer dates and prior registrants (historical WHOIS) | |
| Current registrant (or privacy service) | |
| Expiration date | |
| Nameservers | |
| Our mark, registration number, registration date, first use | |
| Archived captures obtained (dates, saved locally) | |
| Current site screenshots (date, URL visible) | |
| Site content: payment endpoints, analytics IDs, chat widgets | |
| Reverse-WHOIS results: other names by same email / org / NS | |
| Of those, names matching third-party brands | |
| Prior UDRP decisions against registrant or email | |
| Offer to sell: date, price, medium | |
| Actual confusion evidence | |
| Registrant location and asset indications |
Rule: every capture is saved locally with a timestamp. Archived pages become unavailable, and the record you rely on at filing must exist on your own systems.
Template 2 — UDRP complaint skeleton
COMPLAINT UNDER THE UNIFORM DOMAIN NAME DISPUTE RESOLUTION POLICY
I. INTRODUCTION
II. THE PARTIES
A. Complainant (business, marks, reputation)
B. Respondent (as disclosed; note privacy service)
III. THE DOMAIN NAME(S) AND REGISTRAR
List each name, registration date, registrar
IV. JURISDICTIONAL BASIS
Registration agreement incorporates the Policy
V. FACTUAL BACKGROUND
A. Complainant's mark and its use
B. The disputed registration(s)
C. The content of the site(s), with archived captures
D. Communications between the parties, if any
VI. ELEMENT ONE — IDENTICAL OR CONFUSINGLY SIMILAR
A. Complainant's rights in the mark (registrations; common law)
B. Side-by-side comparison
C. Additions do not avoid similarity (descriptive terms,
hyphens, gTLD, typographical variants)
VII. ELEMENT TWO — NO RIGHTS OR LEGITIMATE INTERESTS
A. No authorization from Complainant
B. Respondent not commonly known by the name
C. No bona fide offering of goods or services
D. No legitimate noncommercial or fair use
E. Anticipated defenses addressed
VIII. ELEMENT THREE — REGISTERED AND USED IN BAD FAITH
A. Registration in bad faith
1. Knowledge of the mark (content, targeting, timing)
2. Pattern of registrations (reverse-WHOIS annex)
3. False or concealed contact information
B. Use in bad faith
1. Offer to sell above out-of-pocket cost
2. Diversion for commercial gain
3. Disruption of Complainant's business
4. Passive holding where no good-faith use is conceivable
C. Prior adverse decisions against Respondent
IX. CONSOLIDATION (if multiple names or respondents)
Common control: nameservers, contacts, templates, timing
X. REMEDY REQUESTED — TRANSFER
XI. MUTUAL JURISDICTION
XII. CERTIFICATION
ANNEXES
Two drafting notes. Element two is a negative; the complainant carries only a prima facie burden, so state the four points cleanly and spend the space anticipating the response. Request transfer, not cancellation — a cancelled name becomes available to whoever registers it next, often the same person.
Template 3 — Reverse-WHOIS worksheet
The highest-value hour in most domain investigations.
| Search vector | Query run | Results | Brand matches |
|---|---|---|---|
| Registrant email | |||
| Registrant name | |||
| Registrant organization | |||
| Registrant phone | |||
| Nameserver pair | |||
| Analytics / ad identifier from site source | |||
| Payment endpoint from checkout page | |||
| Site template fingerprint |
Output for the complaint: a table listing every third-party brand-matching name held by the registrant, with registration dates, demonstrating the pattern under UDRP bad faith and ACPA factor eight.
Template 4 — Consolidation memorandum
Attach to a multi-name complaint. Consolidation is the largest cost lever available.
Complainant requests consolidation of the disputed domain names on the ground that they are held by the same registrant or by registrants under common control. The following evidence supports common control:
- Nameservers. All disputed names resolve through [nameservers], which serve no other identified registrant.
- Contact data. The registrar-disclosed records share [email domain / address / telephone].
- Site construction. The sites use an identical template, including [specific shared elements: identical CSS, identical boilerplate text, identical contact form action].
- Shared third-party identifiers. [Analytics ID / chat widget account / payment endpoint] appears on each site.
- Registration timing. The names were registered within [period], sequentially.
- Content. Each site targets a manufacturer in the same industry using the same approach.
Consolidation is procedurally efficient and equitable, and no respondent is prejudiced because the same defenses apply to each name.
Template 5 — Registrar and host abuse report
For active fraud. Faster and cheaper than any proceeding; use it in parallel.
Subject: Abuse report — phishing/impersonation — [domain]
Domain: [ ] Registrar: [ ] Host/IP: [ ]
Nature of abuse: The domain is being used to impersonate [company] and to solicit fraudulent payments from [company]'s customers.
Evidence attached:
- Email sent from [address]@[domain] to a customer, with fraudulent wiring instructions (Exhibit A)
- Screenshots of the site reproducing [company]'s copyrighted product pages and registered logo (Exhibit B)
- [Company]'s trademark registration No. [ ] (Exhibit C)
- Side-by-side comparison of the legitimate and impersonating sites (Exhibit D)
Harm: [Number] customers approached; $[amount] at risk; ongoing.
Requested action: Suspension of resolution pending investigation.
Contact: [name, direct telephone, email] — available for immediate follow-up.
Send simultaneously to the registrar, the hosting provider, the content delivery network if one is in front of the site, and the payment processor identified on the checkout page. Serial reporting wastes the days that matter.
Template 6 — ACPA complaint outline
I. NATURE OF THE ACTION
II. PARTIES
III. JURISDICTION AND VENUE
A. Federal question, 28 U.S.C. 1331 and 1338
B. Personal jurisdiction -OR-
C. In rem under 15 U.S.C. 1125(d)(2), with the diligence
showing (WHOIS notice sent; publication as ordered)
D. Venue under 28 U.S.C. 1391 or registrar location
IV. FACTUAL ALLEGATIONS
A. Plaintiff's marks, registration, and fame/distinctiveness
B. The disputed domain(s), registration dates
C. Defendant's use of the domain(s)
D. Defendant's pattern of registrations
E. Communications and offers to sell
F. Concealment of identity
V. COUNT ONE — CYBERSQUATTING, 15 U.S.C. 1125(d)
Bad faith factors (1)-(9), each addressed
Safe harbor foreclosed
VI. COUNT TWO — TRADEMARK INFRINGEMENT, 15 U.S.C. 1114
VII. COUNT THREE — FALSE DESIGNATION, 15 U.S.C. 1125(a)
VIII. COUNT FOUR — DILUTION, 15 U.S.C. 1125(c) [if famous]
IX. COUNT FIVE — STATE LAW CLAIMS
X. PRAYER FOR RELIEF
Transfer; injunction; statutory damages (election reserved);
actual damages and profits; fees; costs
Note on in rem: the remedy is limited to forfeiture, cancellation, or transfer. No damages, no fees. Exhaust identification before accepting that trade.
Template 7 — Bad faith factor mapping table
Complete before drafting the ACPA complaint. Blank cells are weaknesses.
| Factor | Statutory text (abbreviated) | Our evidence | Weight |
|---|---|---|---|
| 1 | Registrant's own IP rights in the name | ||
| 2 | Name is registrant's legal name or common identifier | ||
| 3 | Prior bona fide use in offering goods or services | ||
| 4 | Bona fide noncommercial or fair use at the site | ||
| 5 | Intent to divert for commercial gain or to tarnish | ||
| 6 | Offer to sell without bona fide use; pattern of such conduct | ||
| 7 | False or misleading contact information | ||
| 8 | Multiple registrations known to be others' marks | ||
| 9 | Distinctiveness or fame of the mark | ||
| Safe harbor | Reasonable grounds to believe use was lawful | How foreclosed: |
Template 8 — Domain purchase agreement
DOMAIN NAME PURCHASE AGREEMENT
1. PARTIES AND EFFECTIVE DATE
2. THE DOMAIN NAME(S)
Exact name(s); current registrar; current registrant of record
3. PURCHASE PRICE AND ESCROW
3.1 Price
3.2 Funds deposited with [escrow agent] within [n] days
3.3 Release upon confirmed transfer
4. TRANSFER MECHANICS
4.1 Seller unlocks the name and provides the authorization code
within [n] business days
4.2 Buyer initiates transfer to [registrar/account]
4.3 Seller approves within [n] business days
4.4 Transfer completion deadline: [date]
4.5 Who bears registrar transfer fees
4.6 Remedy for failure: escrow returned; [liquidated damages]
5. SELLER REPRESENTATIONS
5.1 Sole registrant with authority to transfer
5.2 No liens, security interests, or conflicting grants
5.3 No pending or threatened dispute proceeding
5.4 No prior UDRP, URS, or court decision affecting the name
5.5 Name is not subject to registry lock or dispute hold
6. ASSIGNMENT OF ASSOCIATED RIGHTS
Goodwill, any common law rights, associated social handles and
platform identifiers listed in Schedule A
7. TRANSITION
7.1 DNS and email continuity period
7.2 Redirect obligations
7.3 Seller cooperation with registrar and registry
8. CONFIDENTIALITY AND NON-DISPARAGEMENT
9. NO FURTHER REGISTRATIONS
Seller will not register any domain confusingly similar to
Buyer's marks
10. GOVERNING LAW AND DISPUTE RESOLUTION
Clause 9 is the one people forget. A seller who sells one name and registers three variants the following week has cost the buyer more than the purchase price.
Template 9 — Escrow instructions summary
| Step | Party | Timing |
|---|---|---|
| Open escrow, agree fee split | Both | Day 0 |
| Buyer deposits funds | Buyer | Day 1–3 |
| Escrow confirms funds | Escrow | Day 3 |
| Seller unlocks and provides auth code | Seller | Day 4–6 |
| Buyer initiates transfer at gaining registrar | Buyer | Day 6 |
| Seller approves transfer | Seller | Day 7–9 |
| Registry completes transfer (up to 5 days) | Registry | Day 9–14 |
| Buyer confirms control | Buyer | Day 14 |
| Escrow releases funds | Escrow | Day 15 |
Never release funds before confirming control at the gaining registrar. "Transfer initiated" is not "transfer complete."
Template 10 — Portfolio register
| Field | Notes |
|---|---|
| Domain | |
| Registrar and account | Corporate account, role-based access |
| Registrant of record | Must be the company, not an individual |
| Administrative and technical contact | Monitored role address |
| Registration date / expiration date | Drives renewal alerts |
| Auto-renew enabled | Y/N |
| Registrar lock / registry lock | |
| DNSSEC | |
| Purpose | Primary / redirect / defensive / campaign |
| Associated mark | |
| Live content? | |
| Business owner | |
| Last audited |
Alerts: 90, 60, and 30 days before expiration, routed to the business owner and to legal. Never rely on registrar emails to an individual's mailbox.
Template 11 — Watch service triage rule
ALERT RECEIVED: new registration containing [MARK] or variant
1. Does the name contain the mark plus an industry term, or a
typographical variant of the mark?
NO -> log and monitor
YES -> continue
2. Does it resolve to a commercial page, a parking page with
competitor ads, or a page impersonating us?
NO (dark/no content) -> log; re-check in 30 days
YES -> continue
3. Is there evidence of fraud (impersonation, payment solicitation)?
YES -> registrar/host/processor abuse reports TODAY,
in parallel with step 4
NO -> continue
4. Does the registration predate our rights in the mark?
YES -> route to counsel; do not file
NO -> continue
5. Run reverse-WHOIS. Are there other brand-matching names?
YES -> consolidate and file UDRP
NO -> file UDRP for this name
6. NO CEASE-AND-DESIST LETTER before filing in categories 3 and 5.
Template 12 — Contract flow-down clause
For agency, development, distribution, franchise, and reseller agreements.
Domains and platform identifiers. Any internet domain name, social media account or handle, application store listing, advertising platform account, or other online identifier that incorporates, is confusingly similar to, or was created for use with Company's trademarks or business (collectively, "Identifiers") is and remains the exclusive property of Company, regardless of who registered or created it. Counterparty will register all Identifiers in Company's name where the relevant provider permits, and will hold any Identifier registered in Counterparty's name in trust for Company.
Upon expiration or termination of this Agreement for any reason, Counterparty will promptly transfer all Identifiers and all associated credentials, authorization codes, and administrative access to Company, and will execute any document and take any action necessary to effect the transfer. Counterparty irrevocably appoints Company its attorney-in-fact, coupled with an interest, to execute any such document if Counterparty fails to do so within ten business days of written request.
Counterparty will not, during or after the term, register any Identifier incorporating or confusingly similar to Company's trademarks.
Why the power of attorney matters: registrars will act on a signed transfer authorization far faster than on a court order, and a departed counterparty frequently simply stops responding.
Template 13 — Reverse hijacking response outline
For a registrant answering a complaint that should not have been filed.
I. THE REGISTRATION PREDATES COMPLAINANT'S RIGHTS
Registration date vs. Complainant's own claimed first use
(cite Complainant's registration certificate)
II. RESPONDENT HAS RIGHTS OR LEGITIMATE INTERESTS
A. Prior bona fide use, with dated evidence
B. Commonly known by the name
C. Descriptive/generic use
D. Noncommercial or fair use
III. NO BAD FAITH — REGISTRATION OR USE
A. Independent derivation of the name
B. No knowledge of Complainant at registration
C. Complainant initiated contact
IV. REQUEST FOR A FINDING OF REVERSE DOMAIN NAME HIJACKING
A. Complainant knew or should have known its mark postdates
the registration
B. Complainant misrepresented [ ]
C. Complainant filed after failing to purchase
V. RESERVATION OF COURT REMEDIES
15 U.S.C. 1114(2)(D)(v); ten-business-day window
Related documents
- Domain Name Disputes: Cybersquatting, the ACPA, and the UDRP
- Recovering a Domain Name: A Practical Guide
- Domain Name Dispute Checklist: A Practical Checklist
- Trademark Enforcement and Litigation Toolkit: From Watching to Verdict and Appeal
- Trademark Registration Toolkit: A Roadmap from Brand Idea to Federal Registration and Maintenance
- Border Enforcement Toolkit: Recordations, Seizure Responses, and Gray Market Programs
- Cybersecurity Program Toolkit
