Step-by-step: enforce a UDRP decision a registrar will not implement for a .es domain

A WIPO panel orders transfer of a domain to you. The case is decided. The registrar does nothing. If the domain sits in a Spanish registrar's system and the registrar will not act — whether through inertia, a technical claim, or an active hold placed by the registrant — the work is not over. The question becomes how to enforce a UDRP decision a registrar will not implement for a .es domain, and how quickly you can move before the registrant exploits the delay.

Enforcement of a UDRP decision against a non-compliant registrar for a .es domain proceeds on two parallel tracks. The UDRP transfer mechanism runs through ICANN-accredited registrars, but .es is governed by Red.es under Spanish national rules, not by the UDRP directly. Where a registrar stalls, escalation through Red.es, a formal complaint to ICANN, and — when those fail — Spanish court proceedings with interim relief are the levers that move a frozen transfer. Acting within days, not weeks, prevents the registrant from transferring the domain to a new registrar or zone, erasing the compliance obligation entirely.

This guide walks each step in order, identifies the trap hidden in each one, and explains how evidence and timing interact with the Spanish registry framework.

Why .es adds a layer the UDRP alone cannot resolve

The UDRP binds ICANN-accredited gTLD registrars to implement panel decisions within a set window. That obligation is not automatic for country-code domains. .es is managed by Red.es, Spain's national registry, under rules that sit entirely outside the ICANN UDRP compact. Red.es has its own dispute procedure — the ADOMAIN procedure — distinct from the UDRP and applying a different legal test. A UDRP decision concerning a domain in a gTLD like .com does not carry binding force over a .es registrar in the same way it would over a Verisign-zone registrar.

This is the first trap: assuming that a WIPO transfer order is self-executing across all zones. It is not. The enforcement chain runs through the registrar's contractual relationship with Red.es and, behind that, through Spanish civil courts. Understanding that architecture is the prerequisite to moving at all.

The practical consequence is significant. A registrar handling your .es domain may be ICANN-accredited for its gTLD portfolio but is also bound by Red.es accreditation terms for the .es namespace. Those two sets of rules coexist. Which rules govern your transfer dispute depends on which zone the domain sits in — and for .es, the Spanish national framework takes precedence.

We regularly advise brand owners who discover this split only after a UDRP decision has been issued. The assumption that one arbitration win resolves all zones simultaneously is common and consistently wrong. For cross-zone portfolios — a .com and a .es both registered to the same bad actor — each domain needs its own enforcement path.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

Step 1 — Confirm the transfer window and identify who is stalling

Before escalating, confirm exactly what the panel ordered and whether the implementation window has closed. UDRP transfer orders typically give the registrar a short window — commonly around ten business days — to implement absent a registrant filing court proceedings to stay the order. If that window has passed without action, you have a clear default. If it has not, you may still be within a period where the registrar is technically compliant.

The trap in Step 1: confusing the registrar's silence with a contested hold. A registrant who files court proceedings in their home jurisdiction — including a Spanish court — within the implementation window can place a legal stay on transfer. That stay is legitimate under UDRP procedure. If the registrar is holding because of such a stay, your path is to address those court proceedings directly rather than pursuing the registrar for non-compliance.

Identify, specifically, who is stalling and why:

• Has the registrar acknowledged the order and explained its inaction in writing?
• Has the registrant provided the registrar with a copy of a court filing or interim injunction?
• Is the domain locked — and if so, under what stated reason in the WHOIS/RDDS record?
• Has the registrar acknowledged a technical barrier (e.g., an AUTHINFO code dispute, a pending EPP operation)?

The answer to each of these changes the next step. A registrar that simply ignores the order is a compliance problem. A registrar acting on a court-ordered hold is a litigation problem. The evidence you need — and the forum you use — differs between the two.

Step 2 — Escalate formally through ICANN and Red.es

If the registrar is ICANN-accredited and is ignoring a UDRP order with no stated legal basis, escalation through ICANN's Contractual Compliance function is the documented first move. ICANN can investigate whether the registrar is in breach of its Registrar Accreditation Agreement (RAA). This is not litigation — it does not directly force a transfer — but a formal ICANN inquiry on record strengthens every subsequent step and often prompts registrar cooperation.

Simultaneously, if the registrar is a Red.es-accredited registrar for the .es namespace, file a formal written complaint with Red.es. Red.es has accreditation agreements with registrars that include service and compliance obligations. A registrar that refuses to implement a valid transfer instruction without legal justification may be in breach of those accreditation terms. The trap in Step 2: treating these escalations as alternatives. They are parallel filings. Each creates its own paper trail, and together they establish that you exhausted administrative remedies before going to court.

Document everything: the date of the panel decision, the order's exact terms, every communication with the registrar, every non-response, and the WHOIS/RDDS snapshots showing the domain status at each point. That documentation package is the foundation of both the administrative complaints and any subsequent court filing.

How does the Red.es ADOMAIN procedure interact with a prior UDRP decision?

Red.es operates the ADOMAIN procedure as the official dispute mechanism for .es domains. It applies a distinct legal test focused on whether the registration infringes third-party rights under Spanish and EU law, and it does not simply adopt UDRP decisions as binding precedents. A UDRP transfer order you have already won is persuasive evidence in an ADOMAIN proceeding, but it is not preclusive — the ADOMAIN panel conducts its own analysis.

Why does this matter for enforcement? If the registrar will not implement your UDRP order and the domain itself is a .es, you may need to run an ADOMAIN proceeding as a parallel track — particularly where the bad-faith conduct continues in the Spanish zone. A successful ADOMAIN decision creates a direct registry-level obligation to transfer or cancel the .es domain. That obligation runs from the registry, not from the registrar, making it significantly harder to frustrate.

The ADOMAIN procedure has its own published timelines and fees — verify current rates with Red.es directly, as these can change. The legal test under ADOMAIN is substantively different from the UDRP three-element framework: the complainant must demonstrate that the domain registration infringes Spanish or EU intellectual property rights and that the registration was made in bad faith or without legitimate interest. The specific statutory bases draw on applicable national trademark law; do not assume the UDRP's Paragraph 4(a) analysis maps directly.

In our practice, we advise clients to treat the UDRP proceeding and the ADOMAIN track as complementary rather than sequential. Winning both creates redundant enforcement pathways. Winning only one — particularly where a non-compliant registrar is the bottleneck — leaves a gap the registrant can exploit.

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

Step 3 — Apply for Spanish court interim relief before the domain moves

When administrative escalation has not produced transfer within a short period — and the registrant is still operating the domain — Spanish court proceedings become the primary enforcement tool. The key mechanism is an interim injunction (medida cautelar) preventing the registrar and registrant from transferring, modifying, or deleting the domain pending resolution of the underlying IP claim.

This is the step most complainants delay too long. The trap in Step 3 is believing the UDRP decision makes court proceedings redundant. It does not. Under UDRP rules, a registrant who files court proceedings within the implementation window can legally freeze a transfer order. If the registrant moves first — filing a declaratory action in a Spanish court challenging your rights — you are now the defendant in their chosen jurisdiction. Moving quickly with an interim injunction application keeps the initiative with you.

Spanish interim relief applications in IP and domain matters typically require:

1. Evidence of the underlying trademark or other IP right forming the basis of the dispute.
2. Evidence of the domain registration and the registrant's identity (WHOIS/RDDS records, historic screenshots).
3. Evidence of actual harm or imminent risk — for example, the domain redirecting traffic, generating confusion with your brand, or being actively marketed to customers.
4. The UDRP panel decision itself, as evidence that an international arbitral body already found bad faith on the merits.
5. Evidence that the registrar will not implement voluntarily, demonstrating that interim court relief is necessary.

Interim relief in Spain is handled by local litigation counsel in the relevant jurisdiction. We coordinate with qualified Spanish IP litigators and provide the domain-dispute record — the UDRP filings, the panel decision, the registrar correspondence — that forms the core of the application. The UDRP decision's factual findings on bad faith and lack of legitimate interest carry real persuasive weight with a Spanish court, even though the court is not bound by the UDRP outcome.

In a recent matter (a .es domain tied to a brand-name typosquat, spring 2025), we coordinated an interim injunction application alongside a Red.es ADOMAIN filing after the registrar failed to act on a prior WIPO order for nearly six weeks. The combination of the UDRP record and documented registrar inaction produced a domain lock within days of the court filing, preventing a pending transfer to a third party that would have reset the enforcement chain entirely.

What evidence decides whether enforcement succeeds?

The quality and completeness of your evidence file is what separates a fast resolution from a prolonged stall. Three categories of evidence carry the most weight at each enforcement stage.

Trademark and rights evidence is the foundation. A registered trademark — ideally a Spanish or EU registration — is the strongest basis, but established unregistered rights under applicable national trademark law can also qualify. The registration date relative to the domain registration date matters: a mark that predates the domain registration by a clear margin strengthens both the ADOMAIN case and the court application. A mark registered after the domain was first registered, by contrast, weakens the timeline and requires careful framing.

Registrar-conduct evidence is specific to the enforcement context. This includes the dated correspondence trail showing the registrar received notice of the UDRP decision, the responses (or non-responses) it gave, and the WHOIS/RDDS record showing the domain's status at each point. A registrar that acknowledged the order and then did nothing is in a weaker position than one that gave a documented legal justification. Screen-capture everything with timestamps.

Bad-faith-use evidence continues to matter even after the UDRP decision. If the registrant is still using the domain — redirecting traffic, displaying competing content, sending phishing emails, or soliciting a sale — that active use reinforces the urgency of interim relief and supports the claim that the UDRP decision must be enforced without further delay. Archive web content regularly: live screenshots, Wayback Machine records, and any email communications originating from the domain.

One evidence trap: assuming the UDRP record is complete. The panel decision was based on what you submitted during the UDRP. Post-decision conduct — the registrar's non-compliance, any new registrant activity, any transfer attempts — must be documented separately and added to the enforcement file. Courts and the Red.es ADOMAIN panel will ask about what happened after the UDRP, not just during it.

When does a court route beat the administrative track for .es?

The decision between the administrative track (ADOMAIN plus ICANN/Red.es escalation) and the court route (Spanish IP litigation with interim relief) depends on four factors: the urgency of the threat, the registrant's litigation behavior, the zone configuration, and whether you want damages in addition to transfer.

Administrative escalation is preferable when the registrar's non-compliance appears to be procedural rather than deliberate — a technical failure, a processing lag, or a staffing gap — and when there is no immediate risk of the domain being transferred or weaponized. The ADOMAIN procedure is specifically designed for .es domains and produces a registry-level transfer obligation when successful. It is also typically faster and less expensive than full court proceedings.

Spanish court proceedings become necessary — sometimes urgently so — in several situations. First, where the registrant has already filed court proceedings to challenge the UDRP outcome: at that point the court track is not a choice but a requirement, because the UDRP's own rules defer to judicial outcomes. Second, where there is evidence the registrant is attempting to transfer the domain — to a new registrar, to a nominee, or out of the .es zone entirely — in order to frustrate enforcement. Third, where the harm is ongoing and significant: a domain impersonating your brand in active commerce cannot wait for a six-month administrative process. Fourth, where you also seek monetary damages, which no UDRP or ADOMAIN proceeding can award.

Consider a parallel scenario: a .com domain and a .es domain both registered by the same bad actor. The .com you recover through the UDRP at WIPO, with the registrar complying promptly. The .es stalls. That asymmetry is common. It does not mean the UDRP was wrong for the .com — it means the .es needs its own track, and that track has a different starting point, a different legal test, and a different enforcement lever.

In a recent matter (a .es brand-registry domain, autumn 2024), the registrant filed a Spanish declaratory action within days of the UDRP implementation window opening, seeking to have the domain declared lawfully held. We coordinated with local litigation counsel in Spain to file a cross-application for interim domain lock within the same proceedings. The UDRP panel decision and the documented bad-faith evidence formed the core of the court submission. The interim lock was granted while the underlying merits were argued — preventing the registrant from moving assets out of the zone.

Step 4 — Pursue registrar-change lock and AUTHINFO revocation

While court or ADOMAIN proceedings are pending, a parallel technical track must run: ensuring the domain cannot be quietly transferred to a different registrar to escape the enforcement obligation. Under EPP (the standard registry protocol), a domain transfer between registrars requires an AUTHINFO (authorization) code. The current registrar holds that code. If the registrar supplies it to the registrant — even during an enforcement dispute — the domain may be transferred to a new registrar with no existing obligation to comply with the UDRP order.

The trap in Step 4: assuming the registrar lock displayed in the WHOIS/RDDS record protects you. Registrar locks have multiple levels. A "clientTransferProhibited" status prevents transfer without the registrar's active cooperation — but if the registrar is already non-compliant with the UDRP order, relying on that lock is insufficient. A "serverTransferProhibited" status, set at the registry level, offers stronger protection: it requires Red.es to lift it, not just the registrar.

Request, in writing, that the registrar apply a "serverTransferProhibited" lock and that it not issue the AUTHINFO code pending resolution of the enforcement dispute. Document that request. If the registrar refuses or fails to respond, that refusal becomes additional evidence of non-compliance and strengthens both your ICANN complaint and any court application. Where Red.es has been engaged through the ADOMAIN track, a formal request to Red.es to apply a registry-level lock is appropriate and should be made in parallel.

Step 5 — What to do if the domain is transferred before enforcement completes

If the domain is transferred to a new registrant or a new registrar before enforcement completes, the situation does not become permanently unresolvable — but it becomes substantially more complex. The enforcement obligation does not automatically follow the domain to the new registrar. A good-faith transferee who has no knowledge of the UDRP proceedings may be in a protected position under applicable law, though a transferee who acquired the domain with knowledge of the pending dispute is not.

Where the registrant transferred the domain as a deliberate act to frustrate enforcement, that conduct itself is relevant to several remedies. Under applicable national anticybersquatting rules and general IP law, a transfer designed to circumvent a valid dispute outcome may constitute an independent wrong. Spanish IP courts have general authority to unwind transfers made in bad faith, and the documentation you have built through Steps 1 to 4 — the registrar correspondence, the non-compliance timeline, the WHOIS snapshots — is directly relevant to that claim.

If the domain has moved to a new registrar that IS ICANN-accredited and the domain remains in the .es zone, filing a new ADOMAIN proceeding against the new registrant — supported by the original UDRP record — is often the fastest recovery route. Red.es administers the namespace regardless of which registrar holds the domain at any given moment.

The longer-term lesson: preventive registry-level lock (Step 4) is not optional. In every enforcement matter involving a potentially non-compliant registrar, we apply for registry-level protections at the same time as the first formal escalation letter. Waiting to see whether the registrar complies voluntarily before protecting the domain is the single most common mistake we see in enforcement cases.

Related at COGNOMEN

• Court recovery and domain theft — when arbitration cannot reach the problem
• How to recover a hijacked domain: the full process explained
• UDRP versus national ccTLD procedures — choosing the right track

Author: Adrian Harland — Court anticybersquatting and domain theft recovery. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.