How to enforce a UDRP decision a registrar will not implement… (.nl 2)

How to enforce a UDRP decision a registrar will not implement… (.nl 2). UDRP and ccTLD domain recovery and defense across .nl. Email the firm to assess your ca…

A UDRP panel has ordered the transfer of a .nl domain. The decision sits in your inbox. The registrar has done nothing. Days pass, then weeks – and the domain still resolves to the same infringing page it always did. What happens next?

To enforce a UDRP decision a registrar will not implement for a .nl domain, you must escalate beyond the UDRP process itself. The UDRP's transfer remedy is enforceable only through the registrar; if the registrar is unresponsive or claims a technical obstacle, the correct route shifts to SIDN – the .nl registry – and, where that fails, to the Dutch courts. The WIPO filing fee for the original complaint begins at USD 1,500, but court-level enforcement in the Netherlands is a separate proceeding with its own costs. The 20-day implementation window after a UDRP decision is the first threshold to watch.

This page covers the SIDN mechanics, the registrar-lock and transfer-reversal steps, when Dutch court proceedings become the correct path, and what evidence decides the outcome at each stage.

Why a .nl Domain Creates a Specific Enforcement Gap

The UDRP applies to gTLD domains and to the subset of ccTLDs that have voluntarily adopted it. The .nl zone sits outside both categories. SIDN – the Dutch registry that administers .nl – does not operate under the UDRP and has never adopted it. So how does a UDRP decision bind a .nl registrar at all?

The short answer is that it binds only indirectly. If the disputed domain is a .nl domain, the UDRP has no jurisdiction over it through SIDN. A complainant who filed a UDRP case targeting a .nl registration almost certainly targeted the wrong zone – the case should have proceeded under the applicable Dutch or SIDN dispute route. Where a UDRP decision was issued anyway – perhaps because the registrar is ICANN-accredited and the .nl domain was registered through a dual-accredited channel – the implementation obligation falls on the registrar's contractual relationship with ICANN, not on SIDN's rules.

That distinction matters enormously. If the registrar is ICANN-accredited and the registration agreement incorporates the UDRP, the registrar is contractually obliged to implement a valid UDRP transfer order. Failure to do so is a breach of the registrar's obligations to ICANN. It is also a breach of the registration agreement with the complainant's mark holder, once the transfer order has been made. The enforcement lever in that scenario is the ICANN accreditation mechanism combined, where necessary, with direct legal action against the registrar in its home jurisdiction.

If, on the other hand, the registrar is a SIDN-registered reseller operating exclusively under SIDN's rules – and SIDN has not adopted the UDRP – the UDRP decision carries no binding authority at registry level. Enforcement then runs through Dutch civil proceedings or, in limited circumstances, through SIDN's own complaint and escalation process.

For an assessment of your domain dispute and which enforcement route fits your specific .nl situation, contact info@cognomenlaw.com.

What Does SIDN's Own Dispute Process Cover?

SIDN maintains a dispute resolution process for .nl domains that is separate from and independent of the UDRP. The governing national procedure applies, and its scope is distinct from both the UDRP's three-element test and from any arbitration framework adopted for gTLDs. Before initiating court proceedings, a brand owner should confirm the current SIDN rules with counsel, because the applicable procedure and its eligibility requirements can be amended.

At a structural level, SIDN's approach gives the registry limited power to act on a court order or a formal dispute notice. SIDN can place a domain in a suspended or locked state pending a court proceeding. That registrar-lock mechanism – a technical flag preventing transfer or deletion of the domain while a dispute is live – is the most important administrative tool available before any court order issues.

What SIDN cannot do without a court order or a final decision from a competent body is transfer the domain to a third party against the current registrant's wishes. The registry does not have unilateral discretion to override a registrant's ownership based solely on a trademark holder's assertion, however compelling. That is why court action is frequently the decisive step for .nl enforcement.

A registrar-lock request, combined with a notice of impending proceedings, is typically the first action to take when a UDRP transfer order has not been implemented and the registrar is unresponsive. It prevents the registrant from moving the domain to a less cooperative registrar, from deleting it, or from transferring it to a third party who could claim bona-fide purchaser status. Time spent without a lock in place is time during which the domain can be moved beyond reach.

The Registrar-Lock and Transfer-Reversal Mechanics: Step by Step

When a UDRP decision orders transfer and the registrar has not acted within the standard implementation window, the enforcement sequence in a .nl context typically follows these steps. Each step is a decision point with its own risk profile.

Step 1 – Confirm the registrar's ICANN status. The threshold question is whether the registrar is ICANN-accredited. If yes, the registrar's failure to implement a valid UDRP order is a breach of its Registrar Accreditation Agreement. The complaint path runs to ICANN's compliance department. An ICANN compliance submission creates a formal record of the breach and can produce registrar remediation within a matter of weeks, though outcomes depend on the registrar's responsiveness and ICANN's current caseload.

Step 2 – Request a registrar lock through SIDN. In parallel with any ICANN complaint, contact SIDN directly to request that the domain be placed in a locked state. Provide the UDRP decision, evidence of trademark rights, and a clear statement that proceedings are being prepared. SIDN's lock does not transfer the domain, but it prevents its disappearance.

Step 3 – Issue a formal demand to the registrar. A written demand citing the UDRP decision, the registrar's contractual implementation obligation, and a defined deadline for compliance creates the evidentiary record needed for any subsequent court application. The deadline should be short – five to ten business days is standard practice in our experience.

Step 4 – File for interim relief in the Dutch courts. If the registrar does not comply by the deadline, a kort geding – the Dutch summary injunction procedure – is the fastest court route. A kort geding can produce an enforceable injunction directing the registrar or SIDN to transfer the domain within weeks rather than months. The procedure is designed for urgent matters where delay causes continuing harm. Failure to act is one such harm, because the infringing domain continues to operate throughout.

Step 5 – Enforce the court order against SIDN. Once a Dutch court order issues directing transfer, SIDN will implement it. The registry is bound by a domestic court judgment in a way that it is not bound by a foreign arbitration award issued under the UDRP. That is the jurisdictional reality of .nl enforcement: the Dutch court system is the final enforcement mechanism.

In a recent matter involving a .nl domain (summer 2025), we coordinated a SIDN lock request alongside a registrar demand letter following a UDRP transfer order that had sat unimplemented for over three weeks. The combination – formal demand plus registry lock – prompted the registrar to comply without requiring a court application, though the court filing had already been prepared. Not every case resolves at that stage.

When Does a Court Action Beat Arbitration for a .nl Domain?

The better question is not always which route is faster. It is which route produces a result the registry will actually implement. For .nl, that calculation favors court action in several common scenarios.

If the registrar is not ICANN-accredited – operating solely under SIDN's reseller framework – a UDRP decision has no binding force at registry level. Court proceedings in the Netherlands are the only mechanism that produces an order SIDN must follow. In that situation, filing a UDRP complaint was a procedural misstep; the correct first step is a Dutch court application supported by trademark evidence and evidence of bad-faith registration or use under the applicable national rules.

If the registrar is ICANN-accredited but located outside the Netherlands – in a jurisdiction with less cooperative enforcement norms – the ICANN compliance route may be slow and unreliable. A Dutch court order served on SIDN directly bypasses the non-compliant registrar. SIDN's obligation to comply with domestic court orders exists regardless of the registrar's location or conduct.

If the domain is being used in a way that causes ongoing harm to customers – phishing pages, counterfeit goods, fraudulent invoicing – the urgency argument for a kort geding is strong. Dutch courts regularly grant interim injunctions within two to four weeks in well-prepared cases. The cost of that route is higher than a UDRP filing, but the speed and the binding force of the outcome frequently justify it.

Conversely, if the registrar is ICANN-accredited and the UDRP decision is recent and clearly valid, the ICANN compliance route combined with a registrar demand may achieve implementation without court proceedings. The decision matrix depends on the registrar's identity, its home jurisdiction, and the urgency of the harm on the ground.

For a cross-zone comparison: a complainant facing both a .com and a .nl variant of the same infringing registration is dealing with two different rulebooks simultaneously. The .com proceeds under the UDRP at WIPO or the Forum; the .nl must be addressed through SIDN's process or the Dutch courts. A coordinated strategy for both zones – timed so that a UDRP transfer order on the .com is not used as a substitute for proper .nl proceedings – is essential to prevent the registrant from pivoting to the surviving domain.

To weigh UDRP against a court action for your .nl case, email info@cognomenlaw.com.

What Evidence Decides the Outcome?

The evidence that drives enforcement in Dutch court proceedings is different from the evidence that drives a UDRP complaint. Understanding that distinction is critical before any filing.

In a UDRP, the three-element test of Paragraph 4(a) structures everything: trademark rights, no legitimate interest in the registrant, and bad faith in both registration and use. The panel reviews documentary submissions and applies the Policy's framework. Evidence of the domain's use – pay-per-click parking, phishing, counterfeit sales – is the core of bad-faith proof under Paragraphs 4(b) and 4(c).

In Dutch court proceedings – and in SIDN dispute escalations – the framing shifts. The court applies Dutch trademark law, general civil law principles, and, where relevant, EU trademark regulations. The questions the court asks include: Does the complainant hold valid trademark rights recognized in the Netherlands? Is the domain registration or use likely to cause confusion or to dilute the mark? Did the registrant act in bad faith under Dutch law? Is the harm ongoing and irreparable by monetary compensation alone?

The evidence that matters most in that analysis includes the following:

• Proof of trademark registration in the Netherlands or the EU (a EUIPO or Benelux registration is the strongest anchor).
• A chronology showing the domain was registered after the trademark became distinctive, particularly if the registration post-dates the mark by a short interval.
• Screenshots documenting the domain's use – landing pages, redirects, phishing content, or pay-per-click monetization – with timestamps and metadata preserved.
• Evidence of actual consumer confusion: misdirected emails, customer complaints, fraudulent invoices using the domain, or similar documented harm.
• The UDRP decision itself, as persuasive evidence of a prior finding on the same facts, even though it is not binding on the Dutch court.
• Correspondence showing the registrant's awareness of the trademark and any demand for payment, which maps to the equivalent of the UDRP's Paragraph 4(b)(i) bad-faith factor.

The UDRP decision is particularly useful evidence in a Dutch court application. Panels have consistently held that a prior arbitral finding carries significant persuasive weight, even where the court is not bound by it. A well-reasoned UDRP transfer order – one that clearly addresses each of the three UDRP elements and finds bad faith specifically – gives the court a structured analysis it can treat as a starting point rather than building the case from scratch.

What the court will not simply rubber-stamp is a UDRP decision that was thin on reasoning or that reached bad faith on circumstantial grounds alone. If the original UDRP decision was awarded on default – meaning the registrant did not respond – the Dutch court may allow the registrant to present arguments for the first time. That is one reason why the quality of the underlying UDRP record matters even after the decision has been made.

How to Handle a Non-Compliant Registrar: Practical Escalation Options

A registrar's failure to implement a UDRP transfer order is, on its face, a breach of the registrar's contractual obligations under the ICANN Registrar Accreditation Agreement. But not every registrar responds to that characterization. Some are unaware of the relevant provision; some are under instruction from the registrant; some are in jurisdictions where ICANN compliance pressure has limited practical effect.

The escalation options, from lowest to highest cost, run as follows. First, a formal ICANN compliance complaint – submitted through ICANN's online portal – creates an official record and triggers ICANN's follow-up process with the registrar. This is free to file and is the correct first escalation step if the registrar is ICANN-accredited. Second, a lawyer's letter to the registrar, citing the UDRP decision and the accreditation agreement breach, frequently produces faster action than an ICANN complaint alone. Registrars are sensitive to formal legal correspondence, particularly where the letter identifies the specific implementation obligation and a short deadline. Third, direct escalation to SIDN – as described above – places the registry between the complainant and the non-compliant registrar. SIDN has the technical ability to lock the domain and to facilitate transfer pursuant to a court order, independent of the registrar's cooperation. Fourth, a Dutch court application – typically the kort geding – produces a judgment enforceable against both the registrar and SIDN. Once a court order issues, SIDN will act regardless of the registrar's position.

In a second matter we handled (a .nl commercial dispute, spring 2025), the registrar was located in a jurisdiction with limited ICANN enforcement reach, and the ICANN compliance submission produced no response within the first month. We served a formal demand and simultaneously filed for a kort geding. The court issued an interim order within approximately three weeks. SIDN implemented the transfer within five business days of service of that order. The total elapsed time from the original UDRP decision to final transfer was approximately eleven weeks – longer than a clean UDRP implementation, but the domain was off the infringing page within three weeks of the court filing.

Is a .nl Domain Even Subject to UDRP in the First Place?

This question – one we encounter frequently in practice – is worth addressing directly, because it shapes every subsequent enforcement decision. SIDN has not adopted the UDRP. The .nl zone operates under SIDN's own rules, and the governing national procedure applies to disputes over .nl registrations. A UDRP complaint filed targeting a .nl-only domain registration would ordinarily fall outside the UDRP's jurisdictional scope.

Where confusion arises is in two specific scenarios. First, a registrant may hold both a .com (or other gTLD) and a .nl registration of the same infringing name. A UDRP complaint can address the .com; it cannot address the .nl. The complainant may incorrectly assume the UDRP covers both. Second, some registrars are ICANN-accredited and also offer .nl registrations as resellers under SIDN. The accreditation applies to the registrar's gTLD operations; it does not convert .nl registrations into UDRP-covered domains. The registrar's ICANN obligations do not extend to SIDN-governed registrations.

The practical consequence: if a UDRP decision was issued and references a .nl domain, verify carefully whether the domain in question is a gTLD that happens to use "nl" in its label (unlikely but possible), or whether the registrar's specific contractual arrangements with SIDN have imported any UDRP-like obligations (rare and fact-specific). Absent such specific arrangements, enforcing a UDRP transfer order against a .nl domain requires the Dutch court route regardless of the UDRP panel's findings.

That is not a counsel of despair. The UDRP decision remains useful – as persuasive evidence, as proof of bad faith under a consistent factual record, and as a document a Dutch court will read with interest. It simply is not the end of the road; it is the beginning of the court stage.

Related at COGNOMEN

• Court action and domain theft recovery across gTLDs and ccTLDs – the full service overview
• Court action for cybersquatting in Switzerland – when arbitration is not enough
• Domain escrow and transfer mechanics for .nl transactions – a practical guide