Step-by-step: seek a reverse domain name hijacking finding for a .inf…

Step-by-step: seek a reverse domain name hijacking finding for a .inf. UDRP and ccTLD domain recovery and defense across .info. Email the firm to assess your c…

A brand owner files a UDRP complaint against your .info domain. The trademark they cite was registered after you acquired the name. The complaint relies on thin rights and a shaky factual record – yet the three-element test still puts the burden on you to respond. Getting a transfer order reversed is one outcome. Getting the panel to find reverse domain name hijacking (RDNH) is another, and in the right set of facts it is the outcome worth fighting for.

To seek a reverse domain name hijacking finding for a .info domain, a respondent must show that the complaint was brought in bad faith or with reckless disregard for the complainant's inability to prove its case – typically because the complainant knew its trademark post-dated the registration or lacked any legitimate claim. The procedure runs under the full UDRP, not the lighter URS, and the respondent has 20 days to file a response once the case formally commences. An RDNH finding carries no monetary award, but it is a published, public finding on the complainant's conduct.

This guide walks through each step, names the trap hidden inside it, and identifies the evidence that converts a successful defense into an RDNH finding.

Why .info domains sit inside the full UDRP – and what that means for your defense

.info is a generic top-level domain operated under ICANN accreditation, and every .info registrar is bound by the UDRP in exactly the same way as .com. That means the three-element test of Paragraph 4(a) applies in full: confusing similarity, no legitimate interest, and registration and use in bad faith – the last element is cumulative, not alternative. It also means WIPO, the Forum, CAC, and ADNDRC are all available venues.

Why does that matter for an RDNH argument? Because the UDRP is the only rulebook that has a developed, published RDNH jurisprudence. Panels have consistently held that a complainant who files knowing it cannot prove one of the three elements – particularly the bad-faith limb – acts in bad faith. .info does not have a separate national dispute procedure or a "registered OR used" standard the way Nominet's DRS does for .uk. The test is strict, and a complainant who cannot satisfy it has no cover.

The trap in this step: many respondents assume the venue does not matter. It does. WIPO panels have a longer track record of published RDNH findings and are the most frequently cited. If the complainant filed at the Forum or CAC and you are weighing RDNH, the forum's published precedent on the standard is thinner. That does not change the law, but it changes the persuasive weight of the decisions you can cite in support.

We regularly advise respondents who receive .info complaints that RDNH is a realistic goal only where the record shows deliberate overreach, not merely a complainant who over-estimated its chances. That distinction – overreach versus optimism – is what the rest of this guide builds toward proving.

Step 1: Assess the complainant's trademark and its date against your registration date

The single most powerful RDNH indicator is a trademark that post-dates the domain registration. Panels have consistently held that a complainant who was aware its mark did not exist at the time of registration could not credibly assert bad-faith registration and therefore brought the complaint in bad faith. That is the cleanest RDNH path available.

Pull the WHOIS/RDDS history for your .info domain on the day you receive the complaint. Screenshot the current record and retrieve any archived records through a domain history service. Then pull the complainant's trademark registration: jurisdiction, filing date, registration date, and goods/services class. If the registration date is after your acquisition date, document that gap precisely and preserve the evidence immediately. Do not rely on memory.

The trap in Step 1: a complainant may argue common-law or unregistered trademark rights predating your acquisition. Panels do recognize unregistered marks, particularly in the United States and some common-law jurisdictions. If the complainant holds a registered mark post-dating your domain but asserts pre-existing common-law rights, the assessment becomes more fact-intensive. Your response must address that argument directly, not assume the registration gap closes the issue. Ask: was the claimed common-law mark actually in use, in the relevant jurisdiction, at the time you registered? If the complainant offers no credible evidence of that, the bad-faith element fails on the face of the record.

For a read on whether the three UDRP elements are met in your specific .info dispute, reach us at info@cognomenlaw.com.

Step 2: Build your Paragraph 4(c) legitimate-interest record before anything else

RDNH does not exist as a standalone filing. You earn it through a successful respondent defense. That means proving at least one of the Paragraph 4(c) safe harbors: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; or a legitimate noncommercial or fair use of the domain. The stronger your legitimate-interest record, the weaker the complainant's case – and the easier the panel's path to finding that filing was bad faith.

For .info domains specifically, the "bona fide offering" safe harbor is the most commonly argued. .info was intended for informational use, and panels have consistently recognized that a domain pointing to a genuinely informational website, operated independently of any awareness of the complainant's mark, supports a legitimate-interest finding. To build this record, you need contemporaneous evidence: screenshots from the Wayback Machine or a commercial archive service showing the site's content at the time of registration and since; hosting records; any business correspondence referencing the domain; and registration receipts showing the acquisition price and source.

The trap in Step 2: respondents often send counsel a thin file – a current screenshot and a receipt. Panels look for evidence of continuous use and pre-notice purpose. A website launched the week after you received the complaint does not help; it can actively hurt. If the site has been dormant, focus your argument on the intent at the time of registration and the absence of any bad-faith conduct, not a site that looks constructed for litigation.

In a matter we handled (a .info dispute, spring 2025), the respondent had operated a news aggregator at the domain for several years before the complaint was filed. The complainant – a company whose trademark was registered approximately eighteen months after our client's domain acquisition – offered no evidence of pre-registration rights. The panel found legitimate interest, denied the transfer, and made an RDNH finding. The key document was a hosting invoice dated to the month of registration.

Step 3: Identify which bad-faith indicators the complainant asserted – and why each fails

Paragraph 4(b) lists four non-exhaustive bad-faith circumstances. In your response, work through each one the complainant invoked and explain, with evidence, why the facts do not meet it. A panel that finds none of the asserted bad-faith factors proven is well-positioned to conclude the complaint was filed without a reasonable basis.

The four Paragraph 4(b) circumstances are: (1) registering to sell the domain to the mark owner or a competitor at a profit; (2) registering to block the mark owner; (3) registering to disrupt a competitor's business; and (4) intentionally attracting users for commercial gain by creating confusion with the complainant's mark. Address every one the complaint raises, even if the argument looks weak on its face. Panels read responses expecting engagement with each stated ground.

The trap in Step 3: respondents sometimes write a general denial – "we did not register this domain in bad faith" – without addressing the specific factual assertions. That gives the panel nothing to work with. Structure your response element by element, Paragraph 4(b) factor by Paragraph 4(b) factor. If the complainant says you offered to sell the domain for a profit, address the specific communication they cite. If they say you operate a click-farm, show the actual use of the domain.

We have defended clients where the complainant's RDNH exposure was obvious from the complaint itself – the trademark was filed after the domain, the asserted bad-faith factors were generic boilerplate, and no factual connection between the registrant and the complainant's market was offered. In those cases, the response needs to make the structural gap in the complaint visible to the panel, not just assert it.

How do you make the RDNH argument itself, and when is it realistic?

RDNH is not a threshold finding – it requires an affirmative showing that the complainant brought the case in bad faith or with reckless disregard for the absence of a viable claim. Panels have set a high bar. Losing a case is not enough. Filing a weak case in good faith is not enough. The complainant must have known – or must have acted with willful blindness to the fact – that it could not prove the three elements.

The clearest RDNH scenarios under the UDRP are: (a) the complainant's trademark demonstrably post-dates the domain registration and the complainant was a sophisticated commercial entity or was represented by counsel at the time of filing; (b) the complainant held prior correspondence showing it knew the registrant had a legitimate use; or (c) the complaint materially misrepresents the facts – for instance, stating a date of first use that is demonstrably later than asserted.

To make the RDNH argument in your response: devote a separate section to it, named clearly. State the standard the panel applies. Then walk through the specific evidence showing the complainant could not have had a good-faith basis. Keep it short and factual; RDNH arguments that run to lengthy rhetoric about the complainant's motives tend to lose credibility with panels. The evidence carries the argument.

When is RDNH realistic? In our practice, the cases where RDNH is actually granted share two features: the trademark-date gap is clear from the public record, meaning the complainant had access to the same information the panel now has; and the complaint's factual narrative is contradicted by documents the respondent can produce. One without the other often results in a denied complaint without RDNH. Both together creates the conditions for the panel to make the finding.

To weigh UDRP against a court action for your case, or to assess whether an RDNH finding is available on your facts, email info@cognomenlaw.com.

Step 4: Choose the panel composition and file on time

The respondent has 20 days to file a response after commencement. Missing that deadline means defaulting, and a panel that decides on a default record has no respondent evidence to weigh. RDNH findings in default cases are rare because panels generally decline to make adverse findings against a party with no opportunity to respond. File the response.

Panel composition matters more for RDNH than for a straight defense. A single-member panel may deny the complaint but decline to make an RDNH finding, noting the finding requires a higher showing. Three-member panels have made RDNH findings in cases involving sophisticated complainants with clear post-registration trademark dates – those cases are on the public record at WIPO. If the RDNH argument is strong, requesting a three-member panel is worth considering. The filing-fee consequence: if the complainant requested a single panelist, the parties generally split the higher three-member fee.

The trap in Step 4: requesting a three-member panel when the underlying RDNH argument is only moderately strong. If the panel denies the complaint but declines RDNH, you have paid more than necessary and the outcome is the same. Weigh the strength of the trademark-date gap and the quality of the complainant's conduct before electing three members.

Step 5: Understand the cross-zone dimension – what if the complainant also holds a .com?

A complainant who pursues a .info domain may also hold – or simultaneously pursue – a .com or a ccTLD. The UDRP complaint for the .info runs on its own record, but the existence of parallel proceedings in other zones is worth addressing in your response for two reasons.

First, if the complainant filed the same complaint against your .com and lost – or withdrew it – that history is relevant to the RDNH argument. A prior failed complaint on essentially the same facts, followed by a second complaint on a related domain, is itself evidence of RDNH-adjacent conduct. Second, if the complainant holds a .com of the same name and files against your .info claiming it has priority, the question of whether the .info registration independently qualifies as bad faith still turns on the three UDRP elements, not on the existence of the .com.

The right route depends on the zone and the goal. If the domain is a .info and you want to keep it and secure an RDNH finding, the UDRP response is the primary vehicle. If you also face a parallel .com complaint, the two responses need to be coordinated – a concession in one record can undermine the other. If the complainant's conduct spans multiple zones and includes threats of court action, anticybersquatting litigation in the relevant jurisdiction may be relevant in parallel, handled with local litigation counsel where needed.

We have coordinated multi-zone respondent defenses where the complainant filed at WIPO for a .com and at a national registry for a ccTLD simultaneously. In one such matter (late 2024), the complainant's trademark in the .com case predated the registration by only a matter of weeks, but the evidence of legitimate use at the ccTLD was strong. The WIPO panel denied the .com complaint; the ccTLD panel found no abusive registration. The RDNH argument was strongest in the .com case, and that is where we focused the factual record.

What evidence actually decides the outcome?

Three categories of evidence drive RDNH findings more than any other. Treat each as a separate exhibit in your response.

First, timeline documents. Registration confirmation email or receipt; invoice from the registrar; any archived WHOIS/RDDS record from close to the registration date. These establish when you acquired the domain, which anchors the trademark-date comparison.

Second, use evidence. Wayback Machine screenshots – with dates – showing the domain's content at registration and at regular intervals since. Hosting invoices. Business correspondence referencing the domain. If the site was informational (appropriate for a .info domain), the content itself demonstrates the purpose was not to target the complainant's mark.

Third, complainant-knowledge evidence. Any prior correspondence where the complainant contacted you, acknowledged the domain's existence, or offered to buy it at market value. If the complainant engaged in pre-complaint negotiations or sent a cease-and-desist letter, those communications belong in the record. They show whether the complainant knew the facts before filing – a central issue in the RDNH analysis.

The trap in this step: gathering evidence reactively, after the response deadline. Start document collection the day you receive the complaint. The 20-day response window is shorter than it looks when you are locating archived records and coordinating with counsel.

Related at COGNOMEN

• Respondent defense and RDNH: full service overview for registrants facing a UDRP complaint
• Defending a domain registered before the complainant's trademark existed
• URS and new gTLD protection for domain owners in launch and post-launch phases