Update: changes affecting how to enforce a UDRP decision a re… (.co 2)

Update: changes affecting how to enforce a UDRP decision a re… (.co 2). UDRP and ccTLD domain recovery and defense across .co. Email the firm to assess your ca…

A UDRP panel orders transfer. The registrar does not move. For .co domain holders and brand owners relying on WIPO proceedings, that gap between a written decision and an actual transfer is not hypothetical – it is a practical risk that has become more visible in recent disputes involving the .co zone.

When a registrar fails or refuses to implement a UDRP transfer order for a .co domain, the winning complainant must pursue enforcement through an alternative route: escalation to the registry operator, direct registrar pressure, or court action in the relevant jurisdiction. All three UDRP remedies – transfer, cancellation, and suspension – depend on registrar cooperation; without it, the panel decision has no self-executing force. The practical response turns on whether the registrar is unresponsive, actively obstructing, or itself a party to the compromise.

This update covers what changed, who is affected, and the realistic next step for any party holding a UDRP award that a .co registrar will not act on.

What Changed and Why It Affects .co Domain Disputes

.co operates under Colombian registry authority, and WIPO serves as a dispute-resolution provider for the zone. That means a UDRP complaint over a .co domain follows the standard Policy – including Paragraph 4(a)'s three-element test and Paragraph 4(b)'s bad-faith factors – and the decision is formally addressed to the registrar of record. The registrar is contractually obligated to implement a transfer or cancellation order. Recent experience shows that obligation is not always honored promptly, or at all, when the registrar is a low-tier or less-regulated provider, when the domain has been transferred during the proceedings to a new holder, or when the account was compromised before or during the dispute. Each scenario requires a different enforcement path, and the path is not described in the UDRP Rules themselves.

The practical exposure here is real. A complainant who spent months building a three-element case – assembling confusing-similarity evidence, rebutting any legitimate-interest argument, and documenting bad-faith registration and use – can find the transfer order sitting unimplemented while the registrant continues to benefit from the domain. That outcome is not an acceptable end to a UDRP proceeding.

Who Is Affected by a Non-Implementing Registrar in the .co Zone?

Brand owners who have already won a UDRP decision over a .co domain are the most directly affected. So are parties mid-proceeding who have identified signs that the registrar may not cooperate post-decision – for example, a registrar that has already changed the registration record or failed to lock the domain at commencement. Registrants defending a claim are affected differently: if a transfer is wrongly implemented despite a pending appeal or a legitimate-interest defense, the same enforcement mechanics work in reverse to seek a reversal.

In our practice, we have seen both sides of this problem. A complainant with a clean three-element win faces a functionally useless award. A registrant with a valid defense sees a transfer they never consented to. The zone is the same; the mechanics differ.

What Are the Enforcement Routes When a Registrar Will Not Implement?

Three paths exist, and the right choice depends on the specific obstacle. First, escalation to the registry operator – in .co's case, the entity administering the zone – can pressure the registrar through its accreditation obligations. This is faster than litigation and should always be attempted first. Second, direct registrar escalation through formal written demand, copied to the registry and to ICANN's Contractual Compliance function, puts the registrar on notice that its accreditation is at risk. Third, and most reliably when the first two fail, court action in the registrar's jurisdiction can compel implementation or independently order transfer under applicable anticybersquatting or civil procedure rules.

Where the non-implementation flows from an account compromise – the registrant's WHOIS/RDDS credentials were taken, the domain was moved, and the original registrant is now a stranger to the record – the evidence of compromise becomes the foundation of every subsequent step. Registrar logs, authentication records, timestamps of the unauthorized transfer, and any correspondence with the registrar's abuse desk all form the documentary record. We have handled .co matters where assembling that record within the 20-day response window for a parallel UDRP filing was the only way to preserve the original registrant's position.

If you hold a UDRP transfer order for a .co domain that the registrar has not implemented, or if you are mid-proceeding and already seeing signs of registrar non-cooperation, the time to act is before the decision issues. For an assessment of your domain dispute, contact info@cognomenlaw.com.

What Evidence Decides the Outcome – and What to Do Now

Whether the path is registry escalation, registrar demand, or litigation, the evidence base is the same. The UDRP decision itself is exhibit one. The registrar's communication history – or deliberate silence – is exhibit two. The WHOIS/RDDS record at the time of the decision and at the present moment shows whether a transfer has occurred since the order was issued. If a new registrant appears post-decision, the chain of title is now in dispute and a court action, rather than a registrar demand, is typically required to unwind it.

For .co domains specifically, the cross-border dimension matters. The registry operator, the registrar, and the registrant may each be in a different jurisdiction. A court action filed in the wrong forum may lack personal jurisdiction over the registrar. Coordinating with local litigation counsel in the relevant jurisdiction is essential when the enforcement route moves into court.

The realistic next step for most parties in this situation is a structured escalation: registry notification first, registrar formal demand second, litigation third. Each step should be documented. The decision not to move quickly has a cost – the longer a transfer order sits unimplemented, the more opportunities exist for the domain to change hands again, complicating every subsequent claim.

Related at COGNOMEN

• Court action and domain theft recovery – when arbitration cannot reach
• Guide to enforcing a UDRP decision for a .me domain – step-by-step
• Domain due diligence on .com – chain of title and prior dispute history