How to structure escrow for a .pl domain purchase

How to structure escrow for a .pl domain purchase. UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your case.

A Polish domain acquisition rarely fails at the negotiation stage. It fails afterward – when the buyer discovers the name carries a prior dispute, a registry flag, or an ownership trail that no title search ever caught. Structuring escrow correctly for a .pl domain purchase is the single step that separates a clean acquisition from an expensive correction.

To structure escrow for a .pl domain purchase, a buyer must complete chain-of-title due diligence under the .pl registry rules administered by NASK, confirm no active dispute or registration block exists, and hold purchase funds with a neutral custodian until the domain is confirmed transferred and locked in the buyer's registrar account. Unlike a .com transaction governed solely by ICANN accredited registrar policy, a .pl transfer is subject to Polish law and NASK's own transfer procedures – meaning the escrow mechanics must account for both the registry and the applicable national legal framework. The realistic timeline from signed heads of terms to cleared title is typically several weeks.

This page covers every step: due diligence, escrow structure, transfer mechanics, the red flags that abort the process, and when Polish court intervention becomes necessary.

Why does .pl require a different approach to escrow than a .com?

The .pl namespace sits outside the UDRP's direct reach for most private acquisitions. NASK – the Polish research and academic network that administers .pl – operates its own registration rules and transfer procedures. Those rules are grounded in Polish civil and commercial law, not in an ICANN-accredited registrar agreement. That distinction matters practically: a standard escrow instruction written for a .com transfer will miss the registry-level steps that NASK requires before any holder change is processed.

For a .com, the transfer is largely a registrar-to-registrar affair controlled by an authorization code (the EPP auth-info code). The buyer and seller agree, the code is released, the gaining registrar processes the transfer, and ICANN's inter-registrar transfer policy governs disputes about that process. For a .pl, the holder change procedure runs through NASK's own system, and the buyer's eligibility may need to be confirmed against NASK's current registration requirements before the registry will accept a new holder entry.

A second distinction: .pl has no UDRP. If a dispute over ownership arises mid-transfer, the only forum with jurisdiction is a Polish court. That means the escrow structure must contain a clear default clause specifying what happens to the purchase funds if a legal challenge is filed before completion – a clause that most off-the-shelf escrow services do not include for ccTLD transactions.

In our practice, we regularly advise buyers who have used a generic wire-transfer arrangement for a .pl acquisition, only to find the registry has rejected the transfer paperwork because a consent step was omitted. Correcting that omission after funds have moved is costly. Getting the mechanics right before signing avoids it entirely.

What due diligence should a buyer complete before escrow is opened?

Due diligence for a .pl acquisition has four distinct layers, each of which must clear before escrow instructions are drafted.

First, chain of title. NASK's WHOIS/RDDS data shows the current registered holder, the registrar of record, the creation date, and the expiry date. A buyer should pull that data and reconcile it against the seller's identity documents. Discrepancies – a holder name that does not match the selling entity, a recent holder change, or an expiry date within weeks of the proposed closing – are each a reason to pause. A domain that changed hands rapidly in the year before the current sale may be carrying someone else's unresolved claim to it.

Second, prior dispute history. Polish courts do not maintain a single searchable register of domain disputes in the way that WIPO's case database lists UDRP proceedings. A buyer must instruct counsel to search court records in the relevant Polish jurisdiction and to check whether any dispute-related annotation exists at the registry level. NASK does maintain a procedure for blocking a domain transfer pending a court order; if such a block is active, it will prevent the transfer regardless of whether escrow has been funded.

Third, trademark conflict analysis. The .pl registry rules do not grant a transferee immunity from a prior trademark holder's claim merely because the buyer pays market value. If the domain was originally registered in bad faith by the seller, a brand owner with Polish or EU trademark rights may still pursue revocation through the courts after the transfer completes. A buyer who acquires without checking trademark registers – the Polish Patent Office database and the EUIPO register at a minimum – takes that risk onto their own balance sheet.

Fourth, technical and operational status. Is the domain currently resolving? Is it pointing at active content that itself carries legal risk – counterfeit goods, defamatory material, or a pay-per-click parking page in a regulated sector? Content-related liability does not automatically transfer with ownership, but a buyer who takes control of a domain that a court later orders taken offline has lost both the domain and the purchase price.

For a structured pre-acquisition review of a .pl domain – chain of title, dispute history, and trademark conflict screen – contact info@cognomenlaw.com.

How should the escrow itself be structured for a .pl transaction?

The core function of escrow is simple: the buyer's funds are held by a neutral custodian and released to the seller only when the buyer confirms the domain has transferred cleanly. For a .pl transaction, four structural elements must be built into the escrow instruction that are often absent in generic domain escrow services.

Element one: registry-step conditionality. Release of funds should be conditional not only on the transfer authorization code being delivered, but on the NASK registry confirming the new holder entry. A .pl transfer is not complete – legally or practically – until NASK updates its records. The escrow instruction should state that the completion trigger is registry confirmation, not merely receipt of the auth-info code.

Element two: a dispute-filing default clause. If a third party files a court application to block or reverse the transfer before registry confirmation, the escrow must specify what happens to the funds. The default clause should provide that funds are held in escrow pending final resolution of the court proceeding, with a defined long-stop date after which either party may apply to a named dispute-resolution mechanism. Without this clause, a buyer and seller may both be locked out of the funds with no procedural path to resolve the impasse.

Element three: a currency and banking-law compliant payment structure. Poland is an EU member state but retains the złoty (PLN) as its currency. A transaction denominated in USD or EUR requires attention to Polish foreign exchange rules and any applicable anti-money-laundering obligations on the receiving bank. If the seller is a Polish legal entity, the buyer's counsel should confirm whether any reporting or approval step applies before funds can move cross-border. An escrow provider operating only in USD and outside of EU regulatory oversight may not satisfy these requirements.

Element four: a defined walk-away right. If due diligence reveals a material defect – an undisclosed court block, a trademark opposition that was not disclosed, or a mismatch in the holder record – the buyer needs a contractual right to withdraw from the transaction and recover the escrowed deposit without penalty. That right should be defined, with a specified cure period for the seller to resolve the defect before the walk-away right activates.

In a recent transaction (a .pl domain in a regulated professional-services sector, spring 2025), we identified an undisclosed NASK annotation at the due-diligence stage. The seller was unaware the annotation existed. The deal was restructured with an extended cure period, the annotation was lifted by court order, and the transaction completed approximately six weeks later than originally scheduled. Without the walk-away clause, the buyer would have had no clean contractual basis to pause.

What are the transfer mechanics at the NASK registry level?

The technical transfer of a .pl domain proceeds through NASK's EPP system, but the holder-change process involves steps that differ from a pure registrar-to-registrar transfer under ICANN policy. The practical mechanics depend on whether both parties use the same NASK-accredited registrar or different registrars.

Where both parties use the same registrar, the holder change is processed internally. The registrar updates the holder data in the NASK registry following its own verification procedure, which typically includes identity confirmation for the new holder. The auth-info code is used to authorize the registrar's action, but it does not itself constitute the transfer – the registrar must submit the holder-change request and NASK must accept it.

Where the parties use different registrars, the domain must first be transferred to the buyer's chosen registrar and the holder change may be processed in conjunction with or after that inter-registrar transfer. The sequence matters for escrow timing: if the escrow release is triggered by the inter-registrar transfer alone, the buyer may hold technical access to the domain before the holder record has been updated to reflect their identity. A court challenge filed at that intermediate stage creates genuine ambiguity about who the legal holder is for the purposes of any injunction.

The practical answer is to specify in the escrow instruction that both steps – the inter-registrar transfer (if applicable) and the NASK holder-change confirmation – must be complete before release. This adds a day or two to the closing timeline but eliminates the ambiguity window entirely.

If you are at the heads-of-terms stage for a .pl acquisition, email info@cognomenlaw.com for a review of the transfer sequencing and escrow instruction before drafting begins.

When does a .pl domain dispute require Polish court action?

Court involvement in a .pl domain transaction arises in two distinct scenarios: before closing, where a third party seeks to block the transfer, and after closing, where a prior claimant seeks to reverse it.

Before closing, a brand owner with Polish or EU trademark rights who discovers the domain is about to be sold may apply to a Polish court for an interim injunction preventing the transfer. Polish civil procedure allows interim relief to be granted ex parte – without notice to the other party – where the applicant can demonstrate urgency and a prima facie case. NASK will block a domain transfer upon receipt of a court order. If the escrow instruction does not account for this possibility, the deal stalls with no clear contractual mechanism to resolve it.

After closing, a party with a prior unresolved claim – for example, a trademark holder who did not discover the sale until after it completed – may commence proceedings seeking transfer of the domain to them. Polish courts have jurisdiction over domain disputes involving .pl registrations. The applicable national trademark act and civil code provisions on unjust enrichment and unfair competition are the usual legal bases. Whether such a claim succeeds against a good-faith purchaser for value depends on the specific facts, the court's assessment of the buyer's knowledge at the time of purchase, and the extent of the prior rights holder's established claim.

This is why the pre-acquisition trademark conflict analysis is not optional. A buyer who can demonstrate a thorough good-faith search – and who paid a market-rate price through a properly documented escrow – is in a substantially stronger position to defend a post-closing challenge than one who acquired informally without any due-diligence record.

In a second matter (a .pl acquisition in the consumer goods sector, autumn 2024), we assisted a buyer who received a post-closing demand from a brand owner approximately three weeks after the transfer completed. The escrow documentation, the pre-acquisition trademark search record, and the market-rate pricing evidence together formed the core of the buyer's defense. The matter settled without court proceedings.

How does the .pl route compare to a .com acquisition or a gTLD transaction?

The decision matrix for a multi-zone domain acquisition – where a buyer wants both the .com and the .pl of the same name – depends on the zone, the remedy, the timeline, and the risk profile of each acquisition.

For a .com domain, the transaction is governed by ICANN-accredited registrar agreements and the EPP transfer protocol. Disputes about ownership or prior bad faith are addressed through the UDRP – a roughly two-month process with a filing fee starting at USD 1,500 at WIPO for a single-member panel – or through US anticybersquatting litigation where damages are sought. An escrow for a .com transaction can rely on established domain escrow services and ICANN inter-registrar transfer policy for the mechanics. The buyer's primary risk is that the seller does not deliver the auth-info code, not that the registry rejects the transfer.

For a .pl domain, as set out above, the UDRP does not apply to private acquisitions. Polish courts have jurisdiction. The registry mechanics involve NASK's own holder-change procedure. The escrow structure must be specifically adapted to account for the registry-level steps, the applicable Polish law obligations, and the absence of a standardized dispute-resolution procedure if the transfer is challenged mid-process.

For a new gTLD domain in the same name (say, a .shop or .online), the URS may be relevant if bad faith is alleged by a third party – the URS can suspend the domain quickly, at lower cost than the UDRP, though it does not transfer ownership. An acquisition of a new gTLD domain is therefore closer to the .com model in terms of registrar mechanics, but carries the additional complexity that the new gTLD registry may have its own transfer restrictions or sunrise-era challenge rights still outstanding.

When a buyer is acquiring multiple zones simultaneously, we advise running parallel due diligence tracks on each zone under its own governing rules, with a single escrow structure that conditions release on all zones having transferred cleanly. A single closing date for a multi-zone acquisition is achievable but requires close coordination between the ccTLD counsel, the gTLD registrar, and the escrow custodian.

What are the most common mistakes buyers make in .pl domain escrow transactions?

The errors we see most frequently cluster around three points in the transaction.

The first is using a generic off-the-shelf domain escrow service without verifying that it has handled .pl transactions before. Many well-known domain escrow providers are built around .com transactions and do not have established procedures for the NASK holder-change confirmation step. Their escrow release triggers may be technically correct for a gTLD transfer but leave a legal gap for a ccTLD one.

The second is treating the due diligence as a checkbox rather than a substantive exercise. A buyer who pulls WHOIS data, sees no obvious flag, and proceeds to sign has not completed due diligence for a .pl transaction. The court-records search and the trademark conflict analysis are not optional steps that speed can safely skip. They are the steps that determine whether the domain a buyer is paying for is actually clean.

The third – and most costly – is failing to include a dispute-filing default clause in the escrow instruction. This is the clause that matters most if something goes wrong. Its absence does not make the transaction illegal; it makes the buyer's position contractually unclear if a third party files an injunction application before the transfer completes.

Is there a version of a .pl transaction that avoids all of these risks entirely? No transaction is risk-free. But a transaction structured with a proper due-diligence record, an escrow instruction drafted for the specific mechanics of a .pl transfer, and clear contractual default provisions is one where any dispute that does arise has a defined procedural path to resolution – rather than an improvised one.

Related at COGNOMEN

• Domain Transactions and Brand Protection – the full service overview, including pre-acquisition due diligence and portfolio monitoring
• How to recover a lapsed domain in a new gTLD – strategy guide for registrants and brand owners
• Proving no legitimate interest in a UDRP complaint – what the second element requires