Responding to a Domain Complaint: Preparing the Defence File
Respond to a domain complaint by verifying the notice, checking deadlines and organising evidence and submission records.
What’s in this article?
Direct answer
When a domain complaint arrives, verify its authenticity and identify the procedure before doing anything else. Record the deadline, its starting event and the correct response channel. A structured, evidenced response is more useful than ignoring the complaint. Receipt does not establish the allegations or an inevitable loss.
Verify safely
Dispute-themed email can be phishing. Check the case identifier and provider through official channels before opening suspicious material or paying. For a verified notice, enter the deadline in the case calendar and check its time zone and calculation.
Current UDRP rules specify a twenty-day response period from commencement and allow an expressly requested automatic four-calendar-day extension. Do not apply those periods to .tr or other mechanisms without checking their rules and the actual notice.
Build an allegation-response-evidence matrix
Give each substantive allegation a row. Add the answer, supporting annex and unresolved information. Prior business use, contracts, records showing the holder is known by the name and acquisition history may matter. Explain precisely which asserted fact is wrong instead of merely saying the complaint is unfair.
Do not create backdated records. If a new clarification was added after notice, state its date. Disputing the complainant's trademark rights and establishing legitimate domain use are separate arguments.
Fictional scenario
An established business receives a complaint from a later similar brand. It gathers dated business records, archived pages, invoices and registration history, then adds the complainant's rights to the timeline. This illustrates the investigation required, not an automatic defence victory.
Avoid these mistakes
- Changing relevant pages without preserving the previous version.
- Inventing documents or dates.
- Sharing passwords or transfer codes with an unverified contact.
- Missing a deadline while negotiations continue.
- Assuming default automatically establishes every allegation.
Verify submission of the response
Preparing a response is not enough: confirm delivery through the correct channel, in the required form and within the applicable period. Keep submission records and provider acknowledgements in a restricted file. If missing annexes are requested, identify exactly which version was resubmitted.
Assess both security and evidential implications before changing services associated with the domain during the defence. Altering a page without preserving the earlier version can obscure its history. Public communications should not contradict the response. Track later allegations using the same evidence matrix rather than starting disconnected records.
Questions
What if no response is filed? The case may be assessed on the available record; evidential requirements remain important.
Can the parties negotiate? Potential settlement and its effect on the procedural calendar should be coordinated with counsel and the provider.
Official sources
Related guides
- Preparing UDRP Evidence: Building a File Around the Three Elements
- Misguided Domain Complaints and RDNH: Risks for Trademark Owners
- Criticism and Fan-Site Domains: Investigating Legitimate Use
- Settling a Domain Dispute and Planning a Secure Transfer
Brand protection and monitoring
General information only. Rights, authority and current procedure require case-specific assessment. Fictional examples are not B10 client cases or claimed successes.