Step-by-step: draft a domain assignment agreement for a .nl domain

Step-by-step: draft a domain assignment agreement for a .nl domain. UDRP and ccTLD domain recovery and defense across .nl. Email the firm to assess your case.

A .nl domain changes hands on a handshake every week. The SIDN registry processes the transfer, the registrar unlocks the name, and by Monday morning the new holder appears in RDDS. What does not change is the legal exposure that follows when the paperwork was absent or inadequate. A chain-of-title gap, an undisclosed prior dispute, or a missing representation on trademark encumbrances can cost more to unwind than the domain itself was worth.

To draft a domain assignment agreement for a .nl domain, you need a document that does four things: transfers the registrant-of-record status under SIDN's registration terms, allocates the risk of any undisclosed trademark or dispute history, structures the payment through escrow so that title and funds move simultaneously, and survives scrutiny by a court or arbitration panel if the deal is later challenged. None of that is optional; each element protects a different party from a different failure mode.

This guide walks every step in the sequence, flags the trap inside each one, and closes with the cross-zone and litigation dimensions that a purely domestic draft misses.

Step 1: Understand what .nl assigns – and what it does not

Assigning a .nl domain transfers the registrant-of-record status in SIDN's registry, not ownership of an intangible property right recognized by a specific statutory scheme. That distinction matters. The Netherlands does not have a domain-specific transfer statute analogous to the United States anticybersquatting legislation; what you are buying is a contractual position: the right to be SIDN's registrant, subject to SIDN's registration conditions.

SIDN's conditions require, among other things, that the registrant be reachable, that contact data in RDDS be accurate, and that the domain not be used in a way that infringes third-party rights. If the seller was in breach of those conditions at any point – for example, during a prior dispute or a period of false WHOIS data – that history travels with the name. Your agreement must address it.

The trap in this step: assuming that because SIDN processed a registrar transfer, the legal assignment is complete. SIDN's transfer mechanic confirms registrant-of-record change only. It does not validate representations about prior litigation, trademark encumbrances, or the authority of the transferring party to act. Those are matters for your agreement, not for SIDN.

One further point on zone specificity: for .nl, there is no UDRP. SIDN runs its own dispute procedure with its own standard. A domain sold mid-dispute, or shortly after an adverse ruling, carries reputational and legal risk that a bare registrar transfer does nothing to resolve. We advise clients to treat any .nl domain with a dispute history in the last three years as requiring heightened due diligence – and a correspondingly tighter agreement.

Step 2: Run the chain-of-title and prior-dispute check before you draft anything

Chain-of-title due diligence on a .nl domain means answering three questions before a single clause is written: who has held this name, when, and under what circumstances did each transfer occur? RDDS history, SIDN's publicly accessible registration data, and third-party registration history tools all contribute partial answers. No single source gives the complete picture.

The prior-dispute check is equally important. SIDN's dispute procedure – the Geschillenregeling Domeinnamen – produces published decisions. A quick search of the published case database reveals whether the target domain has been the subject of a complaint, a transfer order, or a finding that a prior registrant acted in bad faith. If it has, you need to know whether the complaint was resolved, withdrawn, or decided adversely.

Why does an adverse prior decision matter to a buyer? If the domain was ordered transferred to a complainant and that order was not implemented – an uncommon but real scenario – the new registrant may inherit a registration that is legally compromised. Even a withdrawn complaint signals that a trademark owner saw enough to file; they may file again.

The trap in this step: treating the RDDS snapshot at the moment of negotiation as the complete record. It is not. RDDS reflects current data only. Historical registrant data, lapsed registrations, and prior-dispute records require active research. We regularly advise buyers who discovered a dispute history only after the transfer had completed, at which point the seller was unreachable and the indemnity was untested.

For a pre-acquisition due diligence assessment on a .nl domain – including dispute history and trademark encumbrance checks – contact info@cognomenlaw.com.

Step 3: Structure the core assignment clauses

A .nl domain assignment agreement needs, at minimum, six operative elements: an identification clause, a transfer-mechanics clause, a representations and warranties cluster, an indemnity provision, an escrow and payment structure, and a governing-law and jurisdiction clause. Each one hides a trap.

Identification. Name the domain exactly as it appears in SIDN's registry, including the full registrant-of-record details of the seller as of the agreement date. If the registrant of record is a company, confirm the company's current status under Dutch commercial registration. A dissolved entity cannot validly assign anything. If the registrant is an individual acting on behalf of a corporate buyer, confirm authority. This sounds basic. It is the most common error we see in lightly drafted agreements.

Transfer mechanics. The agreement must specify that the seller will initiate the registrar-level transfer within a defined window – typically five business days of the escrow release – and will cooperate with SIDN's process including any identity verification SIDN requires. Many registrars use an authorization code (auth-code) system; the clause should require delivery of the valid auth-code as a condition of payment release.

Representations and warranties. The seller must represent, at minimum: that they are the sole registrant of record; that the domain is not the subject of any pending dispute, complaint, or court proceeding; that no prior dispute decision has been issued against the domain in the last five years (or if one has, full disclosure); that the domain does not infringe any trademark of which the seller is aware; and that the seller has the authority to assign. Each of these should survive closing.

Indemnity. The seller should indemnify the buyer against third-party claims arising from the seller's use of the domain prior to the transfer date. The scope of that indemnity – and the practical question of whether the seller can satisfy it – should be calibrated to the purchase price. A five-figure domain warrants a meaningful indemnity cap; a four-figure domain may warrant a price reduction instead.

Step 4: Build the escrow structure correctly

Simultaneous exchange – funds and domain transfer occurring at the same moment – is the only structure that fully protects both sides. In practice, simultaneity means a neutral escrow holder releases funds to the seller only after confirming that the registrant-of-record in SIDN's registry has updated to the buyer's details. Any other structure creates an interval of exposure.

The most common alternative – the buyer pays first, the seller transfers after – is the structure that generates the most domain-transaction disputes we handle. The seller takes payment, provides an incorrect auth-code, initiates a dispute that triggers a registry lock, or simply stops responding. The buyer then has a contractual claim against a counterparty who may be in another jurisdiction with no local assets.

For .nl specifically, the escrow currency and governing-law interaction matter. If the transaction is denominated in euros, the escrow service must handle euro disbursements without forcing a currency conversion that creates a fee dispute after closing. Some escrow platforms designed for US-dollar domain transactions introduce a conversion spread that neither party anticipated.

The trap in this step: believing that a reputable registrar's internal transfer mechanism is adequate escrow. It is not. Registrar-level transfers do not hold funds. An escrow arrangement is a separate contractual structure, and for any material transaction it should be documented in the assignment agreement as a condition precedent to the transfer obligation.

If you are structuring a .nl domain transaction and need escrow and agreement terms reviewed, email info@cognomenlaw.com before funds move.

Step 5: Address the trademark-encumbrance risk explicitly

A .nl domain assignment that ignores trademark encumbrance is incomplete. The buyer is not just acquiring a string of characters in a registry; they are assuming the reputational and legal position that the string carries. If the domain is confusingly similar to a registered trademark held by a third party – even a trademark the seller never thought about – the buyer steps into that risk on the day of transfer.

The due diligence layer here involves a clearance search across the Benelux trademark register (maintained by the BOIP) and, for internationally active marks, the WIPO Global Brand Database. That search should happen before the agreement is signed, not after. If a conflict appears, the buyer has three choices: renegotiate the price to reflect the litigation exposure, require the seller to clear the conflict before closing, or walk away.

Consider a scenario from our practice: a buyer acquired a descriptive .nl domain in early 2025, believing it was generic. A Benelux trademark registration for an identical word-mark had been filed three months earlier and was not yet published in the widely checked sources at the time of the buyer's informal search. The trademark owner identified the domain assignment shortly after and initiated a procedure under SIDN's dispute rules. The buyer's recourse was against the seller's warranty – which the bare agreement they had used did not contain. The litigation to recover the purchase price cost more than the domain.

The fix is straightforward: a specific representation that the seller has no knowledge of any trademark registration that is identical or confusingly similar to the domain, combined with a buyer-side clearance search that runs to within five business days of signing.

Step 6: Choose governing law and jurisdiction – and think about cross-zone exposure

For a .nl domain transaction between two Dutch parties, Dutch law is the natural choice and Dutch courts are the obvious jurisdiction. The parties can also designate the Netherlands Arbitration Institute or another recognized Dutch arbitration body for disputes. That is the simple case.

The complicated case – and the one that arises more often than sellers expect – is where one party is outside the Netherlands. A German buyer of a .nl domain, or a UK seller, brings into play conflict-of-laws questions about which court has jurisdiction and which law governs the warranty claims. An agreement that says nothing on this point leaves both parties to argue about it in front of a court that may not be convenient for either.

The right answer is an explicit governing-law clause designating Dutch law (or another mutually agreed law) and an explicit jurisdiction clause designating a court or arbitral seat. For cross-border transactions, the parties should also consider whether the buyer needs any local-court comfort in their own jurisdiction regarding enforcement of a Dutch judgment, particularly where the seller holds assets there.

There is also a cross-zone dimension that many purely .nl-focused practitioners miss. If the same brand is present in a .com or .eu registration held by a different party, a .nl assignment may be irrelevant or even counterproductive if the third-party holder of those adjacent zones could challenge the buyer's use. We have seen buyers complete a .nl acquisition only to face a UDRP complaint on their own .com filed by the party who sold them the .nl – an extreme case, but real. Checking for related-zone conflicts is part of a thorough pre-acquisition analysis.

Step 7: Execute and implement – and document everything

Execution means signed agreement, funded escrow, delivered auth-code, and confirmed SIDN transfer – all of which must occur in the sequence the agreement mandates. Implementation means updating the registrant-of-record in SIDN's registry, updating nameserver configuration if the buyer is changing the technical setup, and confirming that RDDS reflects the buyer's accurate contact data within SIDN's required window.

Documentation at this stage is not bureaucratic formality. If a dispute arises later – a third-party trademark claim, a seller who denies the agreement, or a SIDN dispute over the domain – the contemporaneous record of the transfer is the buyer's first line of evidence. That record should include: the signed agreement (with timestamps), the escrow release confirmation, the registrar's transfer confirmation, and a RDDS screenshot taken immediately after the registrant update.

The trap in this step: believing the registrar's automated transfer-confirmation email is sufficient documentation. It confirms the technical event, not the contractual one. The agreement and the escrow release are what prove the transfer was authorized, arm's-length, and paid for. Keep both.

One final implementation note specific to .nl: SIDN requires that the new registrant's contact data be accurate and reachable from the moment of registration. A buyer who does not update the technical and administrative contact information promptly is in immediate breach of SIDN's registration conditions – an ironic start to an ownership that was carefully papered elsewhere in the agreement.

Related at COGNOMEN

• Domain transactions, escrow, and pre-acquisition due diligence for brand owners and investors
• Step-by-step guide to drafting a domain assignment agreement for a .es domain
• Recovering a stolen or hijacked domain through court action and registrar escalation