How to prove a legitimate interest in your .us domain

How to prove a legitimate interest in your .us domain. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A complaint lands in your inbox. Someone is claiming your .us domain and demanding transfer. You registered it in good faith, you use it for a real purpose, and you have no intention of selling. The question is whether you can prove it – and prove it in a way that holds up under the usDRP, the dispute procedure that governs .us domains.

To prove a legitimate interest in your .us domain, you must satisfy one of the safe-harbor grounds set out in the usDRP – the governing rules for .us ccTLD disputes, which closely track the three UDRP elements of Paragraph 4(a) but apply to the .us zone specifically. A respondent who demonstrates a bona fide use before notice of the dispute, a personal connection to the name, or a legitimate noncommercial or fair use can defeat a transfer order. The respondent has 20 days to file a response once the case commences, so assembling the evidence record quickly is the first priority.

This page sets out the usDRP test, the safe-harbor grounds, how to build the evidence record, when an RDNH finding is realistic, and how COGNOMEN approaches respondent defense in the .us zone.

What is the usDRP and how does it differ from the standard UDRP?

The usDRP – the us Domain Dispute Resolution Policy – is the mandatory dispute procedure for .us registrations, and it applies the same three-limb test as the core UDRP. A complainant must show: (1) the domain is identical or confusingly similar to a mark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered or is being used in bad faith. That third limb is significant: some readings of the usDRP treat bad faith as an alternative – registered or used – rather than the strict cumulative standard of the standard UDRP, where both elements must coexist.

What does that mean in practice? A respondent who registered the domain innocently but later pointed it at content that benefits from a complainant's mark faces a harder argument than a respondent who registered in error and corrected course. The distinction matters enormously when drafting the response.

The .us zone is subject to a "nexus" requirement: registrants must have a genuine connection to the United States. That requirement bears on the respondent record as well. A respondent who can demonstrate US residency, citizenship, or a lawful business presence in the United States adds a layer of credibility that panels in .us proceedings notice. We regularly advise respondents to document that nexus early in the response, not as an afterthought.

What are the usDRP safe harbors for proving a legitimate interest?

The usDRP, mirroring Paragraph 4(c) of the core UDRP, recognizes three principal safe harbors through which a respondent can demonstrate rights or legitimate interests. Each requires a distinct evidence strategy.

First safe harbor: bona fide use before notice of the dispute. If the respondent was using – or demonstrably preparing to use – the domain in connection with a genuine offering of goods or services before receiving any notice of the dispute, that use supports a finding of legitimate interest. The key phrase is "before notice." A registrant who pivots to a commercial use only after a complaint letter arrives will not satisfy this ground. The evidence must show temporal priority: launch dates, invoices, correspondence, website archives, business registrations, or product listings that predate the complainant's first contact.

Second safe harbor: commonly known by the name. A respondent who is commonly known by the domain name – even without a registered trademark – can establish legitimate interest. This ground covers individuals with personal names matching the domain, businesses operating under a trade name, and entities with longstanding reputations under the contested string. Evidence here includes trade name registrations, DBA filings, social media profiles, press coverage, and testimony from customers or associates who identify the registrant by the name.

Third safe harbor: legitimate noncommercial or fair use. Fan sites, commentary, criticism, and other expressive uses that do not mislead users into thinking the registrant is the trademark owner can qualify. This ground is narrow. The use must genuinely be noncommercial or fairly critical; a site that mimics the trademark owner's branding while parking pay-per-click links will not survive scrutiny.

In our practice, the most defensible respondents are those who can point to documented pre-dispute use across more than one of these grounds simultaneously. A single thin ground is more vulnerable to a panel that reads the usDRP narrowly.

To assess which safe-harbor grounds apply to your .us domain and what evidence you need, contact info@cognomenlaw.com.

How do you build a legitimate-interest evidence record that holds up?

Building the record is the core of respondent defense. Panels in usDRP proceedings review documents, not oral testimony. If it is not in the record, it did not happen – and a respondent who waits to be asked for evidence typically loses the argument on that point.

The evidence record should address five areas:

• Registration history and intent. WHOIS history, registrar records, and any contemporaneous communications showing why the domain was registered and what it was intended for.
• Use evidence, timestamped. Website screenshots with dates (the Wayback Machine is a standard reference), hosting invoices, analytics exports, email logs on the domain, and any content published under the domain name.
• Business identity and the nexus. Trade name registrations, DBA filings, business licenses, tax registrations, and any document linking the registrant's identity to the domain string – not just to the business itself.
• Pre-dispute commercial activity. Contracts, invoices, bank records, and customer correspondence that place the use before the complainant's notice letter or the filing date of the complaint.
• Good faith indicia. Communications showing the registrant did not know of the complainant's mark, or showing the registrant took steps to avoid confusion once aware of it.

A strong record does not merely rebut the complaint – it tells a coherent story. Panels notice when a respondent's narrative is consistent across documents produced from different sources. They also notice when documents are conveniently dated or inconsistent. Authenticity matters as much as volume.

In a recent matter – a .us domain used for a regional services business, spring 2025 – we assembled a record spanning three years of invoices, a DBA filing that predated the complainant's US trademark application, and archived website pages from before the dispute was filed. The panel found legitimate interest without reaching the bad-faith limb.

When is an RDNH finding realistic in a .us proceeding?

Reverse Domain Name Hijacking – a finding that the complaint itself was brought in bad faith to deprive a legitimate registrant of their domain – is available in usDRP proceedings, just as it is under the standard UDRP. The finding carries no monetary penalty, but it is a significant reputational sanction on the complainant and their counsel. It also signals to the industry that the complaint was abusive.

Panels are cautious about RDNH. The bar is higher than simply winning on legitimate interest. A respondent seeking an RDNH finding must show something more: that the complainant knew it could not succeed – because the domain was registered before the trademark existed, because the registrant's use was obvious and documented, or because the complainant failed to conduct basic due diligence before filing. Filing a complaint against a domain with a registration date years before the trademark priority date, without addressing that gap, is a common pattern that panels treat as a ground for RDNH.

We have defended registrants in proceedings where the complainant filed on a registration that predated its own mark by over a decade. In those situations, we seek RDNH explicitly and build the argument in parallel with the legitimate-interest defense, because the two records overlap considerably.

What should a respondent not do? Do not make an aggressive RDNH argument on weak facts. A panel that declines an RDNH request because it lacked foundation will note the overreach, and that notation may affect how it weighs other credibility arguments. RDNH is a secondary argument, not a substitute for a well-built legitimate-interest record.

If the complaint against your .us domain was filed after the complainant's trademark, or without apparent prior research, email info@cognomenlaw.com to discuss whether an RDNH argument belongs in your response.

What evidence patterns most often decide the outcome?

Panels deciding .us disputes tend to reach the same fact patterns repeatedly. Understanding which facts carry weight – and which are legally irrelevant – helps a respondent prioritize the record.

Registration date relative to the trademark. This is the single most important structural fact. If the domain was registered before the complainant's trademark rights arose, the registrant cannot logically have targeted the mark. Documenting the registration date precisely, and locating the complainant's earliest trademark application, is the first task in every response we prepare.

Passivity vs. active use. A respondent who holds the domain but does not use it must explain the passivity. Panels have held that passive holding alone does not establish legitimate interest, though it also does not automatically demonstrate bad faith. A respondent with a parked domain faces a harder argument than one actively using it – but the response can address the reason for non-use (a business not yet launched, seasonal operations, or a domain held for a legitimate personal-name reason).

Conduct toward the complainant. Did the registrant ever contact the complainant offering to sell? Demand a payment disproportionate to registration costs? Attempt to attract the complainant's customers? Any of those facts weighs heavily against the respondent. Conversely, a registrant who refused an approach from the complainant and continued the same use throughout is in a better evidentiary position.

Consistency of use. Panels compare the current use of the domain against the asserted legitimate interest. A registrant who claims a personal-name ground but has operated the domain as a commercial parking page undermines the argument. The use and the claimed ground must align.

In a separate .us matter we handled – an investor holding a generic-phrase domain, autumn 2024 – the complainant argued bad faith based on the domain's parking page. We documented that the domain had carried the same generic content since registration, that the registrant's business plan had been delayed by external factors, and that the parking revenue was incidental to registration costs. The panel declined to transfer.

How does the .us respondent process compare to other zones?

The right forum and the right procedural route depend on the zone. A .us dispute is different from a .com or a .uk dispute in ways that affect strategy.

For .com domains, the standard UDRP applies – with the strict cumulative "registered and used in bad faith" standard. A respondent in a .com case who registered before the complainant's mark is in a structurally stronger position than in a .us case, because the disjunctive reading of the usDRP bad-faith limb can allow a complaint to survive on "use" alone even where registration was innocent. Both zones give the respondent 20 days to file a response after commencement. Both are handled through the same accredited providers – WIPO, the Forum, CAC, and ADNDRC.

For .uk domains, the Nominet DRS applies an "abusive registration" test reading "registered or used" abusively, and it also includes a mandatory mediation stage before an expert decision. That mediation opportunity – which does not exist in the usDRP – gives .uk respondents a structured settlement path that .us respondents lack.

For .eu domains, the ADR.eu procedure at the Czech Arbitration Court applies its own rules, and the remedy may be revocation rather than transfer if the complainant lacks EU eligibility.

If a brand dispute spans both a .us and a .com, the proceedings are separate. The complainant may file both simultaneously. We coordinate the respondent strategy across both forums to ensure that the factual record presented in each proceeding is consistent and mutually reinforcing. An inconsistency between a .us response and a .com response filed by the same registrant can be used by a complainant to undermine both.

Where a .us dispute does not resolve through the usDRP – or where the respondent seeks damages, or the registrant's conduct falls outside the usDRP's remedial scope – US anticybersquatting litigation is the alternative route, handled with local litigation counsel in the relevant jurisdiction. That route carries substantially higher cost and a longer timeline, but it reaches remedies the usDRP cannot.

What is the step-by-step process once you receive a .us complaint?

The procedural clock starts the moment the dispute provider formally commences the proceeding. From that point:

1. Verify commencement and confirm the deadline. The respondent has 20 days to file a response. Missing that deadline results in a default proceeding decided on the complainant's record alone. Confirm the exact commencement date with the provider immediately.
2. Preserve evidence. Archive the domain's current and historic content, gather business records, and preserve all communications related to the domain before producing anything to the other side.
3. Analyze the complaint's three limbs. Which elements is the complainant attempting to prove? Is the trademark registration date before or after the domain registration? What bad-faith theory is the complainant advancing? The response strategy follows from the weaknesses in the complaint.
4. Build the safe-harbor record. Match the evidence to the applicable safe harbor – bona fide use, personal name, or noncommercial/fair use – and document each element in a chronological sequence that a panel can follow.
5. Draft and file the response. The response must be filed within the deadline. Late filings are generally not accepted without cause.
6. Assess RDNH. If the facts support it, include the RDNH argument as a secondary section of the response, with its own supporting evidence.
7. Monitor the panel appointment and any supplemental filing requests. Panels occasionally request additional submissions; respond promptly if that occurs.

See our guide on responding within the deadline – applicable across ccTLDs – for a worked account of steps 1 through 4: How to respond within the deadline in a domain dispute.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview across all zones and forums
• Guide to responding within the UDRP and ccTLD response deadline
• Confusingly similar trademark analysis – understanding the complainant's first element