Step-by-step: transfer a .us domain after a successful complaint

Step-by-step: transfer a .us domain after a successful complaint. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A trademark owner discovers that a .us domain matching its brand is parked at a pay-per-click landing page, or is redirecting customers to a rival. Recovery looks straightforward — file a complaint, win, and collect the domain. The reality is more layered. The .us ccTLD operates under its own procedure, the usDRP, which runs differently from the UDRP in ways that can trip up even experienced complainants.

To transfer a .us domain after a successful complaint you must satisfy the usDRP's three-element test — confusing similarity to a mark, absence of legitimate interest, and bad-faith registration or use — and then navigate a post-decision implementation sequence that is managed by the NeuStar-operated registry rather than a standard ICANN-accredited registrar pipeline. The governing procedure is published by the .us registry and administered through providers that include the Forum. The process, from filing to transfer, typically takes several weeks, with the respondent given a defined window to reply.

This guide walks each step from pre-filing assessment through to confirmed transfer, flags the trap inside each stage, and explains where the usDRP diverges from the UDRP in ways that change your strategy.

What governs .us disputes, and how does the usDRP differ from the UDRP?

The usDRP — the .us Dispute Resolution Policy — is the mandatory procedure for all .us registrations. It is not the UDRP. The policy was developed separately for the .us namespace and applies exclusively to that zone. Complainants who have handled only .com recoveries will encounter a set of differences that matter in practice.

The three elements of the usDRP closely track the UDRP's Paragraph 4(a) structure: (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 element carries a critical distinction. Where the UDRP requires bad faith in both registration and use on a cumulative basis, the usDRP — like several ccTLD procedures — uses a disjunctive "registered or used" formulation in some respects. In practice this lowers the complainant's burden where registration intent is unclear but bad-faith use is demonstrable.

There is a second major difference: the .us eligibility rule. To hold a .us domain, a registrant must qualify as a US nexus entity — a US citizen, US permanent resident, or an organization with a bona fide US presence. This rule cuts both ways. A foreign complainant seeking transfer must either hold US nexus eligibility itself, or the transfer remedy effectively becomes a deletion. Confirm your eligibility before filing; a successful complaint that results in cancellation rather than transfer is a partial outcome you should anticipate rather than discover.

The remedies available under the usDRP are transfer or cancellation of the domain. No monetary damages, no costs award, and no injunction — precisely as under the UDRP. A reverse domain name hijacking (RDNH) finding is also available to respondents who successfully defend against an abusive complaint.

If you are assessing whether the usDRP route fits your situation — particularly where the .us registration sits alongside a .com or other gTLD dispute — contact info@cognomenlaw.com for a read on which procedure to file first and how to coordinate the two.

Step 1: Assess eligibility and build your rights evidence

Before drafting a single page of a complaint, confirm two threshold facts: that you hold qualifying trademark rights and that you have, or can acquire, US nexus eligibility to receive a transfer. These are not formalities. A complaint filed without settled answers to both questions risks a denial that forecloses re-filing without material new facts.

Rights under the usDRP encompass registered and unregistered marks. Registered US trademark rights, shown by a USPTO registration, offer the clearest foundation. Unregistered common-law rights are cognizable, but the evidentiary burden is higher: you must demonstrate that the mark had acquired distinctiveness and secondary meaning in a defined market before the domain was registered. That date — the registration date of the domain — is the temporal anchor. Rights established after that date will not satisfy the first element unless you can show earlier use.

The trap in this step: brand owners sometimes assume a pending trademark application is sufficient. It is not. An application that has not yet matured to registration provides weak support, and unregistered rights tied to the application filing date carry little weight unless the mark was in continuous commercial use before the domain was created.

Practical checklist for this stage:

• Pull the current RDDS (WHOIS) record for the domain and capture the creation date.
• Verify your earliest provable first use of the mark in commerce predates that creation date.
• Confirm your US nexus eligibility — US citizen, US permanent resident, or entity with a bona fide US presence.
• Identify the domain registrar; locate the applicable dispute-resolution provider listed in the registry's published procedures.
• Preserve screenshots, cached page captures, and metadata for the domain's current and historical use — these form the bad-faith evidence base.

Step 2: Build the bad-faith record — what evidence actually decides the outcome?

Under the usDRP, the bad-faith analysis is the element where most complaints succeed or fail. A finding of confusing similarity is rarely contested where a registered mark is in play; the respondent's claim to legitimate interests is often defeated by the absence of any business use. Bad faith is where the panel does real work.

The usDRP, like the UDRP, lists illustrative bad-faith circumstances. Registering a domain primarily to sell it to the mark owner for a sum exceeding documented out-of-pocket costs is bad faith. Registering to disrupt a competitor is bad faith. Attracting users to a commercial site through likelihood of confusion with the complainant's mark is bad faith. Passive holding — owning a domain that is identical to a well-known mark without any active use — can be bad faith, though the analysis requires that additional circumstances make the passive holding inexplicable on any good-faith basis.

What evidence, concretely, supports each category?

• Sale or ransom demand: Preserve any written correspondence in which the registrant quoted a price. Screencaps, email headers, and chain-of-custody notes all matter.
• PPC or parking revenue: Archive the landing page and any advertising links. Third-party traffic data can be useful but is not required if the page's commercial character is clear from its face.
• Pattern of registrations: If the registrant holds several domains matching third-party marks, document each one. Panels treat a portfolio of mark-matching domains as evidence of a pattern of abusive conduct.
• Timing of registration: A domain registered immediately after a trademark application publishes, a product launch, or a press event is strong circumstantial evidence of opportunistic registration.
• No genuine use: Where the domain has been dormant or redirected, document the absence of any bona fide business activity associated with it.

The trap in this step: complainants sometimes rely on conclusory assertions — "the registrant must have known of our brand" — without tying that assertion to objective evidence. Panels require more. Prior mark registrations, press coverage predating the domain creation, and geographic overlap between the registrant and the complainant's market all help ground the inference.

In our practice we find that the richest bad-faith records are assembled before the complaint is drafted, not patched in afterward. Once the response is filed, new evidence is disfavored; you are largely limited to what you put in the complaint.

Step 3: Select the dispute-resolution provider and file the complaint

The .us registry designates approved providers for the usDRP. The Forum (formerly the National Arbitration Forum) is the primary provider used in practice for .us disputes. Filing is done through the provider's platform, accompanied by the provider's filing fee.

A few procedural points that differ from a standard UDRP filing:

• The complaint must comply with the usDRP's own Rules — not the UDRP Rules or the Forum's UDRP Supplemental Rules. Cross-referencing the wrong rule set is a common drafting error that leads to deficiency notices and delay.
• The complaint is served on the registrant by the provider. If the RDDS record is thin or inaccurate — a common occurrence with abusive registrants — document your reasonable efforts to identify current contact details.
• The complaint should specify the relief sought. If transfer is the goal, say so. If US nexus eligibility is uncertain, this is the moment to address it explicitly rather than leaving it to the panel.

Filing fee: the Forum's applicable fees for usDRP proceedings are published on its platform and should be confirmed at the time of filing. They are materially lower than the WIPO UDRP fees for multi-domain .com filings, reflecting the narrower .us market.

The trap in this step: some brand owners assume they can file a .com UDRP and a .us usDRP simultaneously in a single action. They cannot. The two procedures are separate, governed by different rules and providers. A coordinated parallel strategy is possible, but the filings must be separate and their timing managed deliberately. We regularly advise clients on the sequencing of parallel .com/.us disputes to ensure that a decision in one does not prejudice the record in the other.

If a parallel filing across .com and .us is under consideration, or if the .us registration is part of a broader multi-zone campaign by the same registrant, email info@cognomenlaw.com to plan the sequencing before the first complaint is submitted.

Step 4: Manage the response period and the panel appointment

Once the complaint commences, the respondent has a fixed window to file a response. Under the usDRP Rules, the response period is 20 days from commencement — mirroring the UDRP standard. If no response is filed, the proceeding continues as a default. A default does not automatically mean the complainant wins; the panel still reviews the complaint on its merits. But in practice a well-constructed complaint against a clearly abusive registration will generally prevail on default.

If a response is filed, the panel appointment follows. The usDRP, like the UDRP, allows for a single-member or three-member panel. The default is a single panelist unless a party requests a three-member panel. A three-member panel request by the respondent means the parties generally split the higher fee, so the complainant's cost rises if the respondent makes that election. Plan for that contingency in the budget.

What to do during the response window:

• Monitor the domain for any material change — a sudden transfer of the domain, a change in use, or the registration of a related domain are all events to document and, if necessary, flag to the provider.
• If the respondent files a response that contains factual assertions you need to rebut, the usDRP Rules permit a limited supplemental filing in defined circumstances. Do not file one automatically; panels generally disfavor unsolicited supplements. File only if the response raises a genuinely new argument that could not have been anticipated and that materially changes the evidentiary picture.
• Do not communicate with the respondent during the proceeding without care. Anything said in settlement discussions may find its way into a supplemental filing.

How long does the usDRP process actually take?

From filing to a panel decision, a straightforward single-domain usDRP case typically resolves in a matter of weeks — comparable to a standard single-panel UDRP case, which runs roughly two months end-to-end under the WIPO and Forum procedures. The usDRP timeline is set by the Rules and is not subject to extension by the parties without good cause. Registrar implementation of any transfer order follows the decision and is handled by the .us registry and the registrant's registrar of record.

The trap in this step: do not assume the transfer will be immediate once the decision issues. There is a brief post-decision period during which the losing party may seek court review in a US jurisdiction. Until that window closes, or until it is confirmed that no court action has been commenced, the registry may hold the transfer. In our experience this period is rarely exploited, but it is a legal right of the registrant and should be factored into any timeline communicated to stakeholders.

Step 5: Implement the transfer – the post-decision sequence

A successful usDRP decision ordering transfer does not immediately change the domain's registrant of record. Several steps follow the published decision before you hold the domain.

The implementation sequence, at a high level:

1. Decision published: The provider publishes the panel's decision. The registry and the registrant's registrar are notified.
2. Implementation hold: A brief hold period begins. The registrant retains the right to commence a court proceeding in the US to challenge the decision. If the registrant files a court action and notifies the registry within the hold period, implementation is suspended pending the court outcome.
3. Transfer authorization: If no court challenge is filed within the hold period, the registry implements the transfer. You will need to provide registrar credentials for the gaining registrar — the registrar to which the domain will be transferred — before implementation can complete.
4. Gaining registrar acceptance: Confirm that your chosen gaining registrar is accredited to hold .us domains. Not every ICANN-accredited registrar is also accredited for the .us namespace. Verify this before the decision issues; a delay caused by a registrar eligibility problem after the decision is a preventable complication.
5. Domain live in your account: Once the registrar-to-registrar transfer completes, the domain is in your control. Update nameservers, confirm WHOIS accuracy, and set the domain to auto-renew.

The trap in this step: brand owners sometimes delay identifying the gaining registrar until after the decision. This creates a gap during which the domain is in limbo — technically ordered for transfer but not yet accepted by the gaining party. In a recent matter involving a .us name held by a reseller operating across multiple zones (autumn 2025), a four-day delay in registrar confirmation extended the implementation window and required an additional exchange with the registry. Confirm the gaining registrar at the time of filing, not after the decision arrives.

What if the respondent files a court challenge?

The usDRP, like the UDRP, is not a final adjudication. Either party may seek de novo review before a court of competent jurisdiction in the United States. A respondent who receives an adverse transfer order and files a timely court action can freeze the transfer during the litigation. This is the scenario that converts a fast ccTLD arbitration into a prolonged US court proceeding.

How realistic is this risk? In our experience — and consistent with the broader pattern across UDRP-adjacent procedures — the vast majority of adverse parties do not file court challenges. The cost and time of federal-court anticybersquatting litigation is prohibitive for a respondent whose registration was opportunistic. But it cannot be excluded where the domain has significant commercial value, or where the respondent has a substantial organization behind it.

If a court challenge is filed: work with local litigation counsel in the US jurisdiction where the action is brought. COGNOMEN coordinates the substantive domain-dispute strategy and the cross-zone picture; the in-court phase is handled with US litigation counsel as appropriate. The record assembled in the usDRP proceeding — the complaint, response, and panel decision — is directly relevant in subsequent court proceedings and should be preserved in full.

A second contingency: if the complainant lost at the usDRP level and wishes to challenge the outcome, the same avenue exists. A court action in an appropriate US jurisdiction can seek de novo review. The panel's reasoning carries persuasive weight but does not bind the court.

Cross-zone strategy: coordinating .us with .com and other gTLD disputes

A registrant mounting an opportunistic campaign rarely limits itself to one zone. In our practice we regularly see .us registrations paired with a .com, a .net, or a new-gTLD registration by the same beneficial holder. How do you handle that situation?

The right route depends on the zone and the goal. If the domain is a .com and you want it transferred, the UDRP at WIPO or the Forum is the primary path — the filing fee at WIPO starts at USD 1,500 for a single-member panel covering one to five domains. If the campaign spans .com and .us, you can file the UDRP for the .com and the usDRP for the .us as separate, coordinated proceedings. A single UDRP complaint cannot cover a .us domain, because .us registrations fall outside the UDRP's scope. If the respondent holds a pattern of registrations across a dozen zones, a portfolio strategy — combining UDRP filings where they apply and individual ccTLD procedures where they do not — is more effective than serial one-off filings.

If the registrant is based in the US and the conduct is egregious, US anticybersquatting litigation in a federal court is the only route that reaches monetary damages and can address all zones in a single action. That path is substantially more expensive and slower than the usDRP, but it is the appropriate tool where the registrant is well-funded, the damages are real, and deterrence is part of the goal.

For multi-zone campaigns we assess the full picture first: zones affected, registrant profile, evidence available, budget, and the priority of speed versus completeness. The sequence matters. A usDRP decision that establishes bad faith on the record can strengthen a subsequent UDRP filing. A UDRP default decision in which the registrant did not respond can be introduced as background in the usDRP proceeding's context, though it does not bind the panel.

Related at COGNOMEN

• COGNOMEN ccTLD dispute services — procedures across .uk, .eu, .de, .us, and other national zones
• Transfer remedy for .br domains — the Brazilian ccTLD procedure and how it differs from the usDRP
• Case study: recovering a domain held by a multi-registration group through a coordinated UDRP strategy