FAQ: defend a .com domain registered before the complainant's tradema…

FAQ: defend a .com domain registered before the complainant's tradema. UDRP and ccTLD domain recovery and defense across .com. Email the firm to assess your ca…

A UDRP complaint arrives. The complainant holds a trademark. But you registered the .com years before that trademark ever existed. Does the case end there? Not automatically — but pre-registration timing is one of the strongest defenses available under the Policy.

Under the UDRP, a respondent can defeat a .com complaint by demonstrating that the domain was registered before the complainant acquired trademark rights, because bad faith requires that the registrant knew — or could have known — of those rights at the moment of registration. If no mark existed at that point, the "registered and used in bad faith" element of Paragraph 4(a)(iii) typically cannot be satisfied. The 20-day response window after commencement is the critical deadline. Missing it leaves the record bare and the domain at risk.

The questions below address the specific defenses, the evidence that builds them, the forum mechanics for .com disputes, and the realistic path to an RDNH finding.

When Can I Defend a .com Domain Registered Before the Complainant's Trademark?

Pre-trademark registration is a near-complete defense when the timeline is clear and documented. The UDRP requires the complainant to prove that the domain was both registered and used in bad faith — the two limbs are cumulative, not alternative. If bad faith could not have existed at the moment of registration because no mark existed, panels have consistently held that the complaint must fail on the third element.

The timeline comparison is straightforward in principle. Pull the domain's original creation date from historical WHOIS or RDDS records. Compare it against the date the complainant first acquired trademark rights — whether through registration or, where common-law rights are claimed, through demonstrable first use in commerce. If your creation date predates both, the registration-in-bad-faith limb collapses.

Why does this matter so much? Because bad faith is a state of mind at the moment of registration. A registrant cannot have targeted a mark that did not exist. Panels recognize this logic, and the consensus view under the Policy is that retroactive bad faith — "he should have known this brand would eventually emerge" — is rarely sufficient except in the most unusual circumstances, such as where a complainant can prove the registrant was actually aware of a forthcoming brand launch.

The defense is strongest when: the domain is a dictionary word, a geographic term, or a generic phrase; the registrant has a documented use of the domain predating the complainant's mark; and there is no evidence that the registrant monitored trademark filings or had a commercial relationship with the complainant. It is weaker when the complainant can point to evidence — industry publications, prior negotiations, or linked registrations — suggesting the registrant knew the brand was coming.

What Are the Paragraph 4(c) Safe Harbors and How Do You Build the Record?

Even where bad faith at registration is contested, Paragraph 4(c) of the UDRP provides three affirmative safe harbors that independently demonstrate a legitimate interest: 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 without intent to mislead for commercial gain.

Building this record requires contemporaneous, verifiable documentation. Screenshots, invoices, business-registration records, correspondence, and archived web pages showing active use before the complaint was filed are the core evidentiary materials. A Wayback Machine capture showing the domain resolving to a genuine business site as of a date before the trademark was filed is a powerful piece of evidence — panels treat it seriously.

In our practice, we regularly advise registrants to gather this documentation before the response deadline rather than after. The response is a one-shot opportunity. Supplemental submissions are rarely accepted without leave, and panels will generally decide on the record as filed. Scrambling for evidence during the 20-day window while also drafting arguments is a pressure no respondent needs.

What does "bona fide" mean in practice? Panels look for use that is genuine and commercially oriented — not a domain parked on a pay-per-click page after the complainant's mark became known, and not a thin website created only after receiving the complaint. Consistent use over time, with evidence of investment, is far more persuasive than a site spun up to counter a filing.

When Is a Reverse Domain Name Hijacking Finding Realistic?

An RDNH finding is available when a panel concludes that a complaint was brought in bad faith — specifically to deprive a legitimate registrant of a domain the complainant knew, or should have known, it could not win. The finding carries no financial penalty, but it is a reputational mark against the complainant and their counsel.

RDNH is most realistic where the complainant had clear knowledge of the respondent's pre-trademark registration and filed anyway. Panels have found RDNH where a complainant omitted the domain's creation date from the complaint, where the timeline clearly showed registration before the mark, or where the complaint was used as a tool to extract a discounted transfer rather than to vindicate genuine rights. We have defended matters — including a .com dispute in early 2025 — where the RDNH finding was the primary strategic objective from the outset, because the domain had been legitimately held for over a decade before the complainant's brand emerged.

Not every strong defense earns an RDNH finding. Panels are reluctant to make the finding unless the complainant's conduct was objectively unjustifiable. A complaint that loses on a close call does not automatically generate RDNH; a complaint filed with deliberate disregard of obvious prior registration often does. Documenting the timeline in the response — and calling the conduct what it is — gives the panel the basis to act.

Does WIPO or a Court Decide a .com Dispute?

For .com domains, the dispute is almost always decided by an arbitral panel under the UDRP, not by a court. The UDRP is mandatory for all ICANN-accredited registrars covering .com, .net, .org, and other gTLDs, which means the complainant can file a UDRP complaint regardless of whether you consent. The available forums are WIPO, the Forum, the Czech Arbitration Court (CAC), and the ADNDRC. WIPO and the Forum together administer roughly 97% of all UDRP proceedings.

A court action is a parallel option — not a replacement. Either party may take the dispute to a court of competent jurisdiction at any time before or after a UDRP decision. In the US, anticybersquatting litigation is available under the relevant federal statute. If a complainant loses at the UDRP and believes the panel erred, a court is the route for de novo review. Equally, a registrant who receives a transfer order and believes it was wrong can seek a court injunction to block implementation. Courts are not bound by UDRP decisions.

The practical distinction: UDRP proceedings are faster (typically about two months to a decision) and far less expensive than litigation. The only UDRP remedies are transfer or cancellation — no monetary damages. Court actions allow damages but take far longer and cost substantially more. For most .com respondents facing a clear pre-trademark defense, the UDRP response is the right first move, with court action reserved for contested cases where damages or injunctive relief matter.

What Happens If the Registrant Does Not Respond?

A default does not mean automatic transfer. Panels are required to review the complaint on its merits regardless of whether a response is filed. If the complaint fails to establish all three elements, a panel may still deny the transfer. But in practice, a default leaves the record entirely one-sided — the complainant's version of events, evidence, and timeline go unchallenged.

The pre-trademark defense depends on a documented timeline. If that timeline appears nowhere in the record because the registrant defaulted, the panel has nothing to weigh it against. Panels do sometimes note registration dates from WHOIS data in the complaint itself, and they may draw an inference adverse to the complainant where the dates clearly precede the trademark. But that is a fragile position compared to a well-argued response that lays the timeline out explicitly and attaches corroborating exhibits.

In our practice, we treat a default as the worst outcome short of a transfer order. The 20-day window to respond after commencement is tight. We advise registrants who receive a complaint to make contact immediately — before that window closes. Even in straightforward cases, the drafting, evidence assembly, and strategic decisions about RDNH take time that vanishes quickly.

What Evidence Decides the Outcome of a Pre-Trademark Defense?

The outcome turns on three documentary questions: when was the domain registered, when did the complainant's trademark rights arise, and what did the registrant use the domain for after registration. The first two establish the core timeline; the third addresses whether continued use has been legitimate.

Evidence that consistently carries weight includes: the original domain creation date from historical RDDS or WHOIS records; evidence of the complainant's earliest trademark filing and first-use date; screenshots and archived versions of the domain showing its use over time; business-registration documents or commercial records connecting the registrant to the domain's stated purpose; and any correspondence between the parties that predates the complaint.

Evidence that undermines the defense: PPC parking pages featuring competitor or trademark-adjacent advertising; acquisition of the domain after the complainant's brand became publicly known even if the mark was not yet registered; prior offers to sell the domain to the complainant or others at a premium; and a pattern of registering names that track third-party brand development. The pre-trademark timeline is strong — but panels look at the complete picture, and conduct after registration can revive a bad-faith inference that the creation date alone would otherwise eliminate.

We have built respondent records in cases where the only surviving evidence was an archived website from over a decade prior. Documentation strategy is, by a significant margin, the most important practical step a registrant can take after receiving a complaint.

What Is the Deadline Once a UDRP Case Starts?

The respondent has 20 days to file a response after the case commences — the date the provider formally notifies the registrant and begins the proceeding. That deadline is fixed by the UDRP Rules and is not extended automatically for holidays, time zones, or communication gaps. Extensions require a formal request to the provider, which may or may not be granted.

Missing the deadline does not void the case. The panel is appointed on schedule and decides on the available record. Without a response, that record contains only the complainant's materials. The pre-trademark defense, the Paragraph 4(c) safe harbors, the RDNH argument — all of it disappears.

What should happen within those 20 days? First, confirm the commencement date and provider with the case number. Second, obtain and review the complaint in full. Third, identify and gather the timeline evidence. Fourth, assess whether the case warrants a three-member panel request — which the respondent may make, splitting the higher panel fee with the complainant. A three-member panel offers more deliberation and is sometimes strategically appropriate where the legal question is close or the RDNH argument is central. Fifth, draft and file the response with all exhibits.

Twenty days is enough time for a focused, well-documented response. It is not enough time for procrastination. If you have received a UDRP complaint for a .com you registered before the complainant's trademark, the clock is running.

Related at COGNOMEN

• UDRP respondent defense and RDNH findings – full service overview
• FAQ: defending a generic domain name under Dutch and EU procedures
• Analysis: UDRP versus national UK proceedings – choosing the right route