Step-by-step: enforce a UDRP decision a registrar will not im… (.pl 2)

Step-by-step: enforce a UDRP decision a registrar will not im… (.pl 2). UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your ca…

A WIPO panel has ruled in your favor. The decision sits on paper. And the registrar responsible for the .pl domain has not moved. No lock release, no transfer, no acknowledgment — just silence or a technical objection that keeps the name out of your hands. What happens next?

To enforce a UDRP decision a registrar will not implement for a .pl domain, the winning complainant must understand that .pl is a country-code extension administered by NASK (the Polish research and academic network), and that standard UDRP mechanics do not bind NASK or Polish-accredited registrars the way they bind gTLD registrars. When a registrar stalls, the practical route is a combination of formal escalation to NASK, a direct demand under the registrar's own implementation obligations, and — where those channels fail — civil court proceedings in the relevant Polish jurisdiction. The process is fact-intensive and time-sensitive; delay can harden the registrant's position or allow a transfer to a third party.

This guide walks each step in sequence, identifies the trap concealed in each one, and explains where the court route pulls ahead of further arbitration for .pl enforcement.

Why Does a UDRP Decision Fail to Transfer a .pl Domain?

A UDRP decision issued by WIPO or the Forum is not a self-executing court judgment — and that distinction is especially sharp for .pl. The UDRP binds registrars only insofar as they have contractually agreed to implement decisions, and that agreement runs through ICANN accreditation. NASK accredits .pl registrars under its own regime, which does not automatically incorporate ICANN's implementation obligations in full.

In practice, implementation failures occur for several distinct reasons. The registrar may dispute whether the UDRP even applies to a .pl registration — a defensible technical position where the registrar is accredited solely by NASK, not by ICANN. Alternatively, the registrar may assert that the domain is subject to a pending legal hold, a domestic dispute flag, or a third-party claim that it cannot resolve without a court order. In other cases — rare but documented in our practice — the registrar has lost contact with the registrant and faces a procedural deadlock under its own terms.

Each reason requires a different first move. Treating them all as simple foot-dragging is the first trap.

Step 1: Audit the Decision and the Registrar's Obligations Before Acting

Before contacting anyone, read the UDRP decision carefully alongside the registrar's published dispute policy, NASK's domain name regulations, and the registration agreement. The trap at this step is acting on assumption: many complainants assume that quoting the UDRP decision number to the registrar is enough. It is not, where the registrar's obligation to implement runs through a separate contractual chain.

Confirm three things. First, verify whether the registrar is ICANN-accredited, NASK-accredited, or both. An ICANN-accredited registrar that also manages .pl domains under a NASK registry agreement is in a different position than a purely NASK-accredited local registrar. Second, confirm that the decision explicitly orders transfer rather than cancellation — the remedy affects how NASK processes the request. Third, establish whether the standard 10-business-day implementation window has already run from the date the decision was communicated to the registrar; if it has, the registrar is already in a state of non-compliance under the Policy, which strengthens a formal escalation letter.

In a recent matter involving a .pl domain (spring 2025), we found that the registrar had never received a conforming implementation request — the complainant had sent the decision to a general support inbox rather than the designated abuse or legal contact. Correcting that single step resolved the implementation within days. Not all cases are that simple. But the audit saves time before escalation.

Step 2: Send a Formal Implementation Demand to the Registrar

Once the audit is complete, send a formal written demand — not a support ticket — to the registrar's legal or abuse contact, citing the WIPO or Forum case reference, the specific operative paragraph of the decision ordering transfer, and the registrar's contractual obligation to implement. Give a short, defined deadline: five business days is reasonable. Send it by a method that creates a timestamp — email with read receipt, or courier to the registered office.

The trap here is failing to create a paper trail that will serve as evidence if the matter proceeds to court. A vague "please action the decision" email does not demonstrate reasonable demand. A properly structured letter that identifies the decision, the obligation, the deadline, and the consequence of non-compliance does.

If the registrar responds with a technical objection — a NASK lock, a third-party claim, a pending domestic dispute — you now have their position in writing. That matters. Their stated reason determines whether the next step is a NASK escalation, a direct approach to the registrant, or a filing in the Polish courts.

Step 3: Escalate to NASK Directly

NASK, as the .pl registry operator, maintains its own dispute-related procedures and has the technical ability to override a stalled registrar in defined circumstances. An escalation to NASK is not an appeal of the UDRP decision — it is an administrative request asking the registry to recognize the decision and effect a direct registry-level transfer or lock.

This step is underused by complainants who assume NASK is a passive back-end operator. It is not. NASK can place a registry-level lock on the domain to prevent any further transfers while the dispute is resolved, which is critical if you suspect the registrant is preparing to move the domain to another registrar or sell it to a third party. Registry-level locks are the most effective tool against a domain that is in flight.

The trap: NASK operates under Polish administrative and civil law. A request in English, without a Polish-language summary and reference to the governing NASK regulations, will move slowly. Use Polish-language correspondence or engage counsel who can produce it. The NASK escalation is also not indefinite — if the registry's internal position is that a court order is required to override the registrar's hold, they will say so promptly, and that answer sets the timeline for Step 5.

If you are at the escalation stage and are unsure whether a NASK request or a court filing is the more efficient path, contact COGNOMEN at info@cognomenlaw.com. We assess the registrar's position, the NASK response, and the merits of a Polish court route — and can tell you which step fits your facts.

Step 4: Assess Whether the Court Route Has Already Become Necessary

For most .pl enforcement failures that persist past Step 3, the answer is yes: a court route has already become necessary. Polish civil courts have jurisdiction over domain-name disputes involving Polish registrants or Polish-accredited registrars, and a court order is the one instrument that both the registrar and NASK are legally obliged to follow without qualification.

When does the court route clearly beat further arbitration or administrative escalation? Four situations recur in our practice. First, the registrar has provided a written objection grounded in a NASK lock or a third-party claim that it asserts only a court can resolve. Second, the registrant has transferred or attempted to transfer the domain to a third party after the UDRP decision, and you need an interim injunction to freeze the name. Third, the delay has exceeded several months and further letters are producing no movement. Fourth, the value of the domain is sufficient to justify the additional cost and timeline of litigation.

The decision matrix here is practical. A UDRP complaint is typically resolved within about two months, with a WIPO filing fee starting at USD 1,500 for a single panel. A Polish court action runs considerably longer and costs more — the exact legal fee depends on complexity, and litigation costs should be assessed qualitatively as substantially higher than arbitration. The trade-off is that a court judgment carries enforcement power that a UDRP decision does not. If the registrar is ICANN-accredited, further leverage may exist through ICANN's registrar compliance channel, discussed at Step 5 below. If the registrar is purely NASK-accredited, the court is the primary enforcement lever.

A note on zone strategy: this situation differs from a pure .com enforcement failure. A .com registrar is ICANN-accredited and subject to ICANN registrar compliance escalation in a way that most NASK-only registrars are not. That asymmetry is precisely why .pl enforcement failures can be more resistant than gTLD failures, and why the court option arrives earlier in the decision tree.

Step 5: Use ICANN Registrar Compliance If the Registrar Is Dual-Accredited

Where the stalling registrar holds both an ICANN accreditation and a NASK registrar agreement, a formal complaint to ICANN's Registrar Compliance department creates external pressure that operates independently of Polish law. ICANN can require the registrar to respond, can escalate to a compliance notice, and in persistent cases can initiate proceedings that threaten the registrar's accreditation.

The trap at this step is timing. An ICANN compliance complaint filed too early — before a formal demand letter and a reasonable waiting period — will be returned with a note that the complainant has not exhausted direct channels. Filed at the right moment, after documented refusal or silence, it adds institutional pressure at minimal additional cost.

Keep the ICANN complaint factual and procedural: this registrar received a UDRP decision on this date, the implementation window has passed, the formal demand was made on this date, no response has been received. Do not reargue the merits of the underlying UDRP case — ICANN compliance does not review substantive panel decisions. Its role is limited to whether the registrar met its procedural obligations.

Step 6: Prepare and File a Civil Court Action in Poland

If escalation to NASK and ICANN compliance have not produced a transfer, or if the facts call for a court route from Step 4 onward, the next step is a civil action filed in the competent Polish court. COGNOMEN works with local litigation counsel in the relevant jurisdiction for all Polish court proceedings; this step is not a solo filing.

The court action for .pl enforcement typically combines two elements. The primary claim is enforcement of the UDRP decision and an order directing NASK and the registrar to effect the transfer. The secondary claim, where the facts support it, is a trademark infringement or unfair competition claim under the applicable national laws — giving the court multiple grounds to grant relief even if one theory encounters a procedural objection.

Evidence that is decisive at this stage: the certified UDRP decision with operative language; proof of service of the implementation demand on the registrar; the registrar's written response (or documented silence); any NASK correspondence; evidence of the complainant's trademark rights in Poland or the EU; and, critically, WHOIS or RDDS records showing the current registrant and any post-decision transfer activity. If the domain has been moved to a new registrant after the UDRP decision issued, the court action must join the new registrant and may need to seek an interim injunction at the outset to freeze the domain during proceedings.

In a late-2025 matter involving a Polish registrar and a .pl domain that had been transferred to a second registrant after the UDRP decision, we worked with local litigation counsel to obtain a registry-level freeze within weeks of filing, preventing further transfer while the main action was resolved. The underlying trademark was a registered EU mark, which simplified the Polish court's jurisdictional analysis considerably.

If a Polish court filing is the right next step, email info@cognomenlaw.com. We coordinate the cross-border evidence package, the local litigation counsel engagement, and the NASK technical steps in parallel — so no procedural window is missed while the litigation is pending.

What Evidence Decides the Outcome at Each Step?

The evidence required evolves as the process advances. At Steps 1–3, the critical documents are the UDRP decision itself, the implementation demand letter, and the registrar's response. These establish a clear failure-to-comply record. At Steps 4–6, the evidentiary requirements broaden substantially.

Polish courts will want to see the complainant's trademark rights clearly documented — a Polish or EU trademark registration is the cleanest basis. If you hold a foreign registration or rely on unregistered mark rights, the documentary record must be heavier: commercial evidence of use, advertising, consumer recognition, and the scope of protection. Generic mark arguments that were marginal at the UDRP stage become more exposed in civil litigation.

Post-decision conduct by the registrant or registrar is particularly valuable. Evidence that the domain was transferred, monetized, or rerouted after the UDRP decision can support a bad-faith inference and, in the right circumstances, grounds for interim relief. Chain-of-WHOIS records — showing the registration history and any post-decision changes — should be preserved promptly; RDDS data can be volatile and WHOIS records can change or be masked between the decision date and a court filing.

One consistent trap across all enforcement proceedings: complainants who win a UDRP case sometimes treat the decision as the end of the evidence-gathering obligation. It is not. Preserve WHOIS snapshots, registrar correspondence, and domain-use screenshots immediately after the decision issues — do not wait until the enforcement action requires them. By then, some may be unavailable.

What If the Registrant Has Already Moved the Domain to a Third Party?

Transfer of a domain after a UDRP decision issues is one of the most disruptive facts in enforcement proceedings, and it occurs more often than many complainants expect. The registrant, aware that the domain is subject to an implementation order, transfers it — to a related entity, a shell holder, or a genuine third-party buyer — before the lock is in place.

The UDRP itself provides no direct remedy against a post-decision transferee. The decision runs against the registrant of record at the time of filing; a new registrant is not automatically bound. This is a structural gap in the arbitration route and one of the core reasons why court proceedings, with their interim injunction power, are superior in high-value or high-speed situations.

In Polish court proceedings, interim relief — an order directing NASK to lock the domain pending the main action — is available where the applicant can show a credible substantive claim and a risk of harm if relief is not granted. The evidentiary bar for interim relief is lower than for final judgment, but the application must be made promptly and with supporting documentation ready at filing. Delay in seeking interim relief, once post-decision transfer activity is detected, is the single most common enforcement error we observe in cross-border domain cases.

For related guidance on reversing unauthorized transfers — including the evidence framework and registrar-escalation mechanics applicable across zones — see our case study on reversing an unauthorized domain transfer.

Related at COGNOMEN

• Court recovery and domain theft services — when arbitration cannot reach
• Reversing an unauthorized domain transfer: a cross-zone case study
• Defending a generic domain and pursuing an RDNH finding