Step-by-step: defend a generic-word .ai domain

Step-by-step: defend a generic-word .ai domain. UDRP and ccTLD domain recovery and defense across .ai. Email the firm to assess your case. Transparent fees, re…

A brand owner files a UDRP complaint against your .ai domain. The name is a common English word – "vault," "atlas," "nexus" – and you registered it years before any dispute arose. Now you have 20 days to respond or default. The complaint looks aggressive. Is it legitimate, or is this reverse domain name hijacking dressed up in trademark language?

To defend a generic-word .ai domain under the UDRP – which applies to .ai through WIPO's administration of that ccTLD – a registrant must defeat at least one of the three elements in Paragraph 4(a): confusing similarity, absence of legitimate interests, or bad-faith registration and use. Generic and descriptive single-word domains have a strong Paragraph 4(c) safe-harbor record, because panels consistently recognize that common words carry inherent value independent of any one trademark. The response deadline is 20 days from commencement; missing it is the single most damaging procedural error a registrant can make.

This guide walks each step of the defense, flags the trap inside each one, and explains when an RDNH finding is worth pursuing.

Why does the UDRP apply to a .ai domain?

The .ai registry – operated by the government of Anguilla – has designated WIPO as its dispute-resolution provider, meaning the UDRP and its supplemental rules govern most .ai complaints filed today. That is the starting point every registrant must verify, because the procedure, the timeline, and the remedies flow from whichever rules the registry has adopted at the time of filing. For .ai, the UDRP framework applies in all material respects.

What does that mean practically? It means the complaint must satisfy all three elements of Paragraph 4(a), and a respondent defeats the case by negating any single one. The only remedies available are transfer or cancellation – no money, no costs, no injunction. A panel that finds the complaint was brought abusively may also issue an RDNH finding, a reputational sanction with no monetary component but meaningful deterrent effect.

One nuance matters for .ai specifically. Because it functions as a ccTLD, local Anguillian law nominally governs the underlying registry contract. In practice, panels apply the UDRP analysis in essentially the same way as for .com. But if a complainant attempts to invoke local law to supplement the UDRP test, flag that in the response. The UDRP is self-contained; national intellectual property law does not expand the panel's remedial power beyond transfer or cancellation.

Step 1: Read the complaint immediately and calendar the deadline

The response window opens on the day the case commences, not the day you receive the complaint email. WIPO publishes commencement dates in the case file. Your hard deadline is 20 days from that date. Extensions are available only in narrow circumstances and require a prompt request; a panel will not grant an extension because you were unaware of the proceeding.

The trap in Step 1 is treating the deadline as approximate. Many registrants lose on default not because their case was weak, but because they assumed WIPO would notify them again, or that a registrar hold was a separate proceeding. It is not. Read the commencement letter the same day it arrives, add the 20-day deadline to your calendar immediately, and contact counsel within 48 hours if you intend to respond.

What should you look for in the first read? Check the claimed mark – is it registered or unregistered? Check the zone – has the complainant also filed against a parallel .com? Check the remedy sought – transfer or cancellation. And check whether the complainant asked for a single-member or three-member panel, because that affects your option to request the larger panel at shared cost.

For an assessment of your domain dispute – including whether the complaint is meritorious or abusive – contact info@cognomenlaw.com.

Step 2: Map the three UDRP elements against your facts

A defense succeeds by defeating any one element of Paragraph 4(a). In a generic-word case, elements two and three are almost always the primary battleground. Work through each in sequence.

Element one – confusing similarity. Panels apply a low technical bar here; if the domain string matches the trademark character-for-character, similarity is usually conceded. For generic words, the fight is not here. Do not spend response space on similarity unless the mark is stylized, disclaimed, or the word carries a descriptive meaning the trademark registration itself acknowledges.

Element two – absence of legitimate interests. This is where a generic-word registrant typically wins. Paragraph 4(c) of the UDRP lists three safe harbors. The most relevant for a generic domain is demonstrating a bona fide offering of goods or services – or a demonstrable preparation to do so – before receiving notice of the dispute. Panels have also consistently recognized that holding a generic or descriptive word domain for its inherent value, without targeting any specific trademark owner, may constitute a legitimate interest, particularly where the domain has been in active use or development.

Element three – bad faith registration and use. The UDRP's standard is cumulative: bad faith at the time of registration and in current use. A complainant who registered its mark after you registered the domain has a fundamental chronology problem. If the evidence shows you registered a common word domain before the complainant's trademark filing, bad faith at registration is very difficult to establish. The trap here is assuming that a recent trademark registration automatically defeats the bad-faith element. It should, but the response must make that argument explicitly, with dated evidence.

Step 3: Build the legitimate-interest record

The legitimate-interest element is where the response is won or lost for most generic-word .ai cases. Panels weigh documentary evidence, not assertions. The registrant bears the practical burden of producing evidence once the complainant makes a prima facie showing.

What evidence belongs in the record? Start with the registration history: the date of first registration, any prior registrations of the same name in other zones, and the WHOIS/RDDS record at registration. Add evidence of use: screenshots of the website at or around registration, correspondence discussing a development plan, any domain portfolio records showing the name was acquired as part of a generic-term strategy rather than in response to the complainant's brand. If the domain has been used commercially – even as a redirect or a parked page with generic advertising – preserve and submit that use evidence.

One trap registrants consistently fall into: assuming that passive holding of a generic word domain is automatically safe. It can be, but the safer position is showing affirmative preparations to use the name. A development plan, a business registration using the term, or a dated email thread discussing use are all more persuasive than absence of evidence. Panels give generic-word registrants meaningful credit – but not unconditional credit.

In our practice, we regularly advise registrants who have held generic or descriptive names for years and never compiled a usable evidentiary record. Building that record starts on day one of the response period, not the day before the response is due. We document the chain: acquisition date, consideration paid, intended use, any subsequent development, and the absence of any awareness of the complainant's mark at registration.

To weigh UDRP against a court action for your case, email info@cognomenlaw.com.

How do you assess whether an RDNH finding is realistic?

Reverse domain name hijacking is a finding that the complainant brought the case in bad faith to deprive a legitimate registrant of a domain it had every right to hold. It carries no monetary penalty, but it is on the public record and can deter future abusive filings.

When is RDNH realistic? Panels typically find RDNH where the complainant knew – or should have known – that the case could not succeed. The strongest RDNH fact patterns in generic-word cases involve: a trademark registration that post-dates the domain registration; a complainant that is a sophisticated IP owner represented by experienced counsel; a demand letter threatening litigation before filing; and a domain that is plainly a common dictionary word or industry term with obvious independent value.

The trap with RDNH is requesting it reflexively. Panels require explicit, reasoned argument in the response. An RDNH request that is tacked on as a one-paragraph afterthought, without evidentiary support, rarely succeeds and can undermine the tone of the defense overall. We have defended registrants in .ai and parallel .com proceedings where a targeted RDNH argument, developed fully in the response, produced a written finding that the complainant had overreached.

What happens after an RDNH finding? The complainant retains the ability to re-file if it discovers new evidence – but in practice, an RDNH finding on the record reduces that risk substantially. It also signals to the complainant's counsel that the registrant is not a soft target.

Step 4: Address the choice of panel size and forum

When a complaint is filed at WIPO for a .ai domain, the complainant selects the initial panel size. If a single panelist was selected, you may request a three-member panel – but the cost difference is shared. The WIPO filing fee for a single-member panel on one to five domains is USD 1,500; a three-member panel on the same range costs USD 4,000. If you request the three-member panel, you typically pay the difference between those fees – roughly USD 1,250 as your share.

Is a three-member panel worth it? In a close case involving a genuinely generic word where the panel composition could go either way, three members reduce the risk of a single panelist's idiosyncratic reading of "passive holding" or "common-word legitimacy." In a case with overwhelming chronological evidence in your favor – domain registered years before the trademark, clear independent use – a single panelist is usually sufficient. The cost–benefit turns on the strength of your evidence and the complexity of the complainant's trademark portfolio.

The trap here is assuming that more panelists always means a better outcome for the respondent. Three-member panels are not systematically more respondent-friendly. They provide additional scrutiny, which benefits the stronger argument on the facts. If the complainant's case is meritless, a single competent panelist will say so. If the facts are genuinely contested, three perspectives reduce outcome variance.

Step 5: Draft and file the response

The UDRP response is a formal submission to the panel. It is not a letter, an email, or a narrative complaint. Structure matters. The response should: (1) contest each element that is contestable, in order; (2) marshal the documentary evidence into exhibits; (3) present the chronological narrative of registration and use; (4) make any supplemental-filing or three-member-panel request promptly, not at the last moment; and (5) if sought, develop the RDNH argument as a standalone section with its own evidentiary basis.

Length is not a virtue. Panels read hundreds of responses. A concise, evidence-anchored response that addresses each contested element directly is more persuasive than a lengthy narrative that buries the key points. The first paragraph of the response should state the strongest affirmative point: the date the domain was registered relative to the trademark filing date, the generic character of the word, and the use evidence.

A practical note on exhibits: WIPO's electronic filing system has file-size limits. Organize exhibits before the filing date. A PDF of a domain registration history, a compressed archive of website screenshots, and a portfolio summary of related names – all labelled and cross-referenced in the response body – give the panel what it needs to follow your argument without hunting through a large document set.

In a recent matter (a single-word .ai domain in the technology sector, spring 2025), we prepared a response that led with the registration date – registered three years before the complainant's trademark application – and submitted a contemporaneous development record. The panel declined to transfer the domain and noted that bad-faith registration was not established on the evidence. The case closed in approximately eight weeks from commencement.

What happens if you lose at the UDRP level?

A UDRP loss does not end the road. The registrant has a window after the decision – commonly a brief period during which the registrar holds the domain before implementing the transfer order – to seek a court stay in a court of competent jurisdiction. That court route requires engaging local litigation counsel in the relevant jurisdiction. It is substantially more expensive than the UDRP proceeding itself, and success requires building a case under the applicable national trademark and contract law, not just the UDRP framework.

Is it worth pursuing? The answer depends on the domain's value, the strength of the underlying registrant claim, and whether the panel's reasoning contains a clear legal error. Panels are not infallible, and an erroneous UDRP decision is a recognized category. We have worked with registrants where a court route was the right call – typically where the domain had significant commercial value and the panel had misapplied the bad-faith standard. We coordinate that work with local litigation counsel in the relevant jurisdiction.

One myth worth correcting directly: losing a UDRP does not mean you were a cybersquatter or that your registration was improper. Panels can reach incorrect conclusions; the UDRP process is not a full evidentiary hearing. A court reviewing the same facts independently applies its own legal standard and is not bound by the panel's findings.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview, including fee structure and forum selection
• How to respond within the UDRP deadline – FAQ on the response window and extension requests
• Recovering a stolen or hijacked domain – steps when the dispute is account compromise, not a UDRP complaint