FAQ: seek a reverse domain name hijacking finding for a .ai domain

What does it mean to seek a reverse domain name hijacking finding for a .ai domain?

An RDNH finding means a WIPO panel formally records — in the published decision — that the complainant used the UDRP process in bad faith to attack a legitimate domain registration. For a .ai domain, the procedure runs through WIPO under rules that closely track the standard UDRP, so the RDNH doctrine applies in the same way it applies to a .com or .net dispute. The finding carries no monetary penalty, no costs award, and no injunction. Its force is reputational: the decision is publicly accessible, and a declared RDNH finding puts the complainant's IP-enforcement conduct on the record.

Panels do not make RDNH findings lightly. The consensus position is that a complaint falls short of the threshold even if it fails all three UDRP elements; the respondent must show something more — that the complainant knew its case was deficient but filed anyway, or that it used the complaint strategically to pressure a legitimate registrant into surrendering the domain.

When is an RDNH finding realistic in a .ai dispute?

An RDNH finding becomes realistic when the record reveals a clear mismatch between the complainant's claim and the facts available to it at the time of filing. The most common patterns panels cite include: a trademark that post-dates the domain registration by a meaningful margin; a complaint that ignores documented evidence of the respondent's legitimate interest (such as a business use or an established personal name); or a filing that misstates or omits key facts about the domain's history.

In our practice, we see RDNH requests succeed most often where the respondent can show (a) the domain was registered before the complainant's trademark rights accrued, making bad-faith registration chronologically impossible, and (b) the complainant had access to that registration-date information in the public RDDS record before it filed. A complainant that proceeds despite an obvious chronological bar is the clearest candidate for an RDNH finding. Panels have also found RDNH where the complainant held only a very weak or descriptive mark and the domain was a generic or descriptive term in common use.

What evidence is needed to seek a reverse domain name hijacking finding for a .ai domain?

The evidence that supports an RDNH request falls into two distinct layers. The first layer establishes that the respondent had legitimate interests and registered in good faith — this wins the underlying case. The second layer establishes that the complainant's failure was foreseeable and that filing was therefore an abuse of the process.

For the first layer, useful evidence includes: registration invoices or screenshots showing the date the .ai domain was acquired; contemporaneous business records (incorporation documents, product launch materials, correspondence) demonstrating use of the name before any notice of the dispute; proof that the registrant is commonly known by the domain name; and records of any bona fide offering of goods or services under the name. These speak directly to the Paragraph 4(c) safe harbors that demonstrate a legitimate interest.

For the second layer — the abuse element — the strongest evidence is external and objective. RDDS or WHOIS records showing the registration date preceded the complainant's trademark filing are particularly powerful, because they are publicly available and the complainant had no excuse for overlooking them. Evidence that the complainant sent a pre-complaint demand at a very high purchase price — suggesting the real goal was acquisition rather than infringement enforcement — can also support an RDNH conclusion. We assemble both layers in parallel, because a panel that grants the underlying defense may decline RDNH if the abuse element is not separately and clearly argued.

For a detailed treatment of how to build the legitimate-interest record at the first layer, see our guide at Proving Legitimate Interest in a Cloud-Era Domain Dispute.

How long does it take to seek a reverse domain name hijacking finding for a .ai domain?

The RDNH request travels inside the same UDRP proceeding as the defense; it does not require a separate filing or a second case. The total timeline for a standard single-member panel case is roughly two months from the date the case commences — the respondent has 20 days to file its response, the panel is then appointed, and a decision typically follows within two to three weeks of appointment. A three-member panel adds some weeks to that schedule.

There is no additional waiting period specific to RDNH. The panel decides the complaint and, where the respondent has requested it, considers the RDNH question in the same decision. If the case settles before a panel issues a decision — which occasionally happens when a complainant withdraws after seeing a strong defense — no RDNH finding will be made. A finding is only possible in a final decision on the merits.

What does it cost to seek a reverse domain name hijacking finding for a .ai domain at WIPO?

The respondent pays no WIPO filing fee in a standard single-member panel case; the complainant bears the full USD 1,500 WIPO filing fee for one to five domains on a single-member basis. If the respondent requests a three-member panel, the parties typically split the higher three-member fee — USD 4,000 at WIPO — meaning the respondent's share would be approximately USD 1,250, depending on the complainant's original panel selection.

Legal fees for preparing a respondent defense and an RDNH request are separate from forum fees. In the market, a straightforward single-domain defense typically falls in the USD 3,000–7,000 range, depending on the complexity of the legitimate-interest record and the strength of the abuse argument. At COGNOMEN we publish service descriptions with transparent fee ranges; email info@cognomenlaw.com for a specific assessment of your .ai dispute.

For a read on whether the three UDRP elements are met and whether an RDNH request is warranted in your case, reach us at info@cognomenlaw.com.

Can I seek a reverse domain name hijacking finding for a .ai domain for more than one domain at once?

A single UDRP complaint may cover multiple domains, but only if all of the domains are registered by the same holder. Where a complainant bundles several .ai domains — or a mix of .ai and other zones — into one complaint, the respondent's defense and any RDNH request covers all of them in the same proceeding. The RDNH finding, if granted, will address the complaint as a whole rather than domain by domain.

If a complainant files separate complaints against different domains held by the same registrant, those are separate cases with separate timelines and separate RDNH opportunities. There is no mechanism to consolidate independently filed complaints into a single proceeding after they have commenced; each must be defended separately. In our practice we occasionally advise registrants who face serial complaints across multiple zones — a coordinated strategy to pressure a legitimate holder — and the RDNH record built in the first case can be relevant context in later ones, even though each panel decides independently.

What are the possible outcomes when you seek a reverse domain name hijacking finding for a .ai domain?

A respondent who raises RDNH faces four possible outcomes in the panel decision. First, the panel transfers or cancels the domain and declines to address RDNH — the complainant wins on the merits. Second, the panel denies the complaint (the respondent wins) but declines to make an RDNH finding, often because the complaint, while unsuccessful, was not obviously abusive. Third, the panel denies the complaint and makes an explicit RDNH finding — the best result for the respondent. Fourth, in rare cases, a panel may deny the complaint on one or two elements without reaching all three and decline to address RDNH because the denial was on a different basis.

The RDNH finding itself is a published record. It creates no enforceable rights, awards no costs, and does not prevent the complainant from filing future actions in court. Its practical value is reputational and deterrent: future registrars, brand counselors, and business partners can see that the complainant deployed UDRP abusively against a legitimate registrant. For some respondents that record is exactly what the dispute is about.

For background on the full scope of respondent defense options across gTLD and ccTLD zones, see our service page at Respondent Defense and RDNH. For matters involving .ai alongside other national zones, including disputes where a parallel national procedure may be relevant, see ccTLD and National Dispute Procedures.

If you have received a UDRP complaint for a .ai domain and want to assess both your defense and an RDNH request, contact info@cognomenlaw.com.