Step-by-step: seek a reverse domain name hijacking finding for a .pl…

Step-by-step: seek a reverse domain name hijacking finding for a .pl. UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your case.

A brand owner files a complaint claiming your .pl domain. The complaint is thin — the trademark post-dates your registration, the evidence of bad faith is weak, and the filing looks like a pressure tactic designed to pry a valuable name away from a legitimate registrant. You want more than a dismissal. You want the panel to call it what it is: reverse domain name hijacking.

Reverse domain name hijacking (RDNH) is a formal finding that a complainant brought a proceeding in bad faith to deprive a legitimate registrant of a domain. For a .pl domain, no UDRP applies directly — disputes travel through the Polish courts or NASK's own procedure — but where the proceeding is filed before WIPO or another accredited provider under a UDRP-adjacent rule, the panel has authority under the Rules to issue an RDNH finding. The finding carries no monetary penalty, but it creates a durable public record of complainant abuse.

This guide walks each step a registrant should take to build the record, meet the safe harbors, and position the file for an RDNH outcome — and flags the trap hiding in each one.

What governs a .pl domain dispute — and where does RDNH fit?

The .pl zone is administered by NASK (Naukowa i Akademicka Sieć Komputerowa), Poland's national registry, under Polish law. NASK does not operate a UDRP-style arbitration procedure. The standard route for a disputed .pl domain is civil litigation before the Polish courts, applying the applicable Polish trademark and unfair competition statutes by branch reference — not UDRP arbitration.

That means a complainant who wishes to pursue a UDRP-style complaint against a .pl registrant must use WIPO or another provider only if the registrant agreement or a separate submission to jurisdiction allows it. In practice, most .pl disputes that reach a UDRP provider do so because the complainant has filed under the Policy against a registrant who holds both a .pl and a gTLD, or because the parties have separately consented. Where the proceeding runs under the UDRP, the UDRP's own supplemental rules govern, and Paragraph 15(e) of the Rules — the RDNH provision — applies in full.

The trap at this step: registrants sometimes assume that because .pl is outside the ordinary UDRP, no RDNH finding is possible. That assumption is wrong wherever the proceeding has been accepted and commenced by an accredited provider. Confirm the procedural basis of the complaint before deciding how to respond.

Where the dispute is in the Polish courts rather than a UDRP forum, an RDNH finding as such is not available — but a successful defense can support a counterclaim for litigation costs and, in some circumstances, an unfair competition claim against the complainant. That court-side strategy is handled with local litigation counsel in the relevant jurisdiction and is addressed later in this guide.

How realistic is an RDNH finding — and when do panels grant one?

Panels grant RDNH findings in a distinct minority of cases, and always for a specific reason: the complaint was brought in bad faith, or the complainant knew — or clearly should have known — it could not prevail. RDNH is not a consolation prize for a failed complaint. A complainant who made a reasonable argument in good faith will not draw an RDNH finding even if the complaint is dismissed.

The fact patterns that consistently produce RDNH findings include: a complainant whose trademark registration post-dates the respondent's domain registration by a material margin; a complainant who misrepresented its rights in the complaint; a complainant who used the filing as a tactical pressure tool rather than a genuine rights-enforcement action; and a complainant who could not possibly have satisfied the bad-faith element because the domain was registered before the mark existed. Any one of those patterns, if documented, materially strengthens an RDNH argument.

In our practice, we have seen RDNH petitions fail because the respondent asked for the finding without demonstrating specifically why the complainant knew or should have known it would lose. The ask must be grounded. Generic language — "this complaint is abusive" — does not move a panel. A concise, fact-specific argument pointing to the fatal weakness the complainant must have recognized does.

Step 1 — Audit the complaint immediately and map the weaknesses

The 20-day response window begins on the day the proceeding formally commences. That is the registrant's entire pre-decision timeline. Spend the first two days on a structured audit of the complaint, not drafting a response.

Map three things in sequence. First, identify the complainant's trademark: when was it applied for, when registered, and in which jurisdiction? Compare that date against the date the .pl domain was created. If the trademark post-dates the domain, the bad-faith limb of Paragraph 4(a)(iii) — which requires the domain to have been registered in bad faith — fails on its face, because a registrant cannot have targeted a mark that did not exist. That is the clearest RDNH predicate.

Second, read the complaint's bad-faith allegations carefully. Does the complaint contain factual assertions about your conduct that are incorrect, exaggerated, or unsupported by the evidence annexed? Misrepresentation in a complaint is a separate RDNH ground, independent of the trademark-date issue.

Third, check whether the complainant attempted any contact before filing — an offer to purchase, a cease-and-desist letter, or a trademark demand. A complainant who filed without any prior contact and whose mark is weak may signal a tactical filing rather than a genuine rights dispute.

The trap here: registrants focus on rebutting the three UDRP elements and forget to record the RDNH argument as a separate section of the response. Panels treat RDNH as a distinct question. It must be raised explicitly and argued with its own evidence.

Step 2 — Build the Paragraph 4(c) legitimate-interest record

To secure an RDNH finding you must first defeat the complaint. That means satisfying at least one of the three safe harbors in Paragraph 4(c) of the Policy. Winning on legitimate interest is typically the clearest path, because it does not require disproving bad faith — it shifts the burden back to the complainant once a credible showing is made.

The three safe harbors are: a bona fide offering of goods or services before any notice of the dispute; being commonly known by the domain name; and legitimate noncommercial or fair use without intent to mislead for commercial gain. For a registrant of a .pl domain, the most commonly applicable harbor is the first — a genuine business use or demonstrable preparation for use that predates the complainant's notice.

What does that record look like in practice? It includes dated business registration documents, invoices, screenshots of the website as it operated before the complaint, email correspondence showing commercial use, and any trademark filings of your own. Where the domain was registered as a personal name, a geographic term, or a descriptive phrase, collect evidence that third parties have used the same phrase independently — that corroborates the argument that the name was not selected because of the complainant's mark.

The trap at this step: registrants often produce evidence of current use without documenting the timeline. A panel evaluating legitimate interest looks backward from the date of the complaint. Evidence that the site went live after the complaint was filed carries almost no weight. Assemble your chronological record before drafting a single paragraph of the response.

We regularly advise registrants who registered a domain years before a brand owner's trademark application. In those matters, the registration date — confirmed by the WHOIS/RDDS record and corroborated with the original registration email — is itself the core of the legitimate-interest argument. For a .pl domain, NASK's registration history records can be obtained and should be annexed to the response.

Step 3 — Draft the response: structure, sequence, and the RDNH section

A well-structured response addresses the three UDRP elements in order and then contains a discrete RDNH section at the end. Do not bury the RDNH argument inside the bad-faith rebuttal. Panels read hundreds of responses; a clearly labeled section is more likely to receive focused analysis.

The RDNH section should open with a one-sentence statement of the standard — that an RDNH finding requires the complainant to have brought the proceeding in bad faith or knowing it could not prevail. It should then identify, by specific reference to the complaint, the one or two facts that make this complaint fall within that standard. Brevity is a feature, not a weakness. A five-paragraph RDNH argument grounded in two concrete facts outperforms a ten-paragraph argument that reads like a general grievance.

For the broader response, the sequence matters. Confusing similarity is typically conceded where the domain and the mark are facially similar — do not waste space disputing it unless the similarity is genuinely arguable. Allocate the word budget to legitimate interest and bad faith, where the real contest is. And state the RDNH argument as a request, not a hope: "The Respondent respectfully requests that the Panel issue a finding of reverse domain name hijacking."

For an assessment of how these elements apply to your specific .pl domain dispute, contact info@cognomenlaw.com.

To weigh UDRP against a court action for your .pl dispute, email info@cognomenlaw.com.

What evidence actually decides an RDNH outcome?

Evidence for an RDNH finding is evidence about the complainant's knowledge and conduct, not just about your own legitimate use. The two tracks of evidence must be developed in parallel.

On the complainant's side, the most powerful evidence is the trademark registration date. If a WHOIS or registry record shows your .pl domain was created before the complainant's trademark filing — and that gap is clear on the face of the record — a panel has everything it needs to find that the complainant knew the registration-in-bad-faith element could not be satisfied. Annex a screenshot of the trademark certificate showing the application and registration dates. Annex the NASK registration record showing the domain creation date. The juxtaposition is the argument.

Where the timing is closer, or where the complainant's trademark is much older than the domain, RDNH is harder to sustain. In those cases, the stronger argument is typically misrepresentation: identify specific statements in the complaint that are factually wrong and support each correction with a documentary exhibit. A complainant who said "the Respondent has no known use for this domain" when the website has operated for years has made a misrepresentation — and that misrepresentation, documented with a Wayback Machine archive or a server log, supports an RDNH claim independent of the trademark-date issue.

In a recent matter — a .pl-adjacent dispute, spring 2025 — we assembled a response demonstrating that the complainant's trademark had been filed approximately eighteen months after our client's domain registration. The panel dismissed the complaint and issued an RDNH finding, noting specifically that the complainant must have been aware that the bad-faith element could not be established given the sequence of dates. The decisive exhibits were two: the NASK domain history record and a certified copy of the complainant's trademark certificate.

The trap at this step: registrants sometimes produce the evidence but fail to connect it to the RDNH standard in the text of the response. An exhibit does not argue for itself. Each piece of evidence must be referenced in the body of the response with an explicit statement of what it proves about the complainant's knowledge or conduct.

Step 4 — Handle the .pl court dimension: when RDNH ends and litigation begins

If the complaint was filed in the Polish courts rather than before a UDRP provider — or if the UDRP proceeding has been decided and the complainant refuses to accept the outcome and pursues Polish civil litigation — the RDNH concept does not translate directly. Polish courts apply Polish trademark law and unfair competition statutes by branch reference, without the UDRP's four-element structure.

That does not leave a legitimate registrant without options. A successful defense in Polish proceedings can support a claim for procedural costs. Where the complainant's litigation was brought without adequate basis and caused demonstrable harm — including the cost of a defense, reputational damage, or lost business opportunities during a registrar lock — a counterclaim under the applicable Polish unfair competition provisions may be available. That analysis requires local litigation counsel in the relevant jurisdiction.

What the UDRP proceeding produces, if it results in an RDNH finding, is a public record at the provider's database — searchable by WIPO or the Forum's case tracking system — that the complainant's prior filing was abusive. That record can be introduced in Polish civil proceedings as evidence of the complainant's pattern of conduct. It does not bind the Polish court, but it carries persuasive weight. File the UDRP decision as an exhibit if litigation follows.

The decision matrix is straightforward: if the .pl domain is the only domain in dispute and the proceeding is in a Polish court, seek RDNH-equivalent relief through the court's own cost and counterclaim mechanisms, with local counsel. If there is a parallel .com or other gTLD involved, pursue RDNH through the UDRP proceeding while coordinating the Polish defense separately. The two proceedings run on different clocks and under different rules; they must be managed in parallel without allowing either to prejudice the other.

Step 5 — After the decision: using an RDNH finding strategically

An RDNH finding is published in the provider's online database. WIPO's case search is publicly accessible and indexed by search engines. That visibility is the sanction — there is no monetary award — and it is a meaningful one for a repeat complainant or a publicly traded brand owner.

Once a finding is issued, preserve it. Download the full decision text and the panel's reasoning. If the complainant subsequently files another complaint against a related domain, the prior RDNH finding is directly relevant: panels have consistently held that a prior RDNH finding weighs against a complainant in a subsequent proceeding, particularly where the same registrant and the same mark are involved.

If the complainant then shifts to Polish civil litigation, the RDNH decision and the response submissions constitute a fully developed factual record that local litigation counsel can use in the Polish proceedings. The work done for the UDRP defense is not wasted — it is the foundation of the court defense.

Consider also whether to monitor the complainant's trademark portfolio after the decision. A complainant who filed a pre-trademark complaint may file again once a mark is obtained. Domain name dispute defense and monitoring can be structured to catch a repeat filing before the 20-day response window becomes a crisis.

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

Handling the myth: "RDNH findings are almost never granted, so it's not worth asking"

This is the objection we encounter most often. It is partly accurate and mostly wrong. RDNH findings are not common — panels do not grant them as a matter of course, and a bare request without argument will be ignored. But the category of cases where RDNH is realistic — complaints filed against registrants who predated the trademark, complaints containing factual misrepresentations, complaints brought as tactical leverage without a genuine rights basis — is not a narrow one.

More importantly, the cost of raising the argument is low. The RDNH section of a well-drafted response adds little additional work if the legitimate-interest record and the trademark-date analysis are already assembled. A registrant who defeats a complaint and gets an RDNH finding has turned a defensive proceeding into a reputational sanction against the complainant. That outcome is worth seeking wherever the predicate facts exist.

The caution is proportionality. Raising RDNH in a case where the complainant had a reasonable argument — even one that ultimately fails — risks undermining the credibility of the response overall. Assess the RDNH predicate with the same rigor as the substantive defense. If the facts support it, make the argument. If they do not, do not manufacture one.

See also our analysis of the related question of what happens when a domain was registered before a trademark application was filed — a recurring predicate for both the legitimate-interest defense and the RDNH argument.

Related at COGNOMEN

• Respondent defense and RDNH: keep a domain and seek a hijacking finding
• FAQ: domain registered before a trademark application — what are your rights?
• URS and new-gTLD claims notices: suspension and defense options