How to respond to a UDRP complaint within the deadline for a .pl doma…

How to respond to a UDRP complaint within the deadline for a .pl doma. UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your cas…

A UDRP complaint arrives naming your .pl domain. The clock starts immediately. You have 20 days from formal commencement to file a response – and missing that window almost certainly means a default transfer order against you, regardless of the merit of your registration.

Responding to a UDRP complaint within the deadline for a .pl domain requires understanding two overlapping systems: the UDRP's three-element test under Paragraph 4(a), and the distinct position of .pl as a Polish country-code zone that does not run under the UDRP by default. A well-built response establishes your rights or legitimate interests under Paragraph 4(c), rebuts bad-faith allegations, and – where the complaint is opportunistic – positions the case for a reverse domain name hijacking (RDNH) finding. The timeline is fixed; the strategy is not.

This page covers the procedural and substantive framework, the evidence that decides .pl respondent cases, what an RDNH finding requires, and when to act.

Does the UDRP Actually Apply to Your .pl Domain?

The UDRP does not automatically govern .pl domains, and that threshold question determines which rulebook you are defending under. Poland's country-code zone, .pl, is administered by NASK, the Polish national registry. NASK has not appointed WIPO or any UDRP-accredited provider as its dispute-resolution service. The governing Polish law and NASK's own dispute rules apply to .pl registrations, not the UDRP or the Uniform Rapid Suspension system designed for new gTLDs.

What does this mean in practice? If you receive what is styled as a "UDRP complaint" for a .pl domain, read the filing header carefully. Several possibilities exist. First, the complainant may also hold a parallel .com or other gTLD domain in dispute and has filed under the UDRP for that name, while citing your .pl as contextual evidence. Second, the registrant may have registered through an ICANN-accredited registrar that offers .pl under a reseller arrangement; in rare configurations this creates procedural complexity about which body has jurisdiction. Third, the complaint may be filed under a Polish court proceeding rather than the UDRP, dressed in the language of cybersquatting law.

In our practice, we regularly advise registrants who receive demand letters or procedural notices that conflate UDRP language with national law claims. Getting the jurisdictional question right before drafting any response is the single most important step. Filing a UDRP response in a national-court dispute, or vice versa, wastes time you do not have.

For true .pl disputes – that is, disputes about .pl domains decided by the Polish courts or under NASK procedure – the applicable national trademark act and unfair-competition provisions govern. The complainant does not prove "registered and used in bad faith" under Paragraph 4(a); the court or NASK evaluates rights under national law. The safe harbors in Paragraph 4(c) do not apply by name, but analogous defenses exist: prior rights in the name, legitimate commercial or descriptive use, and absence of intent to harm the rights holder.

Where the UDRP does arise for .pl – because a parallel gTLD domain is at issue, or because the registrar's contract incorporates the Policy – the analysis below applies in full.

If you are uncertain which procedure applies to your .pl domain dispute, contact info@cognomenlaw.com before taking any action. The jurisdictional question decides your strategy entirely.

What Does a UDRP Response Actually Require?

A proper UDRP response must address all three elements of Paragraph 4(a) – and the respondent's task is not to prove a positive case but to rebut each element the complainant must establish. Understanding the structure of that burden is essential before you write a single word of the response.

Under Paragraph 4(a), the complainant must prove: (1) the domain is identical or confusingly similar to a trademark in which it has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. All three elements must be satisfied. A failure on any one defeats the complaint.

The first element – similarity – is largely objective. Panels examine the domain string against the mark, typically ignoring the TLD suffix. Where the domain and the mark are identical or near-identical, the first element is usually conceded. Your response should acknowledge this where true and reserve your argument for elements two and three, where the real contest lies.

The second element – rights or legitimate interests – is where the Paragraph 4(c) safe harbors live. The complainant bears the ultimate burden, but in practice the panel expects the respondent to come forward with evidence. The three recognized safe harbors are: (a) bona fide use of the domain in connection with an offering of goods or services before any notice of the dispute; (b) the respondent is commonly known by the domain name; and (c) legitimate noncommercial or fair use, without intent for commercial gain by misleading consumers or tarnishing the mark.

The third element – bad faith – requires both registration and use in bad faith, cumulatively. Panels have consistently held that registration in good faith cannot be retroactively converted to bad faith by a later dispute. If you registered the domain without knowledge of the complainant's mark, for a legitimate purpose, and have used it consistently with that purpose, the bad-faith element fails.

The 20-day response window from commencement is set by the UDRP Rules and does not bend easily. Extensions are rare and require consent from the provider or a showing of exceptional circumstances. Filing late almost certainly means the panel proceeds on the complaint alone.

How Do You Build a Legitimate-Interest Defense for a .pl Domain Respondent?

Building the legitimate-interest record is the core of the respondent's affirmative case. It is not enough to deny the complainant's allegations; you must place evidence of your own rights or interests squarely before the panel.

Start with the chronology. When did you register the domain? Was the complainant's mark in existence and known in your territory at that time? Panels place significant weight on the registration date relative to the mark's first use and registration. A domain registered years before the complainant's trademark application is a powerful – though not conclusive – indicator of good faith.

Next, document your use. Website archives (independently verifiable), invoices, business records, correspondence, and branding materials showing consistent use of the domain for your own goods or services all support the bona-fide-use safe harbor. The use must predate notice of the dispute; post-complaint website changes are viewed with suspicion by panels and should be avoided.

Personal name registrations deserve special attention. Where the domain corresponds to your personal name or the name of a natural person associated with your business, panels have recognized this as grounds for legitimate interest even without a registered trademark of your own. Document the connection clearly.

For descriptive or generic terms, the analysis shifts. A complainant cannot own exclusive rights in a common descriptive phrase merely by registering a trademark that incorporates it. If the domain is a generic word or phrase in Polish or in English, and you registered it for its descriptive value – to attract relevant search traffic or to serve a descriptive business purpose – that registration can qualify as legitimate even if the complainant holds a stylized or composite mark that contains the term. We have defended registrations on exactly this basis.

In a recent matter – a .com domain dispute involving a Polish-market brand, spring 2025 – we built a legitimate-interest defense for a registrant who had operated a descriptive services directory under the domain for several years before the complainant's mark was filed. The panel found the second element not established and denied the complaint. No RDNH finding was sought, as the complainant had reasonable grounds even if the filing ultimately failed.

One further consideration: reseller or affiliate relationships. If you registered the domain to operate as a legitimate reseller of the complainant's products, panels have recognized that a bona-fide reseller can have legitimate interests in a mark-incorporating domain under the conditions articulated in the widely applied reseller doctrine. Those conditions include: actually selling the rights holder's products, not using the domain to sell competing goods, accurately disclosing the relationship, and not blocking the rights holder from registering its own domain. Satisfying all four is essential; partial compliance is typically insufficient.

To build a respondent record for a UDRP or .pl domain dispute, reach us at info@cognomenlaw.com. We assess the Paragraph 4(c) safe harbors, assemble the legitimate-interest evidence, and draft a response that addresses each element directly.

When Is a Reverse Domain Name Hijacking Finding Realistic?

Reverse domain name hijacking (RDNH) is a finding that a UDRP complaint was brought in bad faith – specifically, to deprive a legitimate registrant of a domain to which it has a right. The finding carries no monetary penalty, but it is a significant reputational marker for the complainant and its counsel. Panels do not make RDNH findings lightly, and simply prevailing on the defense is not enough to obtain one.

What fact patterns actually produce RDNH findings? Panels have consistently held that the following, alone or in combination, support the finding: the complainant filed knowing the respondent had a legitimate interest; the complainant's trademark postdates the domain registration by a significant margin; the complainant had evidence of the respondent's good faith but withheld it from the filing; the complaint mischaracterized the nature of the domain or the respondent's use; or the complainant filed solely to pressure a sale rather than to vindicate trademark rights.

The timing of the mark relative to the domain is particularly powerful. Where a registrant can show that the domain predates the complainant's trademark by years, and the complainant filed without acknowledging that timeline, the inference of bad faith on the complainant's part is strong. We have pursued RDNH findings in cases where the complainant's first trademark application postdated the domain registration by more than three years, and the domain had been in active commercial use throughout that period.

RDNH is also available in the Nominet DRS for .uk domains, a point worth noting for registrants holding parallel names across ccTLDs. For .pl specifically, an analogous concept of abuse of process may be available in national court proceedings, though the label and the test differ from the UDRP formulation.

One caution: seeking an RDNH finding when the facts do not clearly support it can backfire. Panels notice when a respondent raises RDNH as a defensive reflex rather than on a principled basis. Reserve the argument for cases where the chronological and evidentiary record genuinely supports it.

What Evidence Decides the Outcome of a .pl Respondent Case?

The evidence you submit with your response – not your legal argument alone – is what actually moves panels. Argument without evidence is unconvincing; evidence without framing fails to connect to the elements. Both matter, and the quality of the record you build in the response determines the outcome far more than rhetorical skill.

For the legitimate-interest defense, the primary evidence categories are: domain registration confirmations showing the registration date; website archive captures (from services such as internet archive tools) showing the site's content and active use over time; business registration records, tax filings, or trade licenses showing the registrant's business activity under the relevant name; correspondence predating the dispute that shows the domain was used in a genuine commercial context; and – where the personal-name defense applies – identity documents and evidence of professional or commercial activity under the name.

For the bad-faith rebuttal, the key evidence is: any record showing the registrant did not know of the complainant's mark at registration (geographic separation, different industries, the mark's limited public profile at the time); the absence of any offer to sell the domain to the complainant or at an inflated price; and evidence of active, consistent use inconsistent with the passive-holding or confusion-exploitation patterns that panels treat as bad faith.

Declarations or affidavits from the registrant explaining the purpose of registration are accepted by most panels and can be decisive in close cases. They must be truthful, specific, and consistent with the documentary record. Panels are experienced at identifying post-hoc narratives constructed to fit the defense; the declaration should explain the actual reason for registration at the time, not the most legally convenient one.

For .pl domains specifically, Polish-language business records are admissible and can be filed with the response. Where the record is in Polish, a certified or accurate translation should accompany it. Panels handling disputes about Polish-market domains are accustomed to reviewing evidence in European languages, but translations reduce ambiguity and the risk of a panel drawing incorrect inferences from untranslated documents.

In another matter we handled – a .com dispute touching a Polish e-commerce operator, summer 2024 – the panel turned on a single piece of evidence: a Polish business registry extract showing the registrant had operated under the disputed name as a legal entity for approximately six years before the complaint was filed. Without that extract, the panel would have faced an evidentiary gap on the legitimate-interest element. With it, the denial was straightforward.

How Does the Choice Between UDRP Forums Affect a .pl Respondent?

Where the UDRP does govern your dispute – because the domain at issue is a gTLD running alongside the .pl, or because the registrar contract incorporates the Policy – the complainant chooses the forum. You do not. The complainant may file at WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC. Each forum applies the same Policy and Rules, but administrative features differ.

One feature that does affect respondents directly: the panel composition. A single-member panel is the default. If you believe a three-member panel gives you a materially better chance – because the facts are complex, the legal issues are novel, or the complainant is a sophisticated repeat filer with resources – you may request a three-member panel as the respondent. The cost is shared: the parties generally split the higher three-member fee. At WIPO, that means a total panel fee of USD 4,000 for a standard single-domain case, divided between the parties after the complainant's single-member filing fee is offset.

The right route depends on the circumstances. If the domain is solely a .pl and the complainant has filed in a Polish court or initiated a NASK dispute, the UDRP forum choice is irrelevant; the national procedure governs, and you need to respond in that system within its own deadlines. If the complainant holds a parallel .com and has filed both a UDRP complaint (for the .com) and a national-law claim (for the .pl), you may be managing two simultaneous proceedings with different deadlines, different evidentiary standards, and different remedies available to the other side.

That dual-track situation is where the risk of a tactical mis-step is highest. A statement made in the UDRP response can be used in the national-court proceedings, and vice versa. Coordination between the two filings – or at minimum, awareness of the risk – is essential. Where court proceedings in Poland require local litigation counsel, we work alongside counsel in the relevant jurisdiction to ensure the two filings are consistent and strategically aligned.

For respondents who only face the UDRP (because the .pl is not in dispute or the registrar contract creates UDRP jurisdiction), the forum selection by the complainant is a fixed parameter. What you can control is the panel composition request and the quality of the record you build in the 20-day response window.

What Are the Most Common Mistakes Respondents Make?

Default is the single most costly mistake. A respondent who does not file within the deadline does not lose the ability to argue the merits – the panel still applies the Policy – but in practice, panels that receive no response rarely deny a facially adequate complaint. The evidentiary record consists entirely of what the complainant submitted, and the panel draws reasonable inferences from it. Default is not a neutral act.

The second common error is addressing only the bad-faith element while conceding the legitimate-interest element by silence. Respondents sometimes assume that if they can show good faith, the complaint fails. Technically, the complainant must prove all three elements – but panels frequently find that a respondent who fails to come forward with evidence of legitimate interest has not rebutted the complainant's prima facie showing. Address all three elements, even if briefly, on all three.

Third: submitting an unorganized evidentiary packet without connecting each exhibit to the element it supports. Panels work through a structured legal analysis. A response that presents twenty exhibits without explaining which one supports which element of the defense forces the panel to do that work, and some panels simply will not. Label exhibits, connect them to the element, and state the inference you want the panel to draw.

Fourth: misunderstanding the myth that registering a domain in a jurisdiction where the complainant has no trademark registration is an automatic defense. Panels under the UDRP assess trademark rights broadly; a well-known mark may be recognized even without a Polish registration. The complainant's trademark registration in its home jurisdiction can suffice for element one. Do not assume geographic distance from the complainant's home market protects you.

Fifth: treating the response as purely defensive when the facts support an RDNH counter-argument. If the complaint is opportunistic, say so, with evidence. A panel that denies the complaint without an RDNH finding is still a win for you – but an RDNH finding also deters the same complainant from repeat filings against legitimate registrants.

Related at COGNOMEN

• UDRP and ccTLD respondent defense, RDNH findings, and domain protection across all zones
• Defending a domain on fair-use grounds in .eu and European ccTLD proceedings
• Recovering .eu domains from serial cybersquatters – complainant strategy and forum choice