Step-by-step: structure escrow for a .nl domain purchase

Step-by-step: structure escrow for a .nl domain purchase. UDRP and ccTLD domain recovery and defense across .nl. Email the firm to assess your case.

A Dutch company lists a premium .nl domain at a price your brand team wants to accept. Everything looks clean. But two things remain invisible until you dig: whether the domain carries unresolved dispute history, and whether the transfer can actually complete under SIDN's rules. Getting those wrong means the purchase price goes out the door while the domain stays put — or arrives encumbered.

To structure escrow for a .nl domain purchase, a buyer must work through five sequential steps: pre-contract due diligence on SIDN eligibility and prior disputes; a signed purchase agreement that assigns registry risk; an escrow arrangement with a neutral holder; SIDN transfer execution; and post-transfer confirmation. SIDN — the Dutch registry — mandates that the registrant of a .nl domain must be an entity or individual with a verifiable connection to the Netherlands or the broader EEA, so eligibility must be confirmed before any funds are committed. A misstep at any stage can strand the purchase.

This guide walks each step in order, identifies the trap hidden inside it, and explains what evidence anchors a clean transaction.

What makes .nl different from a .com transaction?

The .nl zone is governed by SIDN, not by ICANN's generic-TLD rules, so none of the standard UDRP or URS mechanics apply directly to a transfer dispute. That single fact reshapes the risk map for a buyer.

For a .com, the transferability of the asset is assumed: any legal entity can hold it. For a .nl domain, eligibility restrictions mean a prospective buyer must confirm that it qualifies to register in the zone before signing a purchase agreement. SIDN currently requires a Dutch address or, under its general registration policy, an address within the European Economic Area. An international brand holding only a US or UK postal address may need a Dutch subsidiary, a branch registration, or a local administrative contact — none of which is fast to arrange. Discovering that constraint after the escrow funds are deposited is the most common early-stage mistake we see in .nl transactions.

There is a second structural difference. Because SIDN operates its own dispute procedures separate from UDRP, a domain that was the subject of a prior Dutch-law complaint or a WIPO case in a UDRP-adjacent zone may carry reputational and procedural history the buyer inherits. Unlike a clean .com with a blank UDRP record, .nl dispute records are not held in a single public database. Tracing them requires targeted searches, not a single lookup.

Finally, .nl transfer mechanics run through SIDN's registrar network. The seller's registrar and the buyer's registrar must both be SIDN-accredited. A mismatch — seller at an accredited registrar, buyer intending to receive the domain through a non-accredited one — blocks completion regardless of what the purchase agreement says.

If you are assessing a .nl acquisition and need a preliminary read on eligibility and prior-dispute exposure, contact info@cognomenlaw.com before signing any agreement.

Step 1: Run pre-contract due diligence — and the trap inside it

Pre-contract due diligence on a .nl domain has four components: registrant identity and eligibility, chain of title, prior dispute history, and trademark clearance. Each one can kill the deal if it surfaces a defect; the trap is treating any one of them as optional.

Registrant identity starts with the SIDN WHOIS — now delivered through RDDS in line with GDPR-era restrictions — and often requires the seller to provide documentation of the registration history directly. Ask for: the registration date, every historical registrant of record, and any change-of-registrant events. A domain that has changed hands three times in five years in a rising market is not necessarily problematic, but each transfer is a point where a prior dispute could have been reset or obscured.

Chain-of-title review means verifying that the seller has unambiguous authority to transfer the domain. If the seller is a company, confirm that the individual signing has authorization. If the domain was acquired in a corporate restructuring or liquidation, verify that the registry acknowledged the transfer and that the domain was not locked or flagged at the point of acquisition. A domain transferred during a liquidation without a SIDN-acknowledged change-of-registrant is a domain whose title may be contested.

Prior dispute history requires searching both Dutch civil court records — because .nl disputes can end up in Dutch courts — and any WIPO or equivalent proceedings where the domain was named as a respondent domain in a related proceeding. We regularly advise buyers who assume a blank UDRP record means a clean domain; for .nl, the absence of a UDRP record is expected and tells you nothing about local court proceedings.

Trademark clearance runs in both directions. Does the domain string match, or confusingly resemble, a third-party trademark registered in the Benelux or European Union? If it does, the buyer acquires not just the domain but the exposure to a future dispute or demand from the trademark holder. The EUIPO and Benelux trademark databases are the primary search points.

Step 2: Draft the purchase agreement — and the trap inside it

The purchase agreement is the document that allocates registry risk between seller and buyer. The trap here is using a generic domain sale template that was drafted for .com transactions. Such templates omit the .nl-specific provisions that protect a buyer when SIDN's mechanics do not behave as expected.

At a minimum, the agreement should cover: the agreed domain (confirmed SIDN spelling and IDN encoding, if any); the purchase price and the currency; conditions precedent — specifically, buyer eligibility under SIDN's registration policy confirmed in writing before any funds are released; representations by the seller that the domain is free of encumbrances, liens, pending disputes, or registry locks; the escrow mechanics and the name of the neutral holder; a defined transfer window within which SIDN must acknowledge the transfer; the consequence of a failed transfer (return of escrowed funds, with or without a break fee); and choice of law and dispute-resolution clause for the purchase agreement itself.

The eligibility condition precedent deserves emphasis. If SIDN rejects the buyer's application to hold a .nl domain — because the buyer has no qualifying EEA presence — the deal cannot close. A well-drafted agreement makes that a condition for fund release, not a post-payment discovery. We have advised on transactions where this clause was missing; the outcome in each case was a dispute over who bore the cost of an unclosable deal.

Choice of law matters, too. A .nl transaction between a Dutch seller and a non-EU buyer involves at least two legal systems. Dutch law will govern the registry relationship; the purchase agreement can elect a different governing law for its own enforcement, but that election must be express. Silence defaults the agreement toward Dutch law, which may not be what an international buyer's counsel anticipated.

How do you structure the escrow arrangement for a .nl domain?

Escrow for a .nl domain purchase works the same way it does for other zones in its mechanics, but the release conditions must be written to match the SIDN transfer sequence — and that sequence has a step that many generic escrow services do not know to accommodate.

The structure has three parties: the seller (transferor), the buyer (transferee), and a neutral escrow holder. The buyer deposits the agreed purchase price with the escrow holder at the point the purchase agreement is signed. The escrow holder holds the funds under instructions that specify two release triggers: transfer confirmed and buyer eligibility verified. Neither alone is sufficient.

The SIDN transfer sequence works as follows. The seller's registrar initiates a change-of-registrant or a registrar-of-record change, depending on whether the buyer will use the same registrar as the seller or move to a different SIDN-accredited registrar. SIDN generates an authorization token. The buyer's registrar (or the seller's registrar if it is the same entity) applies the token. SIDN confirms the new registrant of record. That SIDN confirmation — typically in the form of a WHOIS or RDDS record update reflecting the buyer as registrant — is the trigger event for escrow release.

The trap is treating any earlier event — the seller delivering the authorization token, or the buyer's registrar accepting the application — as the trigger. We have seen transactions where funds were released on token delivery, before SIDN had confirmed the transfer, and the transfer subsequently failed because the buyer's registrar was not SIDN-accredited. The seller had the money; the buyer had no domain.

For larger transactions, a two-stage escrow is worth considering: a partial release on token delivery (say, 10–15% of the price) and the balance on SIDN confirmation. This compensates the seller for the delivery step while protecting the buyer's principal until the registry confirms. The precise percentages are negotiated; what matters is that the release conditions are unambiguous in the escrow instructions.

Use a specialist domain escrow service that operates under a recognized regulatory framework and can confirm that its release mechanics accommodate SIDN token delivery as a distinct event from registry confirmation. Confirm, before funds are deposited, that the service handles .nl transfers specifically. Not all domain escrow providers are familiar with SIDN's token-based transfer mechanics.

To review a proposed escrow structure for a .nl acquisition — or to assess the release conditions in a draft agreement — email info@cognomenlaw.com.

Step 3: Execute the SIDN transfer — and the trap inside it

Execution is the step where mechanical errors cause the most friction, because SIDN's authorization tokens are time-limited and the registrar coordination required is tight.

The SIDN transfer process begins with the seller's registrar unlocking the domain and requesting a transfer authorization code from SIDN. That code has a defined validity window — consult the current SIDN registrar documentation for the precise duration, which can change. If the buyer's registrar does not apply the code within the window, the code expires and the process must restart. In a time-sensitive transaction — one where the seller has other interested parties — an expired token is a real risk.

Where buyer and seller use different registrars, both must be SIDN-accredited. Verify accreditation before the purchase agreement is signed, not after. SIDN publishes a current list of accredited registrars; a registrar that was accredited when the seller originally registered the domain may have lost accreditation since. Check the current list.

The change-of-registrant step — where the domain moves from the seller's name to the buyer's name in SIDN's records — is separate from, and must follow, the registrar-of-record change if the buyer is moving to a new registrar. Doing them out of order creates a state where the domain is moving between registrars but the registrant of record still shows the seller. That intermediate state can complicate the escrow release trigger if the release condition is poorly drafted as "transfer to buyer's registrar" rather than "SIDN records show buyer as registrant."

In a recent .nl transaction (autumn 2024), a buyer engaged us mid-process after the seller's registrar had unlocked the domain but the buyer's registrar — which turned out not to be SIDN-accredited — could not accept the transfer. The authorization token had been generated, the funds were already in escrow, and the release instruction was tied to token delivery. We negotiated an extension of the token window with the seller's registrar, identified an accredited registrar the buyer could work with, and rewrote the escrow release condition to align with SIDN confirmation before the funds moved. The transaction closed roughly three weeks later than originally planned, but without loss to either party.

Step 4: Confirm the transfer and conduct post-transfer checks

SIDN confirmation that the buyer is the new registrant of record is not the end of the process — it is the trigger for escrow release and the beginning of the post-transfer checklist.

Immediately after SIDN reflects the buyer as registrant, verify four things. First, check that the domain's technical records — DNS nameservers, associated hosting — are as agreed. A seller who retains DNS control after the registrant-of-record change can still redirect the domain. The purchase agreement should require the seller to deliver DNS control simultaneously with, or immediately after, the SIDN transfer confirmation.

Second, confirm that the domain is not locked at the registry level in a way that would prevent the buyer from making administrative changes. A domain transferred under a SIDN dispute-entry block — the Dutch equivalent of a registrar lock imposed during litigation — would show a new registrant but still be administratively frozen. That freeze survives the change of registrant; it does not automatically lift.

Third, document the state of the domain at the moment of transfer: a screenshot of the SIDN WHOIS record showing the buyer as registrant, the DNS records at the point of transfer, and any associated hosting or mail infrastructure. This documentation protects the buyer in any future dispute about when ownership transferred.

Fourth, if the domain's purpose is commercial — a landing page, an e-commerce site, an email domain — run a trademark search at this point to confirm that the domain is not subject to a newly filed Benelux or EU trademark by a third party that postdates the purchase agreement but predates the transfer. The window is narrow; in most transactions it is not a material risk. But in sectors with active trademark filing activity, the check costs little and the exposure it catches is real.

How does the .nl escrow process compare to a .com transaction?

The comparison is instructive for any buyer who has previously purchased a .com domain and is approaching .nl for the first time.

For a .com, the zone is governed by ICANN, the domain is transferable to any registrant worldwide, and the UDRP provides a relatively fast dispute route if a transfer goes wrong or if a third party challenges the acquisition. The filing fee at WIPO starts at USD 1,500 for a single-member panel on a single domain. The process is arbitral, not judicial, and typically resolves in about two months. The .com market has mature escrow infrastructure, and services familiar with ICANN's transfer policy are widely available.

For a .nl domain, none of those defaults apply. SIDN's registrant eligibility rules are a buyer-side constraint that simply does not exist in the .com world. The absence of UDRP means a third-party trademark challenge after acquisition would proceed through Dutch courts or, where applicable, the broader Benelux or EU trademark enforcement system — a slower, more expensive route than an arbitral UDRP. Escrow services must understand SIDN-specific mechanics. And the choice-of-law question for the purchase agreement is more complex when the domain sits in a national registry under Dutch administrative law.

That said, .nl does not lack enforcement mechanisms entirely. SIDN's dispute procedure — distinct from UDRP — provides a route for a trademark holder to challenge an abusive .nl registration. A buyer who acquires a domain that a third-party trademark holder later characterizes as abusive will face that procedure, not a UDRP. Understanding the applicable dispute route is part of the pre-acquisition analysis, not an afterthought.

The practical upshot for a buyer choosing between a .com and a .nl: the .nl transaction requires more front-loaded due diligence, a more carefully drafted purchase agreement, and escrow mechanics that are specific to SIDN's token-based transfer process. In exchange, the .nl zone has generally lower speculative registration volume, which means fewer competing buyers and, for certain geographic or Dutch-language brands, a strategically valuable namespace with less noise.

For buyers with a portfolio spanning both gTLDs and ccTLDs, this cross-zone comparison also surfaces a monitoring obligation. A brand protected by a .com and a .nl domain needs different alert configurations: UDRP-based monitoring for the .com, and Dutch trademark and SIDN-specific monitoring for the .nl. We advise clients running dual-zone protection to maintain both independently and not assume that a UDRP-alert service covers Dutch-registry activity.

What evidence should you preserve throughout the transaction?

Evidence preservation is not a step — it runs alongside every step above. Its purpose is twofold: to protect the buyer's title in any future dispute about when and how ownership transferred, and to provide the documentation a dispute panel or court would require if a third party challenges the acquisition.

The evidence file for a .nl transaction should contain: the executed purchase agreement with the eligibility condition precedent confirmed; the seller's representation that the domain is free of encumbrances (with supporting SIDN WHOIS records at the date of signing); all communications between the parties and their registrars about the transfer process; the authorization token record and the date of its generation; the escrow service's release confirmation with timestamp; the SIDN WHOIS record at the moment of registration change; and the post-transfer DNS and hosting snapshot.

If a dispute arises — whether a seller alleging non-payment, a buyer alleging non-delivery, or a third-party trademark challenge — this file is the foundation of the defense. Panels in domain-name proceedings and Dutch courts both look for contemporaneous documentation. A buyer who can produce a clean chain from purchase agreement through SIDN confirmation is in a materially stronger position than one who relies on reconstructed correspondence.

Preserve originals where possible. Email threads are acceptable; WhatsApp or informal message-platform exchanges are harder to authenticate and easier for a counterparty to dispute. For transactions above a moderate threshold, consider using a notarized or formally witnessed exchange of the purchase agreement, particularly where the parties are in different jurisdictions.

Related at COGNOMEN

• Domain purchase, sale, escrow, and pre-acquisition due diligence for gTLDs and ccTLDs
• Domain due diligence for cross-border acquisitions including chain-of-title and dispute history checks
• Understanding TMCH claims notices and trademark clearance in domain registrations