How to draft a domain assignment agreement for a .pl domain

How to draft a domain assignment agreement for a .pl domain. UDRP and ccTLD domain recovery and defense across .pl. Email the firm to assess your case.

A buyer and seller agree on a price for a valuable .pl domain. The handshake is done. But without a properly structured assignment agreement, the transfer can unravel at the registry, expose the buyer to a hidden prior-dispute claim, or leave the seller liable for content the new registrant posts after closing. The paperwork is the deal.

To draft a domain assignment agreement for a .pl domain you must address three interlocking concerns: a clear chain-of-title clause showing unencumbered ownership, a representation that no Polish court proceeding or NASK registry dispute is pending against the name, and a mechanics clause that mirrors NASK's own transfer requirements so the registry will execute the change without a hitch. There is no UDRP for .pl – disputes over the zone are resolved through the Polish courts or voluntary arbitration, which means pre-acquisition due diligence carries more weight here than in any UDRP-governed zone.

This page explains every clause a .pl assignment agreement needs, the due-diligence checks that protect both sides, how escrow fits into the process, and how COGNOMEN prepares these documents for buyers, sellers, and portfolio holders.

Why .pl Is Different from a .com Transfer – and Why That Matters for Your Agreement

.pl operates entirely outside the UDRP. NASK, the Polish registry, does not administer a mandatory arbitration procedure equivalent to the UDRP for disputed names. When ownership of a .pl domain is contested, the dispute goes to the Polish civil courts – or, where the parties agree, to a designated arbitration body such as the Court of Arbitration at the Polish Chamber of Information Technology and Telecommunications (SA KIGiT). That single structural fact reshapes everything about how an assignment agreement should be drafted.

For a .com, a buyer can at least search WIPO and the Forum's published databases for prior complaints against the name. For .pl, the equivalent search is a judgment registry check and a NASK administrative records inquiry – neither of which a buyer can run without knowing what to look for. If the domain was previously transferred under a court order, or if a court has issued a security measure (zabezpieczenie) freezing transfers, an agreement that ignores those facts may be void or voidable under Polish law from the moment it is signed.

The assignment agreement, in other words, does two jobs at once: it documents the commercial terms and it is also the primary due-diligence instrument. Drafting it well means building both functions into a single document.

For a read on whether your .pl transaction is structured to close cleanly, reach us at info@cognomenlaw.com.

What Chain-of-Title Due Diligence Does Your .pl Agreement Need to Address?

Chain-of-title for a domain name is the unbroken record of registered ownership from original registration to the current seller. For a .pl domain, the starting point is a WHOIS/RDDS query against the NASK database, which shows the current registrant, the registrar, and the registration date. That query is necessary but not sufficient. Several additional checks must be completed before a buyer should sign anything.

First, the agreement should require the seller to warrant – with a representation that survives closing – that no court judgment, interim injunction, or security order relating to the domain is in effect. Polish civil procedure allows a court to impose a transfer freeze as a preliminary measure in intellectual-property or unfair-competition proceedings. A seller who signs the agreement and accepts payment while such a freeze is in place may be personally liable; a buyer who receives the transfer may later see it reversed by court order.

Second, the agreement should include a representation that the domain has not been the subject of a prior transfer ordered by a court or an arbitration award. Unlike UDRP decisions, which are publicly indexed by WIPO and the Forum, Polish court decisions affecting domain ownership are not consolidated in a single searchable database. Counsel must run a targeted search of the seller's identity in relevant court registries. We regularly advise buyers in transactions where this search surfaces an earlier civil claim that the seller did not disclose – and the discovery changes the deal terms or kills it entirely.

Third, check trademark conflicts proactively. The Polish Patent Office (Urząd Patentowy RP) and the EUIPO both index marks that could form the basis of a future court claim by a third party against the buyer after transfer. A domain that reproduces a registered Polish or EU trademark creates litigation exposure for the buyer the moment title passes. The assignment agreement should allocate that risk clearly – either through a seller indemnity or through a price adjustment after a trademark search.

Finally, confirm the registrar relationship. NASK operates through accredited registrars. The transfer mechanism at NASK requires an authorization code (AuthInfo) and registrar-side confirmation. The agreement's mechanics clause must specify who initiates the registrar transfer, within what time frame after payment clears, and what happens if the registrar rejects the transfer request for a technical reason.

How Should the Assignment Agreement Be Structured Clause by Clause?

A well-drafted .pl domain assignment agreement has seven functional blocks. Each block resolves a specific risk; none is optional.

1. Identification of the domain and the parties. Name the domain exactly as registered in NASK. Include the full registrant name, address, and PESEL or NIP (tax identification number) for natural persons and entities respectively, matching the NASK WHOIS record. A mismatch between the agreement and the registry record is the most common reason a transfer request is bounced back by the registrar.

2. Representation of unencumbered title. The seller warrants that it is the sole registered holder, that no third party has a contractual right or court order to the domain, that no transfer freeze or security measure is in effect, and that no prior assignment agreement for the same domain exists. This representation is the contractual anchor of the chain-of-title check.

3. Disclosure of prior disputes. The seller separately discloses – in a schedule, not buried in boilerplate – any past or pending court claim, demand letter, arbitration notice, or informal cease-and-desist relating to the domain. Where a prior dispute was resolved in the seller's favor, the agreement attaches a copy of the court order or settlement agreement. Where it was resolved against the seller and the seller nevertheless retained the domain, the buyer should pause and take independent legal advice before proceeding.

4. Purchase price and payment mechanics. State the agreed price in a defined currency. For cross-border .pl transactions, euro-denominated pricing is common; for domestic deals, Polish zloty. Specify the bank account and the payment timeline relative to the trigger events (signing, escrow funding, registry confirmation). Never make payment contingent on the buyer's subjective satisfaction – that clause invites disputes about whether the domain's traffic or SEO value met an unstated expectation.

5. Escrow structure. For any transaction above a modest threshold, both sides are better served by a neutral escrow arrangement than by sequential performance. The buyer funds escrow; the seller initiates the registry transfer; once NASK confirms the domain in the buyer's name, escrow releases to the seller. If the transfer fails for a technical reason, escrow returns to the buyer. The agreement must name the escrow agent, specify the release conditions, and allocate escrow fees. In our practice, most .pl domain transactions above a five-figure euro value use a formal escrow service; smaller deals sometimes use registrar-facilitated push transfers with a contractual holdback.

6. Post-transfer obligations. The seller undertakes to cooperate with any registrar confirmation requests within a defined window (typically three to five business days). The buyer undertakes to assume all ongoing registration fees and accept responsibility for domain content from the transfer date. Both undertakings prevent the post-closing limbo where neither party wants to manage the domain during the NASK processing period.

7. Governing law and jurisdiction. For a .pl domain, Polish law is the natural choice – NASK is a Polish legal entity and the registry relationship is governed by Polish law regardless of what the agreement says. Parties may choose Warsaw arbitration (SA KIGiT is the domain-specialized venue) or the ordinary civil courts. For international buyers, an agreement to arbitrate in Warsaw in Polish and English, with the award enforceable under the New York Convention, is often more practical than Polish court litigation.

To review a draft agreement or structure a .pl domain acquisition from scratch, email info@cognomenlaw.com.

How Does Escrow Protect Both Buyer and Seller in a .pl Domain Deal?

Escrow removes the central trust problem in any domain transaction: the buyer does not want to pay before the domain is confirmed in its name, and the seller does not want to initiate the registry transfer before payment clears. Sequential performance – one side acts first and then trusts the other – is the arrangement most commonly exploited in domain fraud.

For .pl transactions, the escrow structure needs one additional step that .com deals do not always require: confirmation that the NASK transfer has actually been processed and the registrant record updated, not merely that the registrar has sent an authorization code. The NASK system can show a domain as "pending transfer" for a period while the previous registrar's release is processed. Escrow should not release until NASK's WHOIS confirms the new registrant name – not merely the new registrar.

In a recent matter (a .pl commercial domain acquisition, spring 2025), we structured an escrow release condition tied specifically to NASK WHOIS confirmation. The seller's registrar delayed the release of the domain by several days beyond the expected window, and the escrow holdback meant the buyer's funds were never at risk during that delay. The deal closed without dispute once the NASK record updated.

For smaller transactions where a formal escrow service is disproportionate to the deal value, the agreement can replicate escrow mechanics through a contractual holdback: the buyer pays a portion of the price on signing and the balance within 24 hours of NASK confirming the transfer. That structure works for transactions under a defined threshold; it depends on both parties accepting some settlement risk that a formal escrow eliminates entirely.

What Evidence and Disclosures Decide Whether a .pl Domain Deal Can Close?

A .pl assignment agreement that is well-drafted but lacks supporting evidence packages is still a fragile document. The disclosures attached to the agreement – and the searches that produced them – determine whether the deal will survive a post-closing challenge.

The minimum evidence package for a .pl domain acquisition has four components. First, a dated NASK WHOIS printout showing the seller as current registrant at the time of signing. Second, a trademark search result from the Polish Patent Office and EUIPO covering the domain string and close variants, dated within 30 days of closing. Third, a written disclosure schedule signed by the seller itemizing any past dispute, court claim, or demand letter relating to the domain. Fourth, the seller's tax identification documents confirming that the registered entity in NASK matches the entity executing the agreement.

Where the domain has prior dispute history – even a dispute that the seller won – the buyer's counsel should review the basis of the dispute. A court ruling in the seller's favor based on a narrow procedural ground (for example, the claimant's standing was dismissed rather than the merits decided) does not preclude a future claim by a different party with better standing. We have advised buyers who acquired domains with clean-looking prior dispute outcomes only to face a fresh claim from a trademark holder who was not a party to the original proceeding. That risk is manageable with proper disclosure and pricing, but not if it is discovered after the purchase price has been paid.

In a second recent matter (a .pl portfolio acquisition covering several domain names, autumn 2024), our due diligence review identified one domain in the seller's portfolio with an unresolved trademark conflict. The assignment agreement was structured to exclude that domain from the closing, with a separate holdback mechanism allowing the buyer to acquire it later if the trademark conflict resolved in the seller's favor. The rest of the portfolio transferred cleanly.

Can Existing Dispute History Taint a .pl Domain After Transfer?

Yes – and this is the risk that catches buyers who skip the due-diligence phase and move directly to signing. Under Polish law, a domain name transfer does not extinguish pending claims against the domain by third parties. A trademark holder who filed a civil claim against the previous registrant may be able to join or amend the claim to reach the new registrant, particularly if the transfer occurred after the claim was filed or after the trademark holder gave written notice of its rights.

The practical consequence is that a buyer who acquires a tainted .pl domain inherits not only the registration but the legal exposure that came with it. Polish unfair-competition law (drawing on the general framework of the applicable national statute on combating unfair competition) protects distinctive marks even where they are not formally registered as trademarks. A domain that reproduces a well-known trade name, even without a registered mark behind it, can generate liability for the buyer from day one of ownership.

This is why the seller's disclosure schedule is not a formality. It is the mechanism by which the risk is allocated. If the seller discloses a prior claim and the buyer proceeds, the buyer takes the risk knowingly and the agreement can include an indemnity running from the seller to cover costs arising from pre-transfer conduct. If the seller fails to disclose and a claim emerges, the seller faces contractual liability for breach of the representation-and-warranty clause – but the buyer is still in litigation in Warsaw, which is not the preferred outcome.

How do you know whether there is a hidden dispute before the seller discloses it? Counsel runs a search of Polish court registries under the seller's name and the domain string. It is not a perfect search – Polish court data is not fully centralized – but it surfaces the most common risk: a pending injunction or a judgment entered within the limitation period. The search takes time and expertise; it cannot be replicated by a non-specialist reading a WHOIS printout.

How Does a .pl Assignment Differ from a UDRP-Zone Transfer, and When Do You Need Both?

The right approach depends on the zone and the goal. If the domain you are acquiring or defending is a .com, the relevant governance is UDRP-based and a prior-dispute search is straightforward through published WIPO and Forum databases. The assignment agreement for a .com can be shorter because the buyer has more accessible pre-closing information. For a .pl, the absence of a UDRP equivalent means the assignment agreement itself must do the work that published arbitration databases would otherwise do – hence the disclosure schedule and the court-registry search requirement.

Where a brand operates across both .pl and a .com or other gTLD, an acquisition may require two separate assignment agreements: one for the gTLD transfer (which follows the registrar's own mechanics and may also involve UDRP-zone considerations) and one for the .pl transfer (which follows NASK's requirements and Polish governing law). The two agreements should be cross-conditioned if the buyer's intent is to acquire the full name across zones – meaning that neither agreement closes unless both close. Failing to cross-condition leaves the buyer holding one zone while the seller retains the other, which defeats the brand-consolidation purpose of the acquisition.

If the .pl domain is genuinely disputed – meaning a third party is asserting superior rights to the name – the assignment transaction may need to pause while the dispute is resolved through the Polish courts or SA KIGiT arbitration. Buying a contested domain is not inherently inadvisable, but the agreement must reflect the contingency, price the risk accurately, and structure appropriate escrow or holdback terms to account for a possible adverse outcome in the dispute.

For cross-border acquisitions where the buyer is not a Polish legal entity, the agreement should also address the Polish VAT implications of the transaction and any foreign-investment notification requirements. These are areas where local counsel in Poland coordinates with COGNOMEN's transactional work on the domain-specific clauses.

Related at COGNOMEN

• Domain transactions, escrow, and portfolio due diligence across gTLDs and ccTLDs
• Brand-protection monitoring for domain portfolios in .me and beyond
• Guide to recovering a phishing or AI-misused domain