How to prove a legitimate interest in your .pl domain

How to prove a legitimate interest in your .pl domain. UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your case.

A brand owner files a complaint against your .pl domain. The letter arrives – or perhaps a notice from the Polish court – and suddenly a name you registered in good faith is in dispute. Your first question is whether you can keep it. The answer turns almost entirely on one thing: whether you can prove a legitimate interest in your .pl domain before the proceeding concludes.

Proving a legitimate interest in a .pl domain is a threshold defense. Unlike .com disputes under the UDRP, .pl disputes are governed by Polish courts and the general rules of Polish civil and unfair-competition law – there is no single UDRP-style administrative procedure for .pl as of the date of this page. The complainant must establish that your registration harms a right it holds; you answer by documenting that your use of the name predates the dispute, serves a genuine purpose, and was not designed to exploit the complainant's mark. Building that record early is what determines the outcome.

This page explains the .pl dispute environment, the categories of legitimate interest a respondent can assert, the evidence that decides the issue, and the realistic next steps for a registrant facing a demand.

What Governs .pl Domain Disputes?

.pl is administered by NASK, Poland's national research and academic network, and the registry does not operate a UDRP-type administrative panel procedure. Disputes over .pl domains are resolved primarily through Polish civil courts, with the complainant typically relying on trademark law, unfair competition rules, or the specific provisions of Polish law concerning the protection of registered rights in the online environment.

This is a materially different environment from a .com dispute at WIPO or the Forum. There is no 20-day response clock, no panel appointment in a matter of weeks, and no fixed filing fee to a dispute-resolution provider. Instead, the complainant files a civil claim – often with an interim injunction application – and the proceedings run on the schedule of the court's docket. That timeline is typically measured in months, not in the two-month arc of a standard UDRP case.

Because .pl disputes reach a court rather than an administrative panel, the substantive standard is different too. A court assessing your .pl registration looks at Polish law as a whole: whether you registered the domain in bad faith, whether you are using it to cause consumer confusion, whether you are targeting the complainant's rights, and critically – whether you had a legitimate basis for the registration that predates or independently of the complainant's mark.

For registrants who also hold .com or other gTLD versions of the same name, a parallel UDRP complaint is possible. In that situation, we manage both the Polish-law track and the UDRP defense simultaneously, identifying the strongest legitimate-interest arguments across both proceedings.

If you have received a complaint or a formal demand about your .pl domain, the time to build your record is now – not after interim relief is granted. For an assessment of your domain dispute, contact info@cognomenlaw.com.

How Do You Prove a Legitimate Interest in Your .pl Domain?

A legitimate interest in a domain name rests on demonstrating that your registration and use of the name has an independent, genuine justification – one that does not depend on riding the complainant's reputation. Under the UDRP's Paragraph 4(c) safe harbors (relevant when a parallel gTLD complaint is in play, and widely treated as a useful analytical benchmark in ccTLD disputes), three recognized categories exist.

The first is a bona fide offering of goods or services before notice of the dispute. If you were operating a real business, a genuine service, or a functioning website under the domain name before any demand letter arrived, that prior use is the foundation of your defense. Courts and panels consistently treat demonstrable commercial activity – invoices, contracts, traffic records, archived pages – as strong evidence of legitimate interest.

The second is being commonly known by the domain name. This applies to personal names, trade names, and any designator by which you were genuinely identified before the domain was registered. If your registered business name, your trading name, or your personal name corresponds to the disputed domain, documentary evidence of that identification – business filings, invoices, articles, social media history – anchors the claim.

The third is legitimate noncommercial or fair use. Commentary sites, criticism pages, fan sites, and informational resources can qualify – provided they do not mislead users as to affiliation with the complainant and are genuinely noncommercial in character.

In the .pl context, the Polish court will look at the substance behind each of these, not merely the assertion. A registrant who can point to a continuous, documented history of use has a materially stronger position than one relying on bare registration alone.

Consider a recent matter we handled: in spring 2025, a Polish e-commerce operator held a .pl domain incorporating a generic Polish word for a category of household goods. A foreign brand owner with a registered EU trademark on a phonetically similar term filed a civil claim seeking transfer. The registrant had operated under that trading name since registration, with verifiable invoices and a registered business in Poland using the same term. We assembled the full commercial record, filed it with the court, and the interim injunction application was defeated at the first hearing. The substantive claim remained pending, but the registrant's operations continued uninterrupted.

What Evidence Builds the Strongest Legitimate-Interest Record?

Evidence is not optional in a .pl domain dispute. It is the argument. A registrant who asserts legitimate interest but cannot document it is in a far weaker position than one who arrives in court with a structured, chronologically ordered record.

The most persuasive evidence falls into four categories.

First, temporal evidence: anything that establishes when you began using the name and what you were doing under it. Domain registration records (WHOIS history), archived website screenshots, business registration certificates, invoices, and correspondence all establish a timeline. The earlier the documented use predates the complainant's demand, the stronger the position.

Second, commercial or operational evidence: invoices, supplier agreements, client lists (even anonymized), bank statements referencing the trading name, tax filings in the name of the relevant entity, and marketing materials bearing the domain. These demonstrate that the domain served a real economic function.

Third, identification evidence: anything showing that you, your business, or your organization were genuinely known by the name. Company registration documents, trade-name certificates, trademarks or trademark applications in Poland or the EU that you hold, press coverage, and industry directories all contribute.

Fourth, non-targeting evidence: demonstrating that you were not aware of the complainant's mark when you registered, that the domain was not acquired with the intention of exploiting that mark, and that you made no direct approach to the complainant to sell. Absence of targeting does not automatically establish legitimate interest, but the Polish court will consider it when assessing good faith.

In our practice, we regularly advise registrants who arrive without a complete record. The work is then to reconstruct what exists – archive records, business filings, bank correspondence – and present it in a form the court can assess quickly. Gaps in the record are manageable; the absence of any record is not.

When Does a Complaint Against Your .pl Domain Amount to Reverse Domain Name Hijacking?

Reverse Domain Name Hijacking (RDNH) is the label applied when a complainant uses a dispute procedure abusively – not to vindicate a genuine rights conflict, but to extract a domain from a legitimate holder who has a clear prior claim. RDNH findings are most commonly made in UDRP proceedings, where a panel may declare the complaint brought in bad faith. In the .pl court context, the equivalent concept operates differently: a court that dismisses the claim may award costs, and a particularly abusive enforcement campaign could raise issues under Polish unfair competition law.

RDNH is most realistic in the .pl environment where the complainant's trademark post-dates the domain registration, where the domain consists of a generic or descriptive term that the complainant does not own exclusively, or where the complainant's real motive is price leverage rather than rights protection. We have defended matters where the demand letter itself – offering a settlement on terms that would require the registrant to transfer the domain for nominal compensation – revealed the commercial, not rights-based, purpose of the complaint.

If a parallel UDRP complaint is filed (for a .com or other gTLD version of the same name), an RDNH finding before a WIPO or Forum panel is a reputational consequence for the complainant, though it carries no monetary penalty. In the .pl court track, cost consequences may follow. The key question is always whether the complainant's rights are genuinely at stake – or whether the complaint is instrumentalized to acquire a name it could not otherwise buy.

If the complaint against your .pl domain appears to target a name you registered and use in good faith, we can assess whether an RDNH defense or a costs argument is realistic. Email info@cognomenlaw.com to discuss your situation.

How Does the .pl Route Compare to UDRP and Other ccTLD Procedures?

Understanding where .pl sits relative to other zones helps a registrant facing a multi-domain demand make the right strategic decisions.

If the domain in dispute is a .com, the complainant can file a UDRP complaint at WIPO (filing fee starting at USD 1,500 for a single-member panel) and receive a decision within roughly two months. The registrant has 20 days to respond once the case commences. The only remedies are transfer or cancellation – no damages. The UDRP is a constrained, fast-moving procedure, and a legitimate-interest argument under Paragraph 4(c) is the primary defense.

For .uk domains, Nominet's DRS applies. It is notable for a free mediation stage before any expert decision, and the substantive test – "abusive registration" – reads "registered OR used" abusively, a lower bar for the complainant than the UDRP's cumulative "registered AND used." The registrant's legitimate interest defense must therefore address both the registration moment and the ongoing use.

For .de, there is no administrative procedure at all. Disputes go to the German courts, with DENIC offering a DISPUTE entry to block transfers during litigation. The .pl environment resembles this model closely: court-based, civil-law governed, without a dedicated administrative panel.

For .eu domains, the ADR.eu procedure at the Czech Arbitration Court applies. The complainant must demonstrate EU-nexus eligibility, and the remedies include transfer or revocation. An EU trademark that the complainant holds may be asserted in a .eu complaint while a .pl court action runs separately – which means a registrant holding both a .pl and a .eu version of the same name may face two different proceedings on two different timelines simultaneously.

The practical consequence: if a brand owner is serious about recovery, it will often file across all zones simultaneously, hoping that a faster procedure (UDRP for .com, .eu ADR) produces an early result that it then uses as leverage in the slower Polish court track. A registrant's defense must anticipate that multi-front pressure.

What Are the Common Weaknesses That Lose a Legitimate-Interest Defense?

A legitimate-interest defense fails when the registrant cannot demonstrate that the claimed interest existed before notice of the dispute, is genuine, and is independent of the complainant's mark. In our experience of respondent-side work, the same categories of weakness appear repeatedly.

First, post-notice activity: a registrant who builds out the website, registers a trade name, or generates invoices only after receiving the demand letter will find that the court discounts or disregards that evidence. Temporal credibility is everything; activity created to litigate is treated as exactly that.

Second, generic claims without documentation: asserting that the domain is a "common word" or "descriptive term" is insufficient without showing what you were actually doing under it. A domain that resolved to a parking page for years, then suddenly gained content after a dispute began, is a difficult defense to run.

Third, inconsistent identification: if the registrant's business, trading name, or personal identification does not match the domain in any verifiable record, the "commonly known" argument is undermined. Courts look for external corroboration, not self-assertion.

Fourth, prior dealings with the complainant: if the registrant previously contacted the complainant offering to sell the domain – or responded to an acquisition inquiry with a price substantially above the cost of registration – that conduct is powerful evidence against legitimate interest and in favor of bad faith. In our practice, we have reviewed correspondence produced in discovery that effectively ended an otherwise viable defense.

Recognizing these weaknesses before the proceeding is filed is how we help registrants assess whether a defense is realistic, and how to structure the record to address the vulnerabilities that exist.

What Is the Realistic Outcome and Next Step?

A well-documented legitimate-interest defense in a .pl domain dispute can defeat a civil claim outright, prevent interim relief, and in the right circumstances support a cost award against an abusive complainant. These outcomes depend entirely on the facts – the strength of your documentation, the timing of your use, the character of the complainant's rights, and the specific allegations made.

No honest assessment can predict a result before seeing the file. What we can tell you is what a thorough defense looks like: mapping the complainant's trademark record against your registration date and use history, identifying every category of legitimate interest that applies to your situation, assembling the documentary record in a form a Polish court expects, and positioning any RDNH arguments where the facts support them.

In a matter from winter 2025, a registrant holding a .pl domain built around an acronym used by his consultancy firm for over a decade received a demand from a multinational corporation that had registered a trademark incorporating the same letters in a different sector. We prepared a complete chronological record – business filings, client invoices, archived site captures, and marketing materials – demonstrating continuous use predating the trademark application. The demand was withdrawn without further proceedings.

The decision now is whether to assess your position before proceedings deepen, or to wait and see what the complainant files. In our practice, the registrants who wait consistently find themselves with less time, a shorter evidentiary window, and a court timeline that does not accommodate a slow response.

Related at COGNOMEN

• Respondent defense and RDNH across all zones and forums
• Defending a generic domain name in .sg and Asian ccTLD proceedings
• Recovering a hijacked domain in EU-zone proceedings