Step-by-step: respond to a UDRP complaint within the deadlin… (.net 2)

Step-by-step: respond to a UDRP complaint within the deadlin… (.net 2). UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your c…

A UDRP complaint lands in your inbox. The domain is a .net you registered legitimately, used for years, and have no intention of surrendering. Now a brand owner — or someone claiming to be one — is demanding transfer. You have a limited window to act.

To respond to a UDRP complaint within the deadline for a .net domain, a registrant must file a written response with the chosen forum — most commonly WIPO — within 20 days of formal case commencement. Missing that deadline does not automatically mean losing, but it removes every procedural tool available to you: the right to present evidence, to invoke the Paragraph 4(c) safe harbors, and to seek a finding of Reverse Domain Name Hijacking. For .net domains, the UDRP applies in full, administered by WIPO, the Forum, CAC, or ADNDRC under the same three-element test.

This guide walks every step of the response process, identifies the trap hidden in each one, and explains what evidence decides whether you keep the domain.

Why .net domains fall under the UDRP — and what that means for you

The .net top-level domain is a gTLD subject to ICANN's Uniform Domain Name Dispute Resolution Policy in exactly the same way as .com or .org. That is not a technicality; it is the entire procedural foundation of what follows.

The UDRP was adopted by ICANN in 1999 and requires all accredited registrars — including those managing .net registrations — to implement its remedies. When a complainant files against your .net, the registrar places a lock on the domain and the chosen arbitral forum takes over. The case is decided by a written record alone, with no hearing and no cross-examination.

The only remedies available under the Policy are transfer and cancellation. No damages. No costs against either party. That means the stakes for a registrant are binary: you keep the domain or you lose it. There is no middle outcome, and no financial penalty for defending vigorously — unless the panel finds the complaint itself was brought in bad faith, a scenario addressed later in this guide.

One practical consequence of the gTLD framework: the same complaint could be filed before WIPO, the Forum, CAC, or ADNDRC. The complainant chooses. WIPO and the Forum together account for approximately 97% of all UDRP proceedings. If you receive a complaint notice, the cover sheet will name the forum. Identify it immediately — the commencement date and the 20-day clock are forum-specific.

Step 1: Confirm the exact commencement date and calculate your deadline

The 20-day response window runs from the date the forum formally commences the case, not from the date the complaint was filed or the date you first saw the email. Those dates can differ by several days.

The trap here is simple and costly. Registrants frequently count from the date they receive a forwarded email notification rather than from the official commencement letter. The forum's commencement notice is a distinct document, usually sent by email, confirming that the complaint is formally accepted and proceeding. Find that document first. Count 20 calendar days from that date. Mark the deadline in two calendars and tell your counsel on the same day.

Extensions are available but not automatic. Under the WIPO Rules, the provider can grant a modest extension in exceptional circumstances on written request. The Forum has its own extension rules. Neither forum grants routine extensions simply because the deadline is inconvenient. We regularly advise registrants who realize on day 18 that they are under-prepared; the answer is not to seek an extension but to file what you have and supplement if permitted — do not miss the deadline waiting for perfection.

One more trap: the complaint may name multiple domains under a single case if the registrant is the same. Check the complaint carefully. If your portfolio is involved, each domain must be addressed in the single response.

Step 2: Read the complaint element by element — and identify what is actually being alleged

A UDRP complaint must allege all three elements of Paragraph 4(a) to prevail. Read it that way — not as a narrative, but as three separate legal allegations, each of which you can address, challenge, or neutralize independently.

The three elements are: (1) the domain is identical or confusingly similar to a trademark in which the complainant has rights; (2) you have no rights or legitimate interests in the domain; and (3) the domain was registered and is used in bad faith. The third element is cumulative — both registration in bad faith and use in bad faith must be established. Panels have consistently held that a complainant who can only show present use in bad faith, without evidence that the registration itself was in bad faith at the time, cannot satisfy the third element.

As you read the complaint, build a parallel document with three columns: the allegation, your factual response, and the evidence you have (or need to gather) to support it. That document becomes the skeleton of your response. Many registrants skip this step and write a narrative rebuttal. Panels prefer the element-by-element structure; it matches how the decision will be written.

Also check the trademark relied upon. When was it registered? Is it in the same country as your operations? Does it predate your domain registration? A trademark registered after you registered the .net is a significant vulnerability for the complainant, not for you. Panels have consistently held that a complainant cannot rely on a trademark acquired or registered after the domain in question was taken.

If you are reading a complaint for the first time and need an immediate read on whether the three UDRP elements are met against your registration, reach us at info@cognomenlaw.com.

Step 3: Build your legitimate-interest record using the Paragraph 4(c) safe harbors

The Paragraph 4(c) safe harbors are the primary defensive tools for a respondent in a UDRP proceeding. They shift the evidentiary weight: if you can demonstrate any of the three, the complainant's second-element allegation fails.

The three safe harbors are: (a) before notice of the dispute, you made a bona fide offering of goods or services using the domain; (b) you have been commonly known by the domain name, with or without trademark rights; and (c) you are making a legitimate noncommercial or fair use without intent to mislead consumers or tarnish the mark.

The trap in each one is proof. Safe harbor (a) requires contemporaneous evidence — screenshots, invoices, email correspondence, analytics, or cached pages from before the complaint was filed. Panels are skeptical of evidence assembled after notice. If you have used the domain commercially, pull the oldest available records first: domain registration confirmation, earliest emails from that address, earliest invoices or bank statements referencing the site, and archived web captures from third-party services if your own records are incomplete.

Safe harbor (b) — being commonly known by the name — applies more naturally to individuals or businesses whose operating name or personal name matches the domain. If your company or trading name matches the .net, gather the business registration, years of advertising, press mentions, and any correspondence where third parties address you by that name. Social media handles predating the dispute add credibility.

Safe harbor (c) covers fan sites, criticism sites, and commentary, but only where there is no commercial element and no attempt to mislead. This is the narrowest of the three in practice. Panels have denied the defense where even modest advertising revenue was present, treating that as commercialization incompatible with "noncommercial or fair use."

Whatever safe harbor you invoke, specificity matters more than volume. A short, precise explanation supported by three dated exhibits outperforms a lengthy narrative unsupported by attachments. Organize your evidence chronologically, label each exhibit clearly, and reference each one by exhibit number in the body of your response.

Step 4: Address the bad-faith allegations directly — and consider requesting a three-member panel

Panels can only transfer a .net domain if bad faith is established at both the registration stage and the use stage. Your response should address both points explicitly, not simply deny the allegation.

On registration: state plainly when you registered the domain and why. If the complainant's trademark postdates your registration, say so and attach the evidence — your registration confirmation and the trademark's registration certificate (obtainable from the relevant trademark database). If you were unaware of the complainant's mark at the time of registration, explain the basis for that: what you intended the domain for, what name or concept it represented to you, and whether you have any commercial or geographical connection to the mark owner's field.

On use: describe what the domain resolves to, what it has historically resolved to, and whether you have ever offered to sell it to the complainant or to anyone connected to the complainant's industry at a price exceeding your documented costs. Paragraph 4(b) of the Policy lists specific bad-faith circumstances — including registering primarily to sell to the mark owner and registering to disrupt a competitor. Address each one the complainant invokes. If none applies to your situation, say so and explain why with reference to the facts.

Panel selection: the complainant chooses a single panelist or requests a three-member panel. As the respondent, you may also request a three-member panel. If the complainant requested a single panelist, you can upgrade to three by paying the additional fee — though if you do, the costs are generally split with the complainant. In our practice, three-member panels are worth the additional cost where the complaint is aggressive, the mark is weak, or an RDNH finding is realistically in play. A single panelist carries more variance; a three-member panel produces a more deliberated outcome and, when the panel finds for the respondent, a more authoritative decision that may deter future complaints.

Step 5: Assess whether Reverse Domain Name Hijacking applies to your case

Reverse Domain Name Hijacking — RDNH — is a formal finding by the panel that the complaint was brought in bad faith, primarily to deprive a legitimate registrant of a domain. It carries no monetary sanction, but it is a published reputational finding against the complainant and, in some circumstances, its counsel.

RDNH findings are realistic — not rare — where certain fact patterns converge. Panels have consistently found RDNH where: the complainant's trademark was registered after the domain; the complainant had actual or constructive knowledge of the registrant's prior legitimate use; the complaint advanced demonstrably false assertions about the registration timeline; or the complainant filed primarily as a pressure tactic against a registrant who had publicly refused to sell.

To pursue an RDNH finding, you must request it explicitly in your response. A panel will not make the finding sua sponte in most cases. State clearly that you consider the complaint to have been brought in bad faith, set out the specific grounds, and point to the evidence. Keep the tone measured — an RDNH argument that reads as emotional undermines the legal precision the panel expects.

We have defended registrants in proceedings where the RDNH argument was the strongest part of the defense, and in others where it was secondary to the safe-harbor case. In a recent matter (a .net domain in a technology sector, summer 2025), the complainant relied on a mark registered nearly three years after our client's registration date, with no explanation for the gap. The panel denied transfer and included an RDNH finding in the decision. The .net remained with its registrant.

What evidence actually decides the outcome?

Evidence in a UDRP case is the written record the panel receives. There is no hearing. The panel reads the complaint, the response, any annexes attached to each, and any properly admitted supplemental filings. That is the entire factual universe.

The evidence that most often determines the outcome in a respondent's favor includes: (1) contemporaneous proof of use or preparations to use before the complaint was filed; (2) a domain registration date that predates the complainant's trademark; (3) documented commercial activity using the domain that is unconnected to the complainant's field; and (4) communications showing the complainant made an unsolicited approach to purchase the domain, which undercuts any claim that the registration was made to extract money from the mark owner.

The evidence that most commonly damages a respondent's position includes: screenshots showing the domain resolved to pay-per-click advertising targeting the complainant's industry; correspondence in which the registrant offered to sell the domain to the complainant at a substantial profit; social media posts or emails suggesting awareness of the complainant's brand before registration; and a thin or nonexistent record of legitimate use over a long holding period — what panels call "passive holding" in a bad-faith context.

Does the volume of evidence matter? Not as much as relevance and timing. A panel confronted with fifty exhibits and no organizing logic will struggle. A panel given eight well-labeled, chronologically organized exhibits that directly address each element will reach the right analysis faster. In our practice, the response brief itself does the organizational work; the exhibits simply confirm what the brief asserts.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. Email info@cognomenlaw.com to discuss what a reassessment looks like.

How does WIPO compare to a national court for your .net domain?

The comparison matters because a UDRP proceeding at WIPO is not the only path — and for some registrants, it is not even the right one.

WIPO under the UDRP offers speed (approximately two months for a standard case), lower cost than litigation, and finality on the transfer question. But it offers no monetary relief, no injunction, and no ability to award costs. If you win, you keep the domain. If you lose, the registrar transfers it within a short implementation window.

A national court proceeding — in the United States, under US anticybersquatting legislation, for example — can reach money, can issue injunctions, and can in some circumstances award attorney fees. It is also substantially slower and more expensive. For a registrant who has suffered reputational or commercial harm from an abusive complaint, or who wants a binding judgment rather than an arbitral decision, court may be the better long-term path. In our practice, we work with local litigation counsel in the relevant jurisdiction for any matter requiring court action abroad.

There is a further procedural nuance: a losing party in a UDRP can still file a court action within ten business days of the transfer order to stay the implementation. This is sometimes called a "UDRP stay" — the registrar holds the domain pending the court filing. The window is narrow and the cost of court action is real, but it is a backstop available to a respondent who believes the panel got it wrong and has the evidence to make that case in a higher forum.

For a .net domain specifically, the question of whether WIPO or court action is the better path depends on: the strength of your legitimate-interest evidence, the quality of the complainant's trademark, the commercial value of the domain, and whether you are seeking primarily to keep the domain or also to pursue a remedy against the complainant. The right route depends on your situation — there is no single answer that applies across all .net registrations.

Related at COGNOMEN

• UDRP respondent defense and RDNH — full service overview across all gTLD zones
• Defending fair-use claims in UDRP proceedings — strategy and safe-harbor analysis
• Frequently asked questions: defending a UDRP complaint for an .app domain