Step-by-step: defend a .info domain against a UDRP complaint

Step-by-step: defend a .info domain against a UDRP complaint. UDRP and ccTLD domain recovery and defense across .info. Email the firm to assess your case.

A complaint lands in your inbox. A brand owner claims your .info domain infringes a trademark and demands a transfer. You have 20 days to respond once the proceeding formally commences – and the clock does not stop while you read the fine print. The question is not whether to engage. It is how to defend a .info domain against a UDRP complaint intelligently, before the deadline expires.

The .info gTLD is fully subject to the UDRP. A respondent who does nothing – or who submits an unfocused response – risks losing a domain that may have real value, a legitimate history, or both. Under Paragraph 4(c) of the UDRP, a registrant has three documented safe harbors: a bona fide offering before notice of the dispute, being commonly known by the name, and legitimate noncommercial or fair use. Building the record around one or more of those safe harbors is the core of any sound defense.

This guide walks every step from the moment the complaint arrives to the day a panel issues its decision – with the trap hidden inside each step identified plainly.

Step 1: Understand what .info means for your defense

The .info gTLD is operated under ICANN's accreditation structure and applies the UDRP in its standard form. There is no separate .info-specific rulebook. That means the same three elements a complainant must prove for any .com dispute apply here: confusing similarity to a mark, your absence of rights or legitimate interests, and registration and use in bad faith – all three, cumulatively.

The all-three-elements requirement is the respondent's first structural advantage. A complainant who can show similarity and bad-faith use but cannot establish that registration itself was in bad faith will not prevail. We regularly advise registrants who acquired .info domains for generic, descriptive, or fan-site purposes long before any dispute arose – and who hold them cleanly under Paragraph 4(c). In those situations, the cumulative standard is a real shield.

The trap in Step 1: many registrants assume that because .info is a minor gTLD, the complaint is less serious or the panel less rigorous. That is wrong. WIPO and the Forum apply the same scrutiny to .info as to .com. A careless or late response carries exactly the same consequence – a default transfer.

One additional point distinguishes .info from some ccTLDs: there is no eligibility requirement to hold a .info domain. You do not need to be based in a particular country or operate in a regulated sector. That breadth can support a legitimate-interest argument, but it also attracts more abusive complaints because the complainant knows you have no eligibility-gating protection to rely on.

Step 2: Read the complaint carefully – and map it to the three elements

The first task after receiving a complaint is a cold, analytical read against the three UDRP elements, not an emotional one. Mark every factual assertion. Identify what evidence the complainant actually attached, as opposed to what is merely asserted. Panels evaluate evidence, not argument alone.

Ask three questions for each element:

• Similarity: Is the trademark registration genuine, currently registered, and in force? What class? What jurisdiction? A complainant relying on a trademark filed after your registration date has a severely weakened case on the bad-faith limb – registration cannot have been in bad faith if you had no way of knowing about a mark that did not yet exist.
• Legitimate interest: What does the complainant actually say about your use? Are there factual mischaracterizations you can rebut with evidence you already hold?
• Bad faith: Does the complaint rely on one of the Paragraph 4(b) factors – an offer to sell, a pattern of registrations, a competitor relationship, or a likelihood of confusion for commercial gain? If none of those situations fits your circumstances, say so directly and provide evidence.

The trap in Step 2: respondents sometimes skim the complaint and skip straight to drafting a rebuttal. That produces a response that misses the strongest point. Read the trademark certificate first. Verify the registration date against your WHOIS history. If the mark postdates your registration, that single fact – properly documented – may end the dispute.

How do the Paragraph 4(c) safe harbors work in a .info defense?

Paragraph 4(c) of the UDRP sets out three circumstances that, if shown, establish your rights or legitimate interests in the domain. You need only one. Demonstrating any of the following shifts the burden back to the complainant to rebut it.

The three safe harbors are:

1. Bona fide use before notice of the dispute: You were offering goods or services – or had concrete, documented steps toward doing so – using the .info domain before you received notice of the complaint. "Notice" here is the moment the complaint arrived, not the date of filing. Invoice records, hosting logs, development contracts, email correspondence with suppliers, or screenshots of a live site all qualify. The earlier the timestamp, the stronger the position.
2. Commonly known by the name: You, as an individual, business, or organization, are genuinely identified by the name in the domain. This does not require a registered trademark of your own. A business registration, a trade-name filing, a long-standing commercial presence, or even a well-documented personal name can support this safe harbor. The panels look at the totality of how you present yourself in commerce.
3. Legitimate noncommercial or fair use: You operate the domain as a criticism site, a fan resource, a commentary forum, or another noncommercial project. The panels scrutinize this carefully. A site that claims to be noncommercial but carries advertising, affiliate links, or a for-sale link does not meet the standard. The use must be genuinely noncommercial and not designed to mislead users about the complainant's products or services.

We have defended registrants who relied on each of these three grounds. The most common mistake is assuming that a single sentence in the response asserting "I have a legitimate interest" is sufficient. Panels require documentary evidence. Building that record before drafting a single word of the response is the correct sequence.

The trap in Step 3: registrants who have used the domain lightly – a parked page, an occasional redirect, or an under-construction notice – may have thin evidence of a bona fide offering. In those cases, the second and third safe harbors deserve serious attention. What matters is which safe harbor fits the facts, not which one feels most comfortable to argue.

If you have received a complaint against a .info domain and are unsure which safe harbor applies to your situation, we can help you map the evidence. For an assessment of your domain dispute, contact info@cognomenlaw.com.

Step 3: Gather and organize your evidence before you draft

Evidence decides UDRP outcomes. A well-argued response with weak documentary support routinely loses to a mediocre complaint backed by solid exhibits. Before drafting a single sentence, collect the following in date order.

• WHOIS or RDDS historical records showing your registration date and any prior registrations of the same domain.
• Screenshots or archived records (Internet Archive / Wayback Machine captures) showing the site's content over time.
• Business registration documents, trade-name filings, or incorporation certificates bearing the name in the domain.
• Correspondence, contracts, invoices, or other commercial documents referencing the domain or the name – dated as early as possible.
• Any records showing your awareness – or non-awareness – of the complainant's trademark at the time of registration. Absence of knowledge is an affirmative point when documented.
• Third-party press, media, forum posts, or social-media accounts confirming you are commonly known by the name, if that safe harbor applies.

The trap in Step 3: registrants gather only the favorable evidence and ignore anything potentially adverse. The complainant will attach it anyway. Addressing a weak point directly – with context – is almost always more effective than hoping the panel does not notice it. Panels notice.

Step 4: Draft the response – structure and the arguments that move panels

A UDRP response is not a court brief. It is a structured document addressed to a single panelist – or three – who will read dozens of similar filings each month. Clarity and direct engagement with the three elements carry more weight than volume. The response should track the complaint's own structure: similarity, then legitimate interest, then bad faith, each addressed in turn.

On similarity, your arguments are usually limited unless the complaint is unusually weak. The standard is low – "confusingly similar" is not a demanding test. Spend minimal time here unless the trademark is clearly dissimilar to the domain string, or unless the mark postdates your registration (in which case the point belongs in the bad-faith section too).

On legitimate interest, this is where the safe-harbor record you assembled in Step 3 does its work. State the applicable safe harbor, cite Paragraph 4(c) by its correct subparagraph, and then attach the documentary evidence. Panels look for: (a) a description of the use, (b) the timing relative to the complaint, and (c) the evidence itself as an exhibit. Do not describe evidence without attaching it.

On bad faith, rebut each Paragraph 4(b) factor the complainant has raised. If the complainant has not proved it, say so and explain why. If you can show you had no knowledge of the trademark at registration – because it was registered in a different jurisdiction, a different class, or after your acquisition – that rebuttal is often decisive. Bad faith requires knowledge, or at minimum circumstances from which knowledge can be imputed. Where it cannot, there is no bad faith.

The trap in Step 4: over-length responses that repeat the same argument across multiple sections. Panels impose no hard word limit, but a response that buries its strongest argument in repetition loses the reader's attention at exactly the wrong moment.

Step 5: Assess whether an RDNH finding is realistic

Reverse Domain Name Hijacking – or RDNH – is a finding that the complaint was brought in bad faith to deprive a legitimate registrant of a domain. It carries no monetary penalty, but it is a published finding that follows the complainant's name on the public record. Panels do not award RDNH frequently, but they award it more readily than many complainants expect when the filing is genuinely abusive.

The circumstances that typically support an RDNH request include:

• The complainant's trademark was registered after your domain registration, yet the complaint alleged bad-faith registration anyway – a factual impossibility the complainant had the means to verify before filing.
• The complainant is a sophisticated party (a large brand or a represented party) who filed knowing that the documentary record showed your legitimate prior use.
• The complaint relies entirely on speculation or inference rather than evidence, and no reasonable reading of the UDRP could support the claims made.
• The complainant used the procedure as leverage to avoid paying fair market value for a domain you legitimately hold.

In a recent matter – a .info domain held for a generic descriptive purpose, spring 2025 – we secured an RDNH finding after demonstrating that the complainant's trademark postdated the registrant's acquisition by several years and that the complaint asserted bad faith on facts that were plainly contradicted by the public WHOIS record the complainant had reviewed before filing.

The trap in Step 5: requesting RDNH as a default defensive add-on, without building a focused argument for it. A pro forma RDNH request that is not grounded in the specific conduct of the complainant rarely succeeds and can dilute the rest of the response. Request it when the facts genuinely support it – and then argue it properly.

For a focused read on when RDNH is realistic and how to pursue it, see COGNOMEN's RDNH service page.

If you believe the complaint against your .info domain was filed abusively, a focused pre-response analysis can identify whether an RDNH request is viable. Email info@cognomenlaw.com to discuss your situation.

Step 6: Choose your forum and decide on panel composition

The complainant chose the forum – most likely WIPO or the Forum. As a respondent, you do not get to change that choice. What you can do is request a three-member panel instead of the single panelist the complainant selected. This matters in close cases. Three panelists produce a majority decision; any one member who finds in your favor shifts the outcome or at minimum produces a published dissent that may support a later challenge.

The cost trade-off is real. If the complainant selected a single-member panel at WIPO (the USD 1,500 filing fee), and you request a three-member panel, the parties generally split the higher three-member fee of USD 4,000. That means you contribute roughly USD 1,250 – or the difference between the fee levels – toward the upgrade. In a dispute over a domain with genuine commercial value, that is usually a rational expenditure.

In a straightforward default case, or where the panel composition is unlikely to affect the outcome, a single panelist is sufficient. The three-member route makes sense when the case is close, when the complainant is well-resourced and the law is unsettled on a key point, or when an RDNH finding – which some practitioners argue carries more weight from a three-member panel – is a realistic goal.

Step 7: Know what happens after you file the response

Once the response is filed, the forum appoints the panel. The panelist reads the complaint and response, reviews the evidence, and issues a decision. There is no oral argument. There is no discovery. Panels rarely invite supplemental filings, and when they do, the invitation is narrow. The record you submit with your response is, in almost all cases, the complete record.

A standard case is normally decided within about two months of filing, often faster. The registrar implements any transfer order after a short implementation window – typically around ten days – during which a respondent who believes the panel made a material legal error may seek to initiate court proceedings to stay the transfer. That court option exists but is rarely used; the standard to obtain a stay is demanding.

If the panel dismisses the complaint, the domain stays in your name. Nothing is owed. No costs are awarded under the UDRP. If you also secured an RDNH finding, that finding is published in the case record and attributed to the complainant. If the complainant wins, the registrar transfers the domain unless you act within the implementation window.

The trap in Step 7: assuming the dispute is over when you file a strong response. Monitor the proceeding. Confirm the response was accepted. Track the panel appointment. If a supplemental filing is invited, respond promptly. A procedural miss late in the process can undo good work done early.

For a fuller view of the respondent-defense process across gTLDs and ccTLDs, see our respondent defense and RDNH service overview.

What if the .info dispute involves a parallel ccTLD registration?

Cross-zone exposure is common. A brand owner filing against a .info domain will often hold – or file against – the equivalent .com, .net, or a national ccTLD such as a .uk or .de registration at the same time or shortly after. Each zone is a separate proceeding. A UDRP decision on a .info domain does not bind a Nominet DRS panel deciding on the .uk equivalent, or a German court considering the .de variant.

That separation cuts both ways. A successful .info defense does not automatically protect the equivalent .com if that dispute follows. But a well-documented legitimate-interest record built for the .info defense can be repurposed directly in a parallel ccTLD proceeding – because the underlying facts about who you are, how long you have used the name, and what you knew at registration are the same across all zones.

The governing rule for ccTLDs varies significantly. Nominet's DRS for .uk uses an "abusive registration" test and reads the bad-faith limb as "registered or used" abusively – a lower bar for complainants than the UDRP's cumulative standard. EURid's ADR.eu for .eu adds an EU/EEA eligibility layer. For .de, there is no administrative procedure at all; the dispute is a German court matter, with a DENIC DISPUTE entry available to block transfer while litigation proceeds. If your exposure spans zones, the strategy for each proceeding needs to be calibrated separately.

For a worked illustration of how cross-zone eligibility and procedural differences played out in an Italian-zone dispute, see our case study on .it ccTLD eligibility.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview for domain registrants facing a UDRP complaint
• Seek an RDNH finding – when and how to pursue reverse domain name hijacking as a respondent
• Case study: .it ccTLD eligibility – cross-zone considerations in a contested domain dispute

About COGNOMEN

COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants – including respondent-side defense and reverse domain name hijacking. Our practice covers .info and every other gTLD as well as the principal ccTLD regimes. To discuss a domain complaint or defense, contact info@cognomenlaw.com.

Written by Anton Grant, COGNOMEN – respondent defense and RDNH practice.

To weigh your response strategy and assess the viability of an RDNH finding, email info@cognomenlaw.com.

Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Related

• Respondent Rdnh
• Seek Rdnh Finding Br
• Case Check Cctld Eligibility It

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.