Step-by-step: seek a reverse domain name hijacking finding for a .us domain

A brand owner files a usDRP complaint against a domain you have held for years. The claim is thin – a trademark registered after your domain, a conclusory bad-faith allegation, and no real evidence of intent to profit from their name. You respond. The panel dismisses the complaint. But can you get something more? Can the record show the complaint itself was an abuse?

To seek a reverse domain name hijacking finding for a .us domain, a respondent must show that the complainant brought the usDRP proceeding in bad faith – typically because it knew, or should have known, it could not satisfy all three elements of Paragraph 4(a). The procedure runs under the usDRP, the country-code variant of the UDRP that governs .us domains, and the RDNH finding carries no monetary penalty but creates a public reputational record against the complainant. A case typically concludes within roughly the same compressed window as a standard usDRP proceeding.

This guide walks through each step of pursuing that finding, the trap concealed in each one, and what the evidence must actually show.

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

The usDRP is the dispute-resolution policy that governs .us domains – the United States country-code top-level domain – and it closely tracks the structure of the UDRP while carrying a few meaningful differences. Understanding those differences is step one, because a respondent who argues from pure UDRP instinct can miss the .us-specific nuances that either strengthen or undercut an RDNH bid.

Like the UDRP, the usDRP requires a complainant to prove three elements: confusing similarity to a mark in which it has rights, the respondent's lack of rights or legitimate interests, and registration and use in bad faith. The bad-faith limb is cumulative – registered AND used in bad faith, not merely one or the other. That matters because a complainant who proves only one limb cannot prevail, and a panel that sees a complainant press forward anyway is more receptive to an RDNH argument.

The .us zone also carries an eligibility overlay: .us registrants must qualify under the nexus requirements for the zone, and some panels consider whether the complainant paid attention to that context when framing the complaint. Panels handling .us disputes sit under the same provider structures used for gTLD UDRP cases – including WIPO and the Forum – and they apply the usDRP rules, not the UDRP text directly. Confirm the current procedural rules with the relevant provider before filing any submission.

Trap in this step: assuming that UDRP precedent maps exactly onto usDRP panels. Cite the usDRP text and the applicable usDRP rules, not generic UDRP language, when framing your RDNH argument.

Step 1 – Assess whether an RDNH finding is realistically available

Not every dismissed complaint earns an RDNH finding, and conflating "the complainant lost" with "the complainant hijacked" is the most common mistake respondents make at this stage. An RDNH finding requires showing that the complaint was brought in bad faith or in a reckless disregard of the lack of merit – something more than a weak case that failed on the facts.

Before investing in an RDNH argument, run through this threshold assessment. First, did the complainant have a trademark at the time of the domain's registration? If the trademark postdates the domain, panels have consistently held that a complainant who pursues the complaint anyway – knowing that registration in bad faith is impossible to show for a domain that predates the mark – crosses the line from losing complainant to abusive one. Second, was the complainant represented by counsel? Panels are less forgiving of a legally advised complainant that runs a demonstrably meritless argument than of a pro se brand owner who simply misjudged the law. Third, was the demand before filing disproportionate – a cease-and-desist asserting ownership of a generic or descriptive term, a demand for a sum far above registration costs, or a thinly veiled attempt to use the usDRP as a substitute for trademark litigation?

If at least two of those markers are present, an RDNH argument has a realistic foundation. If the complaint was merely poorly constructed but the complainant held a plausible senior mark and some colorable bad-faith theory, panels will typically simply dismiss without the additional finding.

In our practice, the matters that produce RDNH findings share a common profile: a complainant with a junior or narrowly scoped trademark, a respondent with a documented pre-dispute history with the name, and a complaint that glossed over the registration-date problem entirely rather than engaging with it honestly.

Step 2 – Build the legitimate-interest record before the response deadline

The respondent has 20 days to file a response after the case commences – a deadline set by the rules, not the parties. That window is also the primary opportunity to assemble the legitimate-interest record, which is the evidentiary spine of both your defense and your RDNH bid.

Paragraph 4(c) of the usDRP (mirroring UDRP Paragraph 4(c)) lists three safe harbors: a bona fide offering of goods or services before any notice of the dispute; being commonly known by the domain name; and legitimate noncommercial or fair use. You do not need to satisfy all three – one, well-documented, is enough. But the documentation must be contemporaneous and specific, not reconstructed after the fact.

What does that look like in practice? If you registered the domain for a business that predates the complainant's mark, gather the business registration, the earliest invoices or receipts, any contemporaneous website captures from archive services, and correspondence showing the name was in active commercial use. If the domain corresponds to a personal name or a geographic expression, collect evidence showing that connection predates any knowledge of the complainant's brand. If the domain was registered as a keyword reflecting descriptive terms, document that registration rationale – a contemporaneous note in an email, a purchase record with a stated purpose, or a domain portfolio strategy that explains the acquisition logic.

Trap in this step: treating the legitimate-interest section of the response as secondary to the bad-faith rebuttal. Panels evaluate all three elements. A respondent who rebuts bad faith impressively but leaves legitimate interest thin gives a panel room to dismiss without reaching RDNH at all.

For a deeper look at building this record across dispute types, see our guidance on proving legitimate interest.

If you have received a usDRP complaint and the 20-day clock is running, the structure of your response determines whether RDNH is available at all. For an assessment of the three elements in your case, contact info@cognomenlaw.com.

Step 3 – Frame the RDNH argument in the response itself

An RDNH finding is available to a panel even without a formal cross-request in many usDRP proceedings, but panels are significantly more likely to make the finding when the respondent explicitly raises it and supports it with argument. The response – not a separate filing, not a supplemental submission – is the proper place to build that argument.

Structure the RDNH section around three points. The first is the complainant's knowledge of the fatal defect: show that the trademark registration date, public WHOIS (RDDS) data, and any pre-complaint correspondence demonstrate that the complainant knew or should have known the registration-before-the-mark timeline made element three impossible to satisfy. The second is the nature of the conduct: was the complaint filed shortly after a failed purchase negotiation? Was it accompanied by a demand that referenced the complainant's litigation resources? Was the bad-faith allegation conclusory and unsupported? Each of those markers has weight. The third is the effect on the respondent: a panel that understands the respondent faced costs, reputational disruption, and the potential loss of a legitimately held domain is more likely to treat the finding as warranted.

One procedural note: do not save the RDNH argument for a supplemental filing. Panels routinely decline to admit supplemental submissions under usDRP rules unless the other side has raised a new argument. Build it into the response in full.

How does the evidence decide the outcome in a .us RDNH proceeding?

The panel weighs the totality of the record, but certain categories of evidence consistently carry more weight than others. Understanding those categories lets a respondent allocate effort correctly – and avoid over-investing in arguments that panels treat as peripheral.

The highest-value evidence in a .us RDNH proceeding is the chronological gap between domain registration and trademark filing. If your .us domain predates the complainant's first trademark application by a meaningful margin, that single fact does most of the work. Panels have consistently held that a complainant cannot credibly allege registration in bad faith with respect to a mark that did not exist when the domain was created. Document this gap with the domain's registration record (from the RDDS/WHOIS data at the time of filing) and the complainant's trademark application and registration dates from the public registry.

The second category is the complainant's pre-complaint communications. A demand letter that overreaches – claiming ownership of a generic word, citing irrelevant marks, or threatening litigation in an atypical way – is probative of bad faith in bringing the complaint. Preserve every email, every letter, and every record of any purchase offer the complainant made before filing.

In a recent matter involving a .us domain held since the early years of the zone (autumn 2025), we built an RDNH argument around three elements: a domain registered more than a decade before the complainant's trademark application, a purchase offer made by the complainant's agent that the respondent declined, and a complaint that asserted bad faith without citing a single item of evidence connecting the respondent's conduct to the complainant's brand. The panel dismissed the complaint and made the RDNH finding.

The third category is the complainant's represented status and the quality of the legal argument. A sophisticated complainant with counsel who still filed a complaint containing no evidence of bad faith is held to a higher standard than a brand owner who self-filed a weak claim. Where counsel signed the complaint, the panel's tolerance for legal error is lower – and the RDNH threshold is correspondingly easier to reach.

If a prior usDRP response failed to raise RDNH or the record on legitimate interest was underdeveloped, a targeted review can identify what was missed. Email info@cognomenlaw.com to discuss the record.

Step 4 – Navigate the forum and procedural mechanics for .us

The .us registry (operated by Donuts/Identity Digital as the back-end registry) designates specific dispute-resolution providers for the usDRP. WIPO and the Forum are the principal providers, and both administer usDRP proceedings under the usDRP policy and rules texts rather than the standard UDRP rules – verify with the provider which procedural supplement currently governs before the response is filed.

The respondent does not choose the forum; the complainant selected it when filing. What the respondent can influence is the panel composition. Where the usDRP rules permit a request for a three-member panel, consider whether that is tactically appropriate. A strong RDNH argument may benefit from a three-member panel that carries greater weight in the domain-disputes community, but the costs of the higher panel tier – which the parties generally split when the respondent requests the upgrade – must be weighed against that benefit.

Filing the response on time is non-negotiable. A default (no response filed) almost always ends the RDNH possibility entirely, because the panel has nothing on which to base the finding. If the 20-day window is running and the record is still incomplete, file a timely skeletal response preserving your right to respond and immediately seek a procedural extension if the rules of the applicable provider permit one. Extensions are not guaranteed and are granted sparingly.

Cross-zone consideration: if the complainant also holds or pursues a complaint about a corresponding .com, the usDRP and the UDRP are separate proceedings on separate timelines. An RDNH finding in the .us proceeding does not automatically produce one in the .com proceeding, and vice versa. We regularly advise respondents who face parallel attacks across zones to manage the two records independently while maintaining consistency in the core legitimate-interest narrative.

Step 5 – What happens after the panel issues its decision?

Once the panel issues its decision, the .us registry (through its designated registrar lockout mechanism) implements the outcome within the period specified in the applicable usDRP rules. If the complaint is dismissed – with or without an RDNH finding – the domain remains with the respondent and the registrar lock imposed at the start of the proceeding is lifted.

If the panel makes an RDNH finding, that finding appears in the published decision. Published decisions under the usDRP are publicly accessible through the provider's database. The finding is reputational: it names the complainant and the relevant conduct, creating a record that future panels may consider in any subsequent complaint filed by the same complainant. There is no monetary award. There is no cost order against the complainant. Those limitations are inherent to the usDRP – if you need monetary relief, the applicable path is US anticybersquatting litigation, handled with local litigation counsel.

A second important point: the usDRP decision is not a final court judgment. A complainant who is dissatisfied with a dismissal (or with an RDNH finding) retains the right to seek relief in the courts. The mutual jurisdiction submission that accompanied the original complaint designates the courts in which such a challenge may proceed. We have seen complainants who received RDNH findings subsequently threaten court action; in our practice, those threats rarely materialize, but the respondent should know the risk and maintain the legitimacy evidence that supported the response.

Comparing the .us RDNH route with analogous procedures in other zones

The route to an RDNH finding differs materially depending on the zone. Under the standard UDRP for .com and other gTLDs, the analysis is the same in structure – the complainant must have known it could not satisfy the elements – but the volume of UDRP panel decisions creates a denser body of RDNH precedent that respondents and panels can draw on. The usDRP has a smaller decision corpus, which means the threshold criteria are applied with less granular panel-to-panel variation, but also that favorable RDNH findings are less routinely discussed in published commentary.

The Nominet DRS for .uk domains explicitly recognizes RDNH under its own terminology (abuse of the procedure), but the test and the procedural mechanics differ meaningfully from the usDRP. The .uk procedure includes a mandatory free mediation stage that the usDRP does not, and the Nominet DRS applies an "abusive registration" test reading "registered OR used" abusively – a lower bar for the complainant than the usDRP's cumulative "registered AND used." For respondents holding both a .us and a .uk domain, those differences matter when constructing parallel defenses.

For .es domains, the applicable ccTLD procedure follows Spanish registry rules and has its own distinct RDNH-equivalent analysis. Our guidance on the RDNH finding for .es domains covers that procedure in detail.

Where the complainant holds trademark rights in multiple jurisdictions and files simultaneously across gTLD and ccTLD zones, the respondent needs a coordinated strategy. An RDNH finding in the .us case carries no direct weight in the .com case – each panel decides on its own record – but a well-documented legitimate-interest narrative, built once and deployed consistently across all proceedings, strengthens each individual response.

For a full account of the respondent defense and RDNH service across zones and forums, see our respondent defense practice overview.

Common traps that undermine an RDNH bid – and how to avoid them

The RDNH argument fails most often not because the underlying complaint was in good faith, but because the respondent's record is insufficient to support the finding. These are the traps we see most frequently.

The first is the reconstructed-legitimacy problem. A respondent who cannot produce contemporaneous evidence of legitimate use – and instead offers testimony about what they intended to do with the domain years ago – gives the panel no basis to confirm the claim. The solution is simple in principle but requires discipline: the moment a complaint arrives, stop and identify every contemporaneous document that speaks to how and why the domain was registered and used. Do not allow the record to be built solely from memory.

The second is the overstatement trap. Respondents who argue that every weak complaint is RDNH erode the argument when the panel sees it deployed against a complaint that was merely unsuccessful. Reserve the RDNH argument for cases where the chronological gap, the complainant's conduct, or the quality of the legal argument genuinely support it. A panel that sees an RDNH argument in a marginal case is less likely to make the finding even in a strong one.

The third is the supplemental filing mistake. A respondent who saves their strongest RDNH argument for a supplemental submission that the panel declines to admit loses the argument entirely. Everything material goes in the response.

In a separate matter (a .us domain in the professional-services sector, spring 2025), a respondent came to us after an initial response had been filed without an RDNH argument. The complaint was dismissed on the merits – the complainant had not proven bad faith – but no RDNH finding was made because the record did not support it. The respondent held a domain that predated the trademark by several years and had turned down a five-figure buy-back offer before the complaint was filed. Had the response included a structured RDNH section with that evidence, the finding would have been available. We advised the respondent on documenting the record for any future complaint by the same party.

The audience myth worth confronting directly: some registrants believe that winning the usDRP case is enough – that the RDNH finding is a bonus for aggressive lawyers, not a meaningful strategic goal. That understates its value. An RDNH finding on a publicly accessible record signals to future complainants and their counsel that this respondent is willing and able to pursue the additional remedy. It deters repeat filings. In our practice, we have seen RDNH findings effectively close off a channel of harassment that a complainant had planned to continue.

Related at COGNOMEN

• Respondent defense and RDNH across gTLD and ccTLD zones – service overview
• How to seek a reverse domain name hijacking finding for a .es domain
• Proving legitimate interest in a domain dispute – evidence and strategy

Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.