Misguided Domain Complaints and RDNH: Risks for Trademark Owners
Review misguided domain complaints and RDNH risk, including adverse chronology, prior permission and pre-filing scrutiny.
What’s in this article?
Direct answer
Failing to buy a domain does not itself create an entitlement to obtain it through a complaint. RDNH concerns abuse of the UDRP to deprive a holder improperly of a registration. Not every unsuccessful case is RDNH, but concealing known weaknesses is a significant warning sign.
Review the opposing case first
Ask whether the domain predates the trademark, whether the holder has an independent business name and whether an earlier agreement exists. Do not remove unfavourable answers from the case summary. A genuine information gap and concealment of an adverse fact are different matters.
A high asking price after unsuccessful negotiations does not establish every UDRP element. Consider the word's character, acquisition history, targeting and use. Commercial frustration should not determine the legal description of the facts.
Use precise allegations
Replace “they stole our name” with a documented observation and a separately identified assessment. Disclose previous permissions. Do not turn uncertainty into fact. Check every sentence of a reused template for the actual parties, dates and circumstances.
A documented decision not to file can be a positive quality outcome. Measuring staff only by complaint volume encourages weak cases. Include false allegations, correction time and evidence completeness in the review process. Unsupervised automated filing can amplify mistakes.
Fictional example
A new brand seeks to purchase an old domain consisting of a general word. The parties do not agree on price. Treating that refusal as conclusive evidence of abusive registration omits the chronology and prior use. Research those facts and consider lawful alternatives instead of assuming the complaint route is suitable.
Pre-filing checklist
- List known adverse records.
- Explain earlier permission and commercial relationships.
- Connect each categorical statement to evidence.
- Ask an independent reviewer for reasons not to file.
- Record the decision and its approver.
Separate automation from human decisions
A tool can scan similar domains and organise a report. It should not automatically submit allegations before rights, previous permission and the holder's explanation are checked. Keep model uncertainty visible; missing information must not become a finding of infringement.
Internal audits should examine withdrawn, corrected and deliberately unfiled cases as well as successful complaints. Capture what changed the assessment. This encourages better-supported action rather than larger submission volumes. Do not create institutional success stories or claimed wins without actual decisions and supporting records.
Questions
Does every rejected complaint constitute abuse? No. RDNH is a separate assessment.
Is an RDNH finding a damages award? It should not be presented that way; consequences or claims outside the UDRP require separate analysis.
Official sources
Related guides
- Assessing Domain Bad Faith: Registration, Acquisition and Use
- Responding to a Domain Complaint: Preparing the Defence File
- Criticism and Fan-Site Domains: Investigating Legitimate Use
- Preventing Domain Disputes: Corporate Portfolio and Incident Playbook
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.