How to escalate a registrar lock to secure a .pl domain

Your .pl domain stops resolving. You check the WHOIS record and find the registrant contact changed overnight. The registrar's standard support queue offers a ticket number and a five-day wait. Meanwhile, whoever controls the name can redirect your customers, harvest credentials, or flip the registration before a court order freezes it. Speed is the entire game here.

Escalating a registrar lock to secure a .pl domain means triggering an emergency administrative hold – through the registrar's abuse or legal team, and if that fails, through NASK (the .pl registry) or a Polish court interim injunction – that freezes the registration in place while the substantive dispute is resolved. There is no UDRP for .pl: the governing national procedure applies, and the route runs through Polish civil courts. Acting within hours to days, not weeks, determines whether the domain is still available to recover when relief is granted.

This page sets out the lock escalation sequence, the court route that follows, the evidence that drives the outcome, and how we structure engagements for .pl recovery.

Why .pl has no UDRP – and what that changes for registrar lock escalation

NASK, the Polish registry, has not adopted the UDRP or appointed WIPO as a dispute-resolution provider for .pl. That single fact reshapes the entire strategy. A brand owner who could file a WIPO complaint for the equivalent .com in about two months must instead work through Polish civil procedure, which moves on a different track and with different interim-relief mechanics.

The absence of a UDRP provider matters for the registrar-lock question specifically. Under the UDRP, a provider-issued lock automatically freezes the domain at commencement. For .pl, no such automatic mechanism exists. A lock must be obtained by direct escalation to the registrar, by a complaint to NASK's abuse channel, or – when those avenues fail or move too slowly – by a Polish court order that the registrar is directed to implement.

That distinction is not a disadvantage if the case is managed properly. Polish courts have jurisdiction over .pl registrations as a matter of domestic law. An interim injunction (zabezpieczenie roszczenia under the applicable civil procedural rules) can, in appropriate cases, be issued on an ex parte basis when delay would cause irreparable harm. Where the registration change is clearly unauthorized – an account compromise, a fraudulent transfer request, or a hijack by a bad-faith registrant – the factual record needed to support urgency is usually strong.

In our practice we see the failure mode clearly: a brand owner assumes that NASK will act on a generic complaint form the way a WIPO complaint triggers an automatic lock. It does not. The .pl path requires the registrar escalation and the court filing to run in parallel, not sequentially.

To assess the urgency of your .pl situation and the lock escalation options available, contact info@cognomenlaw.com.

What is a registrar lock, and when does escalation become necessary?

A registrar lock – also referred to as a registrar hold or a clientTransferProhibited status – is a flag placed on a domain record that prevents a transfer to another registrar or a change of registrant until the lock is lifted. Under normal operation, ICANN-accredited registrars place a standard lock on a domain during the 60-day post-registration and post-transfer periods. That default lock is a process guard, not a dispute guard. It expires, and it can be removed by the current registrant.

Escalation becomes necessary in four typical scenarios. First, the domain has already been transferred away fraudulently and the standard dispute period is running. Second, the registrant contact has been changed to an unauthorized party but the domain is still at the same registrar. Third, the registrar's standard abuse form has been submitted and no action has followed within a commercially acceptable window. Fourth, the party in possession is actively trying to push a secondary transfer to put the name further out of reach.

Each scenario calls for a slightly different escalation target. A fraudulent outbound transfer to another registrar brings ICANN's registrar-change rules into play. A registrant-contact change at the same registrar is an internal abuse matter. In both cases, for .pl, the escalation chain runs: registrar legal or abuse team → NASK registry → Polish court. The third step is not a last resort reserved for worst cases. Given NASK's published response windows, we often initiate the court preparation in parallel with the registry complaint, not after it.

How to escalate through the registrar and NASK before filing in court

The registrar is the first lever. Not the customer-support queue – the registrar's designated abuse or legal contacts, which ICANN-accredited registrars are required to maintain and publish. A formal written notice citing the unauthorized change, demanding an immediate lock, and reserving all legal rights creates the paper record the court will later want to see. It also starts a clock: if the registrar does not act within a defined period, that inaction is itself evidence supporting urgency before the Polish court.

The notice should identify the domain, the registrant-of-record immediately before the unauthorized change (supported by a timestamped WHOIS or RDDS capture), the nature of the compromise or fraud, and the specific lock status codes being requested (clientTransferProhibited and, where the registrant contact is at issue, clientUpdateProhibited). Vague notices produce vague responses. The registrar's legal team needs to understand, on first read, that this is a hijack not a billing dispute.

If the registrar does not lock within a matter of hours in a clear hijack situation, the next escalation is to NASK directly. NASK operates an abuse contact for .pl, and for clear cases of unauthorized transfer it can place a serverHold or a serverTransferProhibited at the registry level, overriding the registrar's status codes. A NASK-level lock is stronger: it cannot be lifted by the registrar without NASK's cooperation. In a recent matter (a .pl brand-matching domain, spring 2025) we obtained a NASK-level hold within 36 hours by providing a timestamped evidence package to NASK's technical-legal team alongside the registrar notice – allowing the court filing to proceed against a frozen target rather than a domain already in a third party's hands.

When does the Polish court route become the right path?

The court route is not the path of last resort – it is the structural path for .pl disputes, because the national procedure governs and no arbitration body can issue a binding transfer or injunction for this zone. The question is not whether to file in a Polish court but when and what relief to seek first.

An interim injunction (zabezpieczenie) is the right first-step court remedy when the registrar and NASK have not acted, or when the dispute goes beyond a simple account-compromise case into contested ownership or bad-faith registration. The Polish civil procedure allows the applicant to seek interim relief without full merits proceedings where it can show a credible right (fumus boni iuris) and a risk of irreparable harm if relief is delayed. A domain about to be transferred again satisfies that urgency standard in most circumstances.

The merits proceeding that follows determines ownership or the basis for a permanent transfer order. It may rest on trademark infringement under the applicable national trademark legislation, unfair competition law, or the civil-law claim to the name right (prawo do nazwy). In our practice we coordinate with local litigation counsel in the relevant Polish jurisdiction who handle the court filings directly; our role is to assemble the domain-specific evidence, structure the chain-of-title arguments, and manage the registrar and NASK side of the escalation in parallel.

Compare this to the .com path. For an equivalent domain dispute under the UDRP, WIPO's filing fee starts at USD 1,500 for a single-member panel, and a standard case resolves in about two months. No lock separate from WIPO's own commencement notice is needed. The .pl path involves no filing fee to a dispute provider – the costs are Polish court costs and legal fees – but the timeline depends on docket and procedural steps rather than the relatively predictable UDRP calendar. Neither path is universally faster; the nature of the dispute and the registrar's cooperation level usually determine which is quicker in practice.

What evidence decides whether you can secure the .pl domain?

The evidence package assembled in the first 24 hours will determine the outcome of both the registrar escalation and any subsequent court relief. This is where most self-represented attempts fail. What you present to NASK and to the Polish court must show a credible entitlement to the domain and a credible basis for saying the current registration status is unlawful.

For a hijack or account-compromise scenario, the core documents are: a complete WHOIS or RDDS history showing the prior registrant of record; authentication logs or account-access records from the registrar showing unauthorized access; any phishing or social-engineering communications that preceded the change; and evidence of the commercial relationship between the claimant and the domain (website archives, DNS records, invoice records, brand registrations).

For a bad-faith registration scenario – where the domain was registered by a third party in your brand name rather than stolen from an existing account – the evidence shifts to: the trademark registration or documented prior use underpinning your name rights; the timing of the domain registration relative to your brand's public emergence; the content or conduct of the current registration (parking pages, pay-per-click links, or ransom demands); and any prior communication with the registrant offering to sell.

Panels and courts that handle domain disputes consistently regard a five-figure buy-back demand from a registrant who registered the name shortly after a brand launch as strong circumstantial evidence of bad faith. That inference does not require the registrant to have explicitly stated a bad purpose; conduct speaks clearly enough.

What weakens the case? Delay. A claimant who knew of the unauthorized transfer for six weeks and took no documented action has a harder urgency argument before both NASK and a Polish court. The evidence package should also address any possible counterargument – in particular, whether the current registrant has any plausible legitimate interest in the name, because that is the first defense they will assert.

How does .pl compare to other ccTLDs – and when is a parallel .com action needed?

Many brand disputes do not live in a single zone. A registrant who targets a Polish brand often registers both the .pl and the .com, or the .pl and the .eu. Understanding how those parallel registrations interact with each other – and which route to prioritize – is part of the strategy.

For the .com, the UDRP applies. The three UDRP elements of Paragraph 4(a) must all be met: confusing similarity to a trademark, no legitimate interest, and registration and use in bad faith. A WIPO complaint commences with an automatic lock of the .com domain and resolves in about two months. That timeline can run in parallel with the .pl court proceedings, which may take longer.

For the .eu, the ADR.eu procedure administered by the Czech Arbitration Court applies. The complainant must have an EU/EEA nexus, and the remedy can include transfer where eligibility is met. In a case spanning .com, .eu, and .pl, we would typically file the UDRP and .eu ADR proceedings simultaneously – both of which produce automatic registry locks at commencement – while coordinating the Polish court interim-relief application to freeze the .pl registration on the same timeline.

For the .de (German zone), there is no UDRP and no WIPO appointment. Like .pl, it is a court-only jurisdiction, with a DENIC DISPUTE entry available to block transfer while litigation proceeds. A registrant holding both .pl and .de behind a corporate screen would require parallel court proceedings in two national jurisdictions, coordinated with local litigation counsel in each.

The choice of which zone to prioritize depends on where the harm is greatest and where the evidence is strongest. In our experience, a swift lock on the .com via UDRP commencement often removes the registrant's most commercially valuable asset fastest, which can accelerate settlement of the .pl and other zones without the full Polish court process running to judgment.

If your situation spans multiple zones – including a .pl alongside a .com or .eu – email info@cognomenlaw.com for an assessment of the parallel-filing strategy.

Transfer reversal mechanics: what happens after a lock is in place

Securing a lock stops further movement of the domain. It does not by itself restore the registration to the rightful owner. Transfer reversal is the next step, and the mechanics differ between the account-compromise path and the disputed-ownership path.

In an account-compromise case – where the domain was fraudulently moved from the legitimate registrant's account – most ICANN-accredited registrars operate a recovery window during which a documented fraudulent transfer can be reversed. That window is typically short. Presenting a verified fraud claim with authentication evidence during the window is the fastest path to physical restoration of the registration, without needing a court order to specify the transfer. The lock preserves the window by preventing secondary transfers while the reversal application is being assembled.

In a disputed-ownership or bad-faith-registration case, there is no automatic reversal window. The registrant of record is the current registrant until a court order or a registry-level decision says otherwise. Here the lock serves a different function: it preserves the domain in a static state while the Polish court proceedings establish the substantive right and issue an order directing the registrar or NASK to update the registration. That order is served on the registrar, who implements the transfer to the claimant.

In a second recent matter (a .pl typosquat of a Polish retail brand, autumn 2024), local litigation counsel secured an interim injunction within a matter of days, and the registrar implemented the serverTransferProhibited flag within 48 hours of receiving the court order. The merits proceeding ran for several months thereafter, but the domain was held static throughout – the commercial risk was contained from week one.

Cost structure: registrar escalation, NASK, and the court route

Cost transparency is a working principle at COGNOMEN. The .pl path does not involve a dispute-provider filing fee, but that does not make it cheaper than a UDRP proceeding overall. The costs distribute differently.

The registrar escalation and NASK complaint stages are primarily legal-drafting costs: a properly structured demand letter to the registrar's legal team, the evidence package, and the formal NASK submission. These are typically flat-fee work. The cost is modest relative to the risk of delay.

The Polish court interim-injunction application involves Polish court fees (which are set by the applicable procedural rules at a fixed or percentage rate), local litigation counsel fees for filing and attendance, and the translation costs if documents are in languages other than Polish. These are not trivial, but an interim injunction application is a far narrower document than full merits pleadings, and the cost is correspondingly lower than full litigation.

The merits proceeding – establishing ownership or trademark rights on a full evidentiary record – is a longer engagement, billed by local litigation counsel on an hourly or staged-flat-fee basis depending on the counsel retained. Our coordination role across the domain-specific components (evidence assembly, registrar communications, parallel zone filings) is agreed separately.

The relevant comparison is not "cost of .pl route vs. cost of UDRP." It is "cost of .pl route vs. cost of losing the domain." For a .pl that carries a brand, customer traffic, or e-commerce infrastructure, the commercial value of a swift lock usually dwarfs the professional fees involved.

Related at COGNOMEN

• Court action and domain theft recovery: the full service overview for cybersquatting and hijack cases
• Court action for cybersquatting under the .au regime: how the Australian route compares to arbitration
• Confusingly similar to a trademark: how panels assess the test across global zones and dispute forums

Author: Adrian Harland — Court anticybersquatting and domain theft recovery. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.