Step-by-step: defend a .info domain used for criticism or commentary

Step-by-step: defend a .info domain used for criticism or commentary. UDRP and ccTLD domain recovery and defense across .info. Email the firm to assess your ca…

A consumer-advocacy group registers brandnamecomplaint.info to document safety issues with a product. Months later, a UDRP complaint arrives — the brand owner wants the domain transferred. The registrant has 20 days to respond once the case commences. Miss that window and the panel decides on the complaint alone.

To defend a .info domain used for criticism or commentary, a registrant must show that at least one of the Paragraph 4(c) safe harbors applies — most often legitimate noncommercial or fair use without intent to mislead — and that the complaint was filed in bad faith or lacks merit under all three UDRP elements. The UDRP applies to .info in full, administered most commonly through WIPO or the Forum. A strong defense turns on the evidence of intent at the moment of registration, not just current use.

This guide walks each step in sequence, flags the trap hidden in each one, and identifies when an RDNH finding — a formal finding that the complainant abused the process — is realistic.

Step 1: Understand the rules that govern your .info domain

The UDRP applies to .info without modification. This is not a ccTLD with its own local procedure. WIPO, the Forum, CAC, and the ADNDRC all accept .info complaints, and the complainant chooses the forum. You do not get to pick.

The complainant carries the burden on element one — confusing similarity — and must establish it formally. On elements two and three, once the complainant makes a prima facie case, the burden shifts to you to show legitimate interest. That shift is the procedural trap most respondents miss: you cannot simply deny the allegations. You must affirmatively build the record.

The UDRP offers only two remedies: transfer or cancellation. No money changes hands, no injunction issues, and no finding of trademark infringement is made. Knowing the ceiling matters because it shapes the argument. The complainant cannot use the UDRP to silence you permanently or impose damages. A determined brand owner who wants more than transfer must go to court — and that litigation is far more expensive and uncertain for both sides.

In our practice, we find that criticism-site registrants underestimate the formality of the UDRP process. This is a real arbitral proceeding with a published decision, a named panel, and an outcome that can become public and searchable. Treat every filing step as if a court clerk will review it.

Step 2: Assess the three UDRP elements against your specific facts

Before drafting a single word of the response, map the complainant's three-element burden against your facts. This is the analytical core of the defense — everything else is evidence and writing.

Element one — confusing similarity to a trademark — is almost always conceded in criticism cases. If the domain contains the brand name, the panel will find similarity regardless of the added term ("complaint", "sucks", "review", "fraud"). The minority view holds that a clearly pejorative suffix negates confusion; the consensus view does not. Do not build the entire defense on contesting element one. It wastes space and often damages credibility.

Element two — no rights or legitimate interests — is where the defense is usually won or lost. Paragraph 4(c)(iii) of the Policy provides a safe harbor for legitimate noncommercial or fair use of the domain, provided there is no intent to mislead consumers or tarnish the mark for commercial gain. A criticism site that publishes genuine commentary, carries no advertising, and does not offer competing goods passes that test with relative ease. A site that monetizes through affiliate links, collects competitor leads, or is actually for sale introduces commercial use that erodes the safe harbor.

Element three — registration and use in bad faith — requires both prongs. The complainant must show the domain was registered in bad faith and is being used in bad faith. A genuine critic who registered the domain before any dispute arose, with no intent to sell it to the mark owner, and who operates a real commentary page, has a strong argument on both sub-elements. Passive holding — registering the domain but doing nothing with it — is a known bad-faith indicator even in criticism cases. Maintain the site actively.

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

Step 3: Build the legitimate-interest record before you file the response

Evidence of legitimate interest must be contemporaneous or pre-date the dispute notice. Courts and panels are skeptical of evidence that appears only after a complaint arrives. This step is the one where timing is most critical — and where registrants most often leave gaps.

Gather the following before drafting the response:

• Registration history: a WHOIS or RDDS record showing when the domain was registered, compared to when the mark was first in use, when the product or service launched, and when the controversy the site addresses first became public.
• Site content archive: Wayback Machine snapshots, your own dated screenshots, any social media posts linking to the site, and any press coverage. The site must look like what you say it is.
• No commercial motive: documentation that the site carries no advertising, no affiliate links, no pay-to-post model, and no "contact us to resolve" language that could be read as an implicit offer to sell.
• Actual commentary or criticism: the substance of the content matters. Panels ask whether a reader arriving at the site would understand it to be criticism or would be confused into thinking it was an official brand page. Prominent disclaimers help. A header that reads "This site is not affiliated with [Brand]" is direct evidence.
• Your identity and motivation: panels are more persuaded by a named individual or organization with a documented grievance than by an anonymous domain holder with no stated reason for the registration. Anonymity is not fatal, but you should be prepared to explain it.

The trap in this step: assembling evidence is not the same as presenting it persuasively. A panel reads hundreds of cases. A response that dumps fifty documents without analysis gives the panel permission to ignore most of them. Organize the evidence around the specific legal elements, not around your narrative of events.

Step 4: Draft the response — structure, arguments, and what to omit

The response must be filed within 20 days of formal commencement. Extensions are rarely granted and only by mutual agreement or in extraordinary circumstances. Use the full period if you need it; do not rush a weak submission.

A well-structured response for a criticism-site defense covers these points in order:

1. Procedural objections first, if any exist — standing issues, missing annexes in the complaint, failure to identify the mark registration properly.
2. Concede element one where appropriate, briefly, and pivot immediately to elements two and three. This signals to the panel that you understand the rules and are not wasting their time.
3. Lead on Paragraph 4(c)(iii) — legitimate noncommercial or fair use. State the legal standard, then apply your facts to each part of it: nature of use (commentary), commercial gain (none), intent to mislead (none), tarnishment for commercial gain (none).
4. Argue bad faith on element three in the alternative: even if the panel finds some commercial element, the registration was not made in bad faith — the registrant had no prior knowledge of a dispute claim, did not register the domain to sell it to the mark owner, and did not register it to disrupt the complainant's business for competitive advantage.
5. Raise RDNH if the facts support it. See Step 6 below.

What to omit: personal grievances that have no legal relevance, claims about the complainant's character unless directly relevant to bad faith, and arguments that require the panel to make findings outside its narrow jurisdiction. The UDRP panel cannot adjudicate defamation, consumer fraud, or product liability. Raising them crowds the response and confuses the panel about what it is being asked to decide.

Step 5: Determine whether to request a three-member panel

The complainant ordinarily requests a single-member panel. The respondent may request a three-member panel, which triggers a cost-sharing mechanism: the parties generally split the higher three-member fee. At WIPO, a single-member panel costs USD 1,500 for the complainant; a three-member panel costs USD 4,000, with the fee split as determined under the applicable WIPO supplemental rules.

Should you request three members? The analysis depends on the profile of the case.

If the complaint is clearly abusive — filed by a well-resourced brand owner against a registrant with a documented, genuine commentary purpose and no commercial motive — a three-member panel often produces a more deliberate analysis. Dissenting views are possible, and the deliberation that precedes a signed decision by three panelists gives close cases more careful treatment. RDNH findings, in particular, tend to emerge more often from three-member panels where at least one panelist is willing to name the abuse. That said, a three-member panel is not a guarantee of a more favorable outcome. It adds cost to the respondent's side and extends the timeline modestly.

If the case is factually straightforward — the site is plainly a criticism page, the content is unambiguous, the registration predates any dispute — a single-member panel may be entirely adequate. In our experience advising respondents in .info and gTLD criticism-site cases, the decision to request three members is driven by two factors: the credibility risk of a single-panelist adverse finding becoming public, and the realistic prospect of RDNH.

Step 6: When is an RDNH finding realistic — and how do you pursue it?

Reverse Domain Name Hijacking is a formal finding that the complainant brought the UDRP in bad faith, seeking to deprive a legitimate registrant of a domain to which the registrant has a valid claim. The finding carries no monetary penalty — that is a limitation of the UDRP. But it is public, searchable, and attached permanently to the complainant's name and counsel's record. For brand owners who file frequently, an RDNH finding has genuine reputational and strategic weight.

Panels apply a high threshold. Filing a complaint that ultimately fails is not, by itself, sufficient for RDNH. The panel looks for something more: the complainant knew or should have known at the time of filing that the respondent had a legitimate interest; the complainant relied on a trademark registered after the domain; the complaint was filed as a tactical move to silence criticism rather than to vindicate a genuine intellectual property right; or the complainant's counsel filed without adequate investigation.

In criticism-site cases, RDNH is most realistic when all of the following align: the domain is clearly expressive in nature (a "sucks" or "complaint" suffix, an established commentary site), the complainant's trademark postdates the domain registration, the complaint mischaracterizes the registrant's purpose, and the complainant either ignored the Paragraph 4(c) safe harbors or addressed them perfunctorily. Where all of those factors appear, we make the RDNH argument expressly, with a dedicated section in the response, and request a three-member panel to maximize the probability that at least one panelist will reach the finding.

In a recent matter — a .info criticism site, autumn 2024 — we secured both a denial of the transfer and an RDNH finding for a registrant who had operated a genuine consumer-advocacy page for over two years before the complaint arrived. The complainant's trademark had been registered several months after the domain was created. The panel found that the complaint was filed with constructive knowledge of the respondent's legitimate interest and dismissed it accordingly.

Step 7: After the decision — what happens next, and what to watch for

If the panel denies the complaint, the domain stays with you. The registrar implements no transfer. There is no appeal within the UDRP system itself — a losing complainant's only recourse is to file a court action within a specified period under the applicable national law to challenge the result. That rarely happens in criticism cases, but it is worth knowing. In our practice, we brief respondents on the post-decision window and advise whether any precautionary steps are warranted.

If the panel orders a transfer, you have a brief window — typically 10 business days — during which ICANN's rules require the registrar to hold the implementation. In that window, you may file a court action in a jurisdiction of mutual jurisdiction elected by the parties (under Paragraph 4(k) of the Policy) to stay the transfer pending judicial review. Court action is expensive, and the bar for a stay is high. But for a registrant with a strong legitimate interest and a decision that rests on a factual error, it is a real option. We coordinate with local litigation counsel in the relevant jurisdiction for that step.

What to watch for after a denial: complainants sometimes refile. A serial refiling based on materially identical facts is itself an abuse, and a panel presented with a prior denial and an RDNH finding in the same matter is unlikely to be sympathetic to a fresh complaint. Document everything. Keep the site's content policy consistent. And monitor the domain registration for any attempt to dispute the renewal — criticism sites sometimes face a complaint timed to the registration anniversary when the domain briefly shows as "recently renewed."

If a prior filing produced an adverse outcome, or if you have just received a complaint on a criticism or commentary domain, email info@cognomenlaw.com to assess the respondent-side options.

Related at COGNOMEN

• Respondent defense and RDNH: services for registrants facing UDRP complaints
• How missing the UDRP response deadline changes the outcome
• Reversing an unauthorized domain transfer: a step-by-step guide for .net registrants