Respond to a UDRP complaint within the deadline for a .info domain: w…

Respond to a UDRP complaint within the deadline for a .info domain: w. UDRP and ccTLD domain recovery and defense across .info. Email the firm to assess your c…

A UDRP complaint arrives naming your .info domain. The clock starts immediately. You have 20 days from the date the proceeding formally commences to file a response – and if you miss that window, a panel will decide on the complaint alone, with no counter-argument on the record.

Responding to a UDRP complaint for a .info domain means satisfying the same three-element test that governs every gTLD dispute: the domain must be identical or confusingly similar to a mark the complainant holds, the registrant must lack rights or legitimate interests, and the domain must have been registered and used in bad faith – all under Paragraph 4(a) of the Policy. The respondent's job is to defeat at least one of those elements, and the 20-day response deadline is set by the UDRP Rules, not by the forum or the complainant. Filing at WIPO, where the standard filing fee for a single-panel complaint begins at USD 1,500, takes no more than a few days once the complaint is lodged.

This analysis covers the procedural mechanics specific to .info, the Paragraph 4(c) safe harbors that decide most defenses, what evidence panels weigh in disputed cases, when a reverse domain name hijacking finding is realistic, and the practical next step for a registrant facing a live complaint.

Why .info domains fall squarely under UDRP jurisdiction

.info is an ICANN-accredited generic top-level domain, and every ICANN-accredited registrar is contractually bound to apply the UDRP to disputes over domains registered under it. There is no separate national procedure, no opt-in requirement. A complainant files with an approved dispute-resolution provider – WIPO and the Forum together handle roughly 97% of all UDRP proceedings – and the registrar is obligated to implement any transfer or cancellation order that results.

That contractual architecture matters for the respondent. Unlike a .uk domain governed by the Nominet DRS, or a .de domain that sends parties to the German courts, a .info dispute is entirely within the UDRP framework. The rules are the same as for a .com, .net, or .org dispute. The three elements are cumulative: a complainant wins only if all three are established. Miss one, and the complaint fails.

In our practice, .info respondents sometimes assume the domain's lower profile reduces the likelihood of a complaint. It does not. Brand owners file against .info registrations with the same frequency and in the same forums as against .com registrations. The zone does not affect the outcome; the facts do.

What does the 20-day response deadline actually require?

The 20-day response period begins on the date the forum formally commences the proceeding – which is not the date the complainant filed, but the date the forum notified the respondent that the complaint was complete and administratively compliant. That distinction is important: a complaint can sit in review for days before commencement, and the 20-day window begins only then.

The response itself must conform to the provider's rules. At WIPO, the response is submitted through an online filing system. It must include a statement of the grounds on which the respondent contends the complaint should be rejected, any documentary evidence in support, and a certification that the information is complete and accurate. Failure to include a certification is a common procedural defect that panels handle with some latitude – but relying on that latitude is not a strategy.

Extension requests are possible but narrow. The provider may grant a short extension for good cause shown, but the bar is not low. Operational disruption, documented illness, or a demonstrable need to gather records from third parties may qualify. "I did not see the complaint in time" does not. We have defended matters where the registrant's contact details in WHOIS were outdated, causing delivery to a dormant address; panels treat that as the registrant's own risk.

What happens on default? A panel decides on the complaint record alone. Default does not mean automatic transfer – the panel must still independently assess whether all three elements are met – but the absence of a response leaves the respondent's side of the factual picture entirely blank. Panels regularly note the absence and give it adverse weight when the complaint's evidence of bad faith is colorable.

How do panels assess the three elements for a .info registrant?

The first element – confusing similarity – is almost always met when the domain incorporates a complainant's registered mark verbatim. The addition of a generic descriptor, a geographic term, or the TLD itself (.info) is routinely disregarded in the similarity analysis. Panels treat .info as a purely technical suffix. A registrant who relies on the suffix to distinguish the domain from the mark will lose on element one.

The second and third elements are where the defense lives. Under Paragraph 4(a)(ii), the burden to demonstrate the respondent's lack of rights or legitimate interests is on the complainant – but only at a prima facie level. Once the complainant makes out a prima facie case (the mark is well-known; the registrant is not authorized; the domain points at content unrelated to any bona fide use), the burden effectively shifts. The respondent must then produce affirmative evidence of one or more of the Paragraph 4(c) safe harbors.

Bad faith under Paragraph 4(a)(iii) requires both registration in bad faith and use in bad faith – a cumulative standard. Panels have consistently held that passive holding of a domain (pointing it at a blank page or a parking service generating pay-per-click links keyed to the complainant's mark) can constitute use in bad faith, even without active deception. That doctrine significantly narrows the space for inaction as a defense.

The cumulative "registered AND used" bad-faith requirement is the UDRP's sharpest structural difference from the Nominet DRS for .uk, which reads "registered OR used." A .info respondent who registered the domain before the complainant's mark existed, and has consistently used it for an unrelated purpose, can make a compelling case that neither registration nor use was in bad faith.

Which Paragraph 4(c) safe harbors are most effective for .info respondents?

Paragraph 4(c) of the Policy sets out three non-exhaustive circumstances in which a respondent can establish rights or legitimate interests: (1) bona fide use of the domain in connection with an offering of goods or services before the complainant gave notice of the dispute; (2) being commonly known by the domain name, with or without a trademark; and (3) legitimate noncommercial or fair use without intent to mislead consumers or tarnish the mark.

The bona fide offering safe harbor is the strongest in commercial contexts – but it requires evidence of actual use before notice, not a declaration of intended use. Panels distinguish genuine businesses from sham websites assembled after a complaint is threatened. The markers of genuineness include: sustained online activity over time, verifiable revenue or transactions, a consistent brand identity, and third-party records (invoices, web-analytics exports, archived pages from the Wayback Machine) that predate the dispute.

The commonly known by the name safe harbor applies in a narrow set of circumstances: the registrant's own name, a registered trade name, or a widely used nickname that predates the complainant's mark. Personal-name cases are decided frequently and the doctrine is well-developed. The respondent must show more than the assertion; registrations of the personal or corporate name in other contexts, published materials, or business filings carry weight.

The fair use safe harbor covers criticism sites, fan sites, and commentary – but with a condition that is routinely misunderstood. The use must not mislead consumers. A criticism site that captures the complainant's mark in the domain without clearly identifying itself as critical at the landing page will fail this safe harbor. Panels have consistently required clear, prominent disclosure on the site itself. Fair use of a .info domain for genuine commentary is viable, but the execution matters as much as the intent.

Which safe harbor fits depends entirely on the respondent's actual pre-complaint conduct. We advise registrants to gather that evidence before the response is filed, not after. In practice, the quality of the evidence – the contemporaneity, the third-party corroboration, the completeness – decides whether a panel finds the safe harbor plausible.

For an assessment of which Paragraph 4(c) safe harbor applies to your .info domain and what evidence will support it, contact info@cognomenlaw.com.

What evidence decides the outcome, and how should a respondent build the record?

Panel decisions turn on the record, and the record is closed once both parties have filed. There are no depositions, no discovery orders, and no ability to supplement after the panel is constituted (absent exceptional circumstances, and even then at panel discretion). Building the response record is the respondent's one opportunity to shape the outcome.

The strongest .info defense records typically contain the following categories:

• Registration history: the original registration date and the chain of ownership since. If the domain was registered before the complainant's mark was filed or published, that timeline is the centerpiece of the defense. WHOIS history tools and registrar records document it.
• Pre-dispute use evidence: archived web pages (Wayback Machine screenshots with timestamps), hosting records, analytics exports, and correspondence with customers or partners that demonstrably predate the complaint notification.
• Complainant's trademark record: the filing date, jurisdiction, and scope of the complainant's mark. A complainant whose mark postdates the domain registration has a structural problem on the bad-faith element. The respondent should pull the USPTO, EUIPO, or other registry record and put it in the response.
• Third-party corroboration: invoices, published articles, business-registration documents, or domain-industry records that independently confirm the respondent's business activity under the domain name.
• The complainant's demand history: if the complainant attempted to purchase the domain before filing, that correspondence is relevant – both to the timeline and, in some cases, to reverse domain name hijacking.

The complaint itself often signals which element the complainant regards as weakest. A complaint heavy on the confusing-similarity analysis but thin on bad-faith evidence is telling the respondent where to press. Reading the complaint carefully before drafting the response is not optional; it is the starting point of the strategy.

In a recent matter – a .info domain held by a small technology firm, spring 2025 – we built a defense record centered on archived product pages and a customer invoice database predating the complainant's trademark registration by more than two years. The panel denied the transfer and noted the absence of any bad-faith indicator at the time of registration. The domain remained with our client.

When is a reverse domain name hijacking finding realistic?

Reverse domain name hijacking (RDNH) is a panel finding that the complainant brought the proceeding in bad faith – typically to deprive a legitimate registrant of a domain to which the complainant has no valid claim. An RDNH finding carries no monetary penalty under the UDRP, but it is a public reputational judgment against the complainant and is cited in subsequent proceedings.

Panels grant RDNH findings in a defined set of circumstances. The clearest is when the complainant's trademark postdates the registration of the domain by a substantial margin, and the complainant – with access to that timeline – filed anyway. Panels have consistently described this as an abuse of the process. A second common scenario is the complainant who knew the registrant had a legitimate use of the domain but filed to use the proceeding as a lever in a commercial negotiation. A third is the complaint that overstates the complainant's trademark rights or misstates the evidence.

What RDNH does NOT cover is a complaint that was simply wrong on the merits. A complainant who files in good faith, makes out a colorable case, and loses on element two or three has not committed RDNH. The panel must find something more – bad faith in the filing itself, or at minimum, knowledge of the respondent's legitimate interests that should have precluded the complaint.

For .info respondents, the RDNH argument is worth assessing in every case where: the domain was registered before the complainant's mark; the complainant attempted to buy the domain before filing; the complaint contains demonstrable factual errors; or the complainant is a serial UDRP filer with a history of overreach. We include an RDNH argument in responses where the record supports it. Where it does not, making the argument weakens the overall submission.

In a second matter we handled – a .info generic-term domain, autumn 2024 – the complainant's mark had been filed roughly eight months after our client registered the domain for use in an unrelated service business. The panel denied the complaint and issued an RDNH finding, noting that the timeline was apparent from the complaint's own exhibits. That result required a precisely constructed response with the timeline at its center.

If you believe the complaint against your .info domain is abusive, or if the complainant's mark postdates your registration, email info@cognomenlaw.com to assess whether an RDNH finding is realistic on your facts.

How does the forum choice affect a .info respondent's position?

Complainants choose the forum: WIPO, the Forum, CAC, or ADNDRC. The respondent cannot redirect the case to a different provider, but the choice of forum affects a few procedural details that matter.

At WIPO, the standard case proceeds under the WIPO Supplemental Rules, which include a word limit for submissions and a defined schedule for panel selection. WIPO's panel pool is large and geographically diverse. An expedited procedure is available for single-panel cases covering up to five domains, with decisions typically within about one month. If a complainant has filed for expedited treatment, the respondent's deadline and the pace of the proceeding both change – check the commencement notice carefully.

At the Forum, the supplemental rules differ in detail. The core timeline – 20 days to respond – is the same under the UDRP Rules, which apply regardless of provider. The Forum's case management interface and its approach to supplemental filings differ slightly from WIPO's.

At CAC, which handles a smaller share of proceedings and offers the lowest entry-level filing fee (beginning around USD 500–800), the procedural rules are broadly similar. CAC cases are less common for .info, but they occur. The response mechanics are the same.

One structural right the respondent holds in all three forums: if the complainant elected a single-member panel, the respondent may request a three-member panel. The cost of upgrading is shared between the parties, with the respondent paying a portion. A three-member panel introduces more deliberative review and, in some cases, a written dissent – which can itself become evidence of the case's complexity. The right to request a three-member panel must be exercised in the response or the opportunity is lost.

What are the realistic outcomes for a .info respondent who files on time?

The outcome of a UDRP proceeding is always fact-specific and panel-discretionary. No outcome can be guaranteed, and any adviser who tells a registrant otherwise is not being straight. What can be assessed – and should be, before the response is filed – is the strength of the defense across each of the three elements.

A registrant who holds a .info domain registered before the complainant's mark, with documented use since registration that is unrelated to the mark, and no commercially suspicious conduct (no parked pay-per-click links keyed to the mark, no demand for payment, no pattern of similar registrations), has a strong factual position on elements two and three. That position does not guarantee a denial, but it substantially reduces the risk of transfer.

A registrant who registered a .info domain containing a well-known mark after the mark was established, with no demonstrated use and pointing at a parking page, is in a materially weaker position – regardless of subjective intent. The evidentiary gap is the problem. The response must find something in the record to work with.

The decision matrix works as follows. If the domain predates the mark: lead with the registration timeline as the centerpiece of the bad-faith defense; assess whether RDNH is arguable; build the Paragraph 4(c) evidence as secondary support. If the domain postdates the mark but use is genuine: lead with the safe harbor, emphasize the pre-complaint use evidence, and ensure the third-party corroboration is robust. If the domain postdates the mark and use is thin: assess honestly whether the risk of transfer outweighs settlement or the cost of a full defense; explore whether the complainant would accept a resolution; consider whether the domain has sufficient strategic value to justify the proceeding.

We regularly advise registrants at that honest assessment stage before any response is filed. The goal is not to file a response in every case regardless of merit. It is to deploy the response where the facts support it and achieve the best outcome – whether that is a panel denial, an RDNH finding, or a negotiated resolution.

Cross-zone and cross-forum considerations for .info respondents

A .info dispute is almost always a gTLD dispute under the UDRP, but respondents sometimes hold parallel registrations in ccTLDs – a .uk, a .de, or a .eu variant of the same name. A UDRP decision against the .info domain does not automatically affect the ccTLD registrations. The procedures are separate, the rules differ, and a panel's findings in a UDRP proceeding are not binding in a Nominet DRS or a German court proceeding.

That separation cuts both ways. A complainant who wins a .info transfer must file separately against each ccTLD registration, under the applicable national procedure. A Nominet DRS for .uk, for example, requires the complainant to show an "abusive registration" – a standard that reads "registered OR used" abusively, a meaningfully lower bar than the UDRP's cumulative "registered AND used" in bad faith. A respondent who narrowly survives a UDRP proceeding on the bad-faith element may face a harder fight in a subsequent .uk proceeding on the same facts.

The .eu procedure, administered through the CAC's ADR.eu platform, introduces an additional complexity: eligibility. The complainant must demonstrate an EU or EEA nexus. A non-EU complainant without that nexus may be unable to use the .eu procedure at all, leaving the respondent in a stronger structural position on that zone.

For respondents facing a .info complaint who also hold ccTLD variants, the strategy should account for the full zone picture from the outset. A UDRP response that succeeds on RDNH does not foreclose a future complainant; it creates a public record that may deter one. Managing the .info proceeding with the broader domain portfolio in view is the right approach.

See also our analysis of defending a generic domain in the .in zone for a parallel discussion of how respondent-side strategy adapts across zones.

The procedural trap: missing the deadline and the options that remain

What happens when a registrant misses the 20-day window? The panel proceeds on the complaint alone. Default does not, as noted earlier, mean automatic transfer – but the record will contain only the complainant's version of events, and panels apply their own review rather than the adversarial testing of the evidence that a response provides.

Post-deadline options are genuinely limited. Late filing is at the forum's discretion, not a right. A request to reinstate the response period must be filed immediately on the registrant's realization of the default and must show good cause. A panel already constituted has no obligation to accept a late response. We have seen late responses accepted in exceptional circumstances – a documented medical emergency, a provably mis-delivered commencement notice due to a registrar error – but the bar is high and the outcome is uncertain.

If a transfer order is issued and implemented, the registrant's recourse is court action. The UDRP explicitly preserves the right of either party to submit the dispute to a court of competent jurisdiction. A registrant who believes the transfer was wrongly ordered can pursue relief in the relevant jurisdiction, but that route is slower, more expensive, and requires local litigation counsel in the applicable jurisdiction.

The structural lesson is straightforward. The UDRP's 20-day window is the respondent's practical moment. Missing it does not end all options, but it dramatically narrows them and shifts the cost of recovery to a much more expensive path.

For information on the broader respondent-defense service, including portfolio-level monitoring and pre-complaint strategy, see COGNOMEN's respondent defense and RDNH service.

If the .info domain in dispute was acquired through a transaction and you are evaluating the acquisition history or prior dispute record, our domain due diligence service covers chain-of-title review and prior proceeding analysis.

Related at COGNOMEN

• Respondent Defense and RDNH – full-service defense and RDNH filing across WIPO, the Forum, and CAC
• Case: Defending a Generic Domain in the .in Zone – zone-specific respondent strategy
• Domain Due Diligence – pre-acquisition dispute history and chain-of-title review