Case study: use mediation before a .us domain decision

Case study: use mediation before a .us domain decision. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A US-based software company discovered that a third party had registered the .us version of its brand — a domain it had overlooked when building out its ccTLD portfolio. The registrant was not using the domain for any apparent business purpose, but had set it to redirect traffic toward a generic landing page with pay-per-click links in the same software vertical. A settlement demand arrived shortly after: six figures or nothing. The company's trademark registration was strong and predated the disputed registration by several years. The question was not whether to act, but how.

The .us country-code top-level domain is governed by the usDRP — a procedure administered through the National Arbitration Forum that closely tracks the three-element UDRP test but contains one important additional requirement: a nexus to the United States for both the complainant's rights and the registrant's eligibility. Unlike the WIPO UDRP, the usDRP also expressly contemplates a pre-decision negotiation window that parties can use to resolve the dispute short of a panel ruling. That window, used strategically, was the pivot point in this matter.

This case study explains the situation, the strategy chosen, and the outcome — and draws the practical lessons for brand owners and registrants operating in the .us zone.

The Situation: A .us Domain Pointing at a Pay-Per-Click Landing Page

The disputed domain incorporated the company's registered trademark in its entirety, differing only by the .us extension. The pay-per-click landing page — monetized through ad revenue — displayed sponsored links for competing software products. That fact pattern sat squarely within the bad-faith circumstances listed in the usDRP rules: registration apparently to attract users for commercial gain by trading on the mark owner's reputation.

The company's trademark had been registered with the USPTO for more than three years before the domain was created. RDDS records confirmed the registration date. The registrant had no apparent trade use of the name, no business presence under that identifier, and no prior history of using the term legitimately. There was no evident fair-use scenario to navigate.

One complication arose at the outset. The company operated globally but had a clear US subsidiary and its primary trademark registrations were US-based. Nexus was not an issue for the complainant. The registrant, however, appeared to be based outside the United States — a point that, if established at the panel stage, could have affected the registrant's eligibility to hold a .us domain at all, since .us registration requires a Nexus Affidavit attesting to a qualifying US connection. That potential ineligibility gave the company an additional lever beyond the standard usDRP elements.

The Strategy: Engage the Mediation Window Before Filing

Filing a usDRP complaint is not the only move available once a brand owner has assembled its evidence. We advise clients early in the process to consider whether a pre-filing contact — structured carefully and without prejudicing the complaint — can resolve the matter faster and at lower total cost than a full proceeding.

In this matter, we identified three factors that made a negotiated resolution attractive before any panel saw the file. First, the complainant's evidentiary position was strong: the trademark predated the registration, the pay-per-click use was documented, and the registrant had no obvious legitimate-interest defense. Second, the registrant's geographic position raised a real risk that the .us registry would have revoked the domain on nexus grounds independent of any dispute proceeding — a fact the registrant's counsel would know once the nexus issue was raised. Third, the six-figure demand was commercially unrealistic given what a usDRP panel could actually award: the only remedies are transfer or cancellation, with no monetary damages available, and no costs award against either party.

We communicated the company's position in writing, identified the nexus issue, and set a deadline for a response. The approach was firm but not inflammatory. We were explicit that a complaint was ready to file and that the nexus ineligibility argument would be part of it.

To weigh your options before committing to a formal filing in a .us or other ccTLD dispute, email info@cognomenlaw.com for an assessment.

The Outcome: Transfer by Agreement, Without a Panel Decision

Within two weeks of our written contact, the registrant agreed to transfer the domain for a nominal sum — a fraction of the opening demand, and well below the legal fees a contested usDRP proceeding would have generated. The transfer was completed through an escrow arrangement that protected both parties. No complaint was filed. No panel was appointed. The company held the .us domain within roughly a month of our first engagement.

The outcome illustrates a point that brand owners sometimes miss: the usDRP complaint is a floor, not a ceiling, for strategy in a .us dispute. A complainant with strong facts and a registrant whose own eligibility is uncertain often does not need a panel to get the result it wants. The filing-ready complaint, the nexus argument, and a clear deadline did the work.

This result is not universal. A registrant with a credible legitimate-interest defense — a business actually trading under the name, a prior-use record, or a strong fair-use argument — presents a very different picture. In those cases, a pre-filing contact can harden positions rather than resolve them, and a panel proceeding becomes the right path.

What Decides the Outcome in a .us Dispute

The usDRP requires the complainant to prove all three elements adapted from the UDRP: the domain is identical or confusingly similar to a mark in which the complainant has rights; the registrant has no rights or legitimate interests; and the domain was registered or is being used in bad faith. The usDRP's bad-faith element tracks Paragraph 4(b) factors closely, including registration to attract users for commercial gain by confusion — precisely the pay-per-click pattern in this case.

The additional .us-specific requirement is nexus. The registrant must have a qualifying US connection: US citizenship, a US organization, or a regular and lawful US commercial activity. A complainant who has reason to doubt the registrant's nexus eligibility should raise it — both as a usDRP argument and as a direct complaint to the .us registry, which has its own enforcement mechanism separate from any dispute proceeding.

Evidence that consistently decides usDRP outcomes includes: the priority date of the complainant's trademark relative to the domain's creation date; RDDS records confirming registration history; screenshots of the landing page showing monetization or competitive use; and any correspondence showing the registrant was aware of the mark. Evidence of good-faith pre-notice use by the registrant — a real business trading under the name before the dispute arose — is the most reliable safe harbor for a registrant.

The difference between the usDRP and the UDRP is smaller in practice than the separate policy suggests. Panels applying the usDRP regularly cite UDRP consensus reasoning on bad faith and legitimate interests, because the rules are structurally parallel. The chief practical distinctions are the nexus requirement, the forum (the National Arbitration Forum administers the usDRP), and the fact that .us disputes tend to draw from a smaller body of published decisions than .com disputes — which means fact-pattern matching requires more care.

For a read on whether the three usDRP elements are met in your situation, or to plan a pre-filing approach for a .us dispute, reach us at info@cognomenlaw.com.

Related at COGNOMEN

• ccTLD dispute services: governing rules, routes, and procedures across national zones
• How national ccTLD dispute procedures differ from the UDRP: a practitioner's guide
• Domain escrow and transfer services: structured and secure domain transactions