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

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

You won. The panel issued a transfer order, and the domain should have moved to your account. Then nothing happened. The registrar — whether based in Canada or abroad — has not acted, has responded with silence, or has cited a technical or procedural reason for the hold. For .ca domains, that silence is not the end of the road. It is the beginning of a second, more targeted proceeding.

To enforce a UDRP decision a registrar will not implement for a .ca domain, you have two primary paths: an escalation through CIRA's CDRP framework and, where that channel does not produce movement, a Canadian court action to compel transfer. The governing body for .ca is the Canadian Internet Registration Authority (CIRA), which operates its own Canadian Domain Name Dispute Resolution Policy (CDRP) — a procedure distinct from the UDRP and carrying its own Canadian Presence Requirements. Where a registrar's failure stems from account compromise or domain theft rather than ordinary non-compliance, the route shifts to registrar-lock escalation and transfer reversal, handled with local litigation counsel in the relevant jurisdiction.

This page covers the registrar-compliance mechanics, the CIRA CDRP rules that govern .ca, the court route that applies when arbitration cannot reach, and the evidence that decides whether enforcement succeeds.

Why Does a Registrar Refuse to Implement a UDRP Decision for a .ca Domain?

A registrar's failure to implement a transfer order is rarer than it sounds, but it does occur — and for .ca domains the reasons are more varied than in the standard .com context. The UDRP binds accredited registrars through their agreement with ICANN. However, .ca operates under CIRA's registry rules, and a .ca registrar is accredited by CIRA, not solely by ICANN. That dual structure creates gaps.

The most common reasons for non-implementation fall into four categories. First, the registrar may be disputing whether the panel had proper jurisdiction over a .ca registration — the UDRP does not natively govern .ca, and CIRA's CDRP is the correct forum for that zone. A transfer order issued under the UDRP against a .ca domain is therefore legally weaker than one issued under the CDRP. Second, the registrar may be locked out of the account due to a technical hold — either a court-ordered freeze, a registry-level CIRA lock, or a hold triggered by a prior dispute flag. Third, the domain may have been transferred to a different registrar before or during the proceeding, routing the order to an entity that was never served. Fourth, and most serious, the underlying registration may have been compromised: a hijacking or account takeover means the registrar itself may not know who controls the account, and it will freeze the domain rather than transfer it.

In our practice, we distinguish sharply between these four scenarios at the outset. The route, the timeline, and the cost differ substantially depending on which problem is actually in front of you.

What Is the CIRA CDRP, and How Does It Differ From the UDRP for .ca Enforcement?

CIRA's Canadian Domain Name Dispute Resolution Policy (CDRP) is the governing dispute procedure for .ca domains, and it is not the UDRP. Understanding the distinction is essential before pursuing enforcement. A complainant who obtained a UDRP transfer order against a .ca domain without proceeding under the CDRP may find that order unenforceable at the registrar level — because the registrar's CIRA accreditation does not bind it to UDRP outcomes for a zone it holds under Canadian registry rules.

The CDRP test centers on bad-faith registration of a name confusingly similar to a mark or personal name in which the complainant has prior rights. Critically, the complainant must also meet CIRA's Canadian Presence Requirements: to hold a .ca domain, the transferee must qualify as a Canadian Presence — a Canadian citizen, permanent resident, corporation, registered trademark owner, or other eligible category under CIRA's published criteria. If you won a UDRP on a .ca and the registrar is resisting, the first diagnostic question is whether the UDRP or the CDRP was used. If the UDRP was used, a fresh CDRP filing may be necessary — an uncomfortable reality, but one that resolves the compliance impasse cleanly.

The CDRP is administered by the British Columbia International Commercial Arbitration Centre (BCICAC) and the Resolution Canada arbitration service. The procedure follows a single-arbitrator model for most cases and generally runs within a comparable window to the UDRP — typically a matter of weeks for an uncontested matter, somewhat longer if the respondent participates. Official fees are governed by the arbitration service's published tariff; verify current fees with the administering body or with counsel, as CIRA's published schedule updates periodically.

If you obtained a transfer order that the registrar has not implemented, contact info@cognomenlaw.com to assess whether the CDRP is the correct next step or whether a court route is faster.

How Do Registrar-Lock Escalation and Transfer Reversal Work for .ca?

When a domain is frozen — whether by a CIRA-level registry lock, a registrar hold, or an account-compromise flag — the transfer order cannot be executed until the lock is lifted. Lifting it requires a separate escalation track that runs in parallel with, or prior to, any formal dispute proceeding.

The registrar-lock escalation process for .ca follows a sequence. The first step is a formal written demand to the registrar's compliance team, citing the panel decision and the CIRA accreditation terms that bind the registrar to honor valid transfer orders. The demand should include the full case record: the commencement notice, the decision itself, and any WHOIS or RDDS data confirming the current registration status. If the registrar does not respond within a defined window — typically five to ten business days for an escalated compliance request — the next step is a referral to CIRA's registrar-management process, which can impose sanctions on non-compliant CIRA-accredited registrars.

Transfer reversal — the separate scenario where a domain was hijacked or stolen — is more urgent and more technically specific. An account compromise means someone obtained access to the registrant's account, changed the registrar-of-record WHOIS data, and either transferred the domain out or locked the legitimate owner out of the account. In that scenario, the priority is a registrar-level account-freeze request, submitted with evidence of the account compromise: login logs, email-header forensics, authentication records, and a sworn statement of the compromise timeline. CIRA can also place a registry-level hold on a .ca domain pending resolution of a verified hijacking claim.

In a recent matter — a .ca domain, winter 2025 — we coordinated a registrar escalation and a parallel CIRA contact for a Canadian brand owner whose domain had been transferred to a foreign-accredited registrar following a credential compromise. The domain was frozen at registry level within days of the escalation, halting further unauthorized transfers while the evidence record was assembled.

When Does a Court Route Beat the CDRP for .ca Enforcement?

The CDRP and the registrar-escalation path resolve the large majority of .ca enforcement problems. But there are specific situations where a Canadian court action is the faster or more effective route — and a practitioner advising a brand owner on enforcement needs to identify those situations early, not after a failed arbitration.

A court route is generally preferable — or necessary — in four circumstances. First, when the domain is being actively used to harm the complainant in real time: diverting customer traffic, processing payments under a confusingly similar name, or hosting counterfeit goods. A court can issue an interim injunction within days; the CDRP cannot. Second, when monetary compensation is sought alongside the domain transfer. The CDRP, like the UDRP, awards only transfer or cancellation — no damages. Canadian anticybersquatting litigation before the appropriate court can reach financial remedies. Third, when the registrar is non-compliant despite a CDRP transfer order and the CIRA registrar-management process has not produced movement: at that point, a court order directed at the registrar is the only enforcement mechanism with teeth. Fourth, when the respondent is a sophisticated actor who will litigate — in which case the full evidentiary process and cross-examination available in court may produce a stronger result than an arbitral record.

Court action for .ca enforcement is handled with local litigation counsel in the relevant Canadian jurisdiction — typically British Columbia, Ontario, or wherever the respondent or registrar is located. COGNOMEN structures the strategy, assembles the evidentiary record, and coordinates the court filing with counsel qualified in the applicable Canadian court system.

If the CDRP result has not been implemented and a court order may be required, email info@cognomenlaw.com to weigh the options for your specific situation.

What Evidence Decides Whether .ca Enforcement Succeeds?

Whether the enforcement route is a fresh CDRP filing, a registrar escalation, or a court action, the evidence assembled at the outset determines whether the process moves quickly or stalls. In our experience, the cases that stall do so because the complainant arrives at the enforcement stage with the original UDRP decision and nothing else.

The core evidentiary package for .ca enforcement should contain the following elements. The original dispute record — complaint, response if filed, decision, and any communications from the prior arbitration — establishes the factual baseline. Current WHOIS and RDDS data from CIRA's registry confirms the current registrant of record, the current registrar, and any lock or hold flags. The Canadian trademark registration (or other qualifying rights document) confirms Canadian Presence eligibility, which is a threshold requirement for a CDRP or a court-based transfer claim. Any evidence of the domain's current use — screenshots of the website, traffic-diversion records, customer complaints — supports both urgency and bad-faith arguments. If account compromise is alleged, the forensic evidence of the compromise: server logs, email authentication headers, account-recovery request records.

For the CIRA registrar-escalation track specifically, the most important single piece of evidence is a comparison of the WHOIS records before and after the alleged non-compliance or compromise event. That comparison, combined with the registrar's accreditation record at CIRA, defines the scope of the registrar's obligation and the basis for a CIRA sanction referral if the registrar remains non-compliant.

In a second matter — a .ca registration held by a foreign shell entity, spring 2025 — we assembled a CDRP complaint supported by a Canadian trademark registration, registry-data forensics, and a chain-of-WHOIS analysis covering approximately eighteen months of registration history. The arbitrator issued a transfer order within the expected window, and CIRA implemented it without registrar resistance, because the evidence package left no factual gap for the registrar to cite.

What Are the Realistic Costs and Timelines for .ca Enforcement?

Enforcement costs for a .ca domain vary significantly depending on the route. A registrar-escalation-only track — where the registrar simply needs a formal demand and a CIRA contact to comply — is the least expensive path. It involves legal time for the demand letter and the CIRA referral, with no filing fee, and can resolve in days to a few weeks.

A fresh CDRP filing adds official arbitration fees governed by the administering body's published tariff — verify current fees directly with BCICAC or Resolution Canada, as the schedule is subject to change. Legal fees for a straightforward CDRP complaint follow market ranges broadly comparable to a standard UDRP complaint; more complex matters with a participating respondent will be higher. The CDRP timeline for an uncontested or lightly contested matter runs in the same general range as a UDRP — weeks for a simple case, somewhat longer for a contested one.

A Canadian court action is substantially more expensive and slower than either arbitration or escalation. Interim injunction applications can be heard on short notice in urgent cases, but the overall litigation timeline extends to months, and legal fees are hourly and jurisdiction-specific. Court action is the right tool when the value of the domain or the harm from ongoing misuse justifies that cost — and in our practice, we are direct with clients about when it does and does not.

A decision matrix helps frame the choice. If you have a clean CDRP award and the registrar is simply slow or unresponsive, escalation is the first move — low cost, targeted, often sufficient. If the underlying dispute was decided under the UDRP and the .ca registrar is correctly noting it has no obligation under that policy, a CDRP filing is the correct next step, with a realistic timeline of weeks and costs comparable to the original proceeding. If the domain is being actively misused and you need immediate relief, a court injunction application in the relevant Canadian province is the tool, with escalation running in parallel. If the registration was a result of account compromise, the forensic-evidence package and the CIRA freeze request come first, before any formal proceeding.

How Does .ca Enforcement Compare to gTLD and Other ccTLD Enforcement?

The .ca enforcement problem is structurally different from the same problem in .com, .eu, or .uk — and conflating the procedures produces costly delays.

For .com and other ICANN-accredited gTLDs, the UDRP directly binds the registrar, and a WIPO or Forum transfer order triggers an automatic implementation hold period. If the registrar does not act after that period expires, ICANN's compliance channel is the escalation route. There is no separate Canadian presence requirement, and the policy is uniform across all ICANN-accredited registrars worldwide.

For .uk, Nominet's DRS governs, with its own implementation mechanics tied directly to Nominet as the registry — registrar non-compliance is effectively a Nominet-level problem, and Nominet has direct authority to implement a transfer without registrar cooperation in cases of clear non-compliance.

For .eu, the ADR.eu procedure at the Czech Arbitration Court governs, and the EURid registry implements transfer orders directly where EU eligibility is confirmed.

The .ca situation sits between these models. CIRA is the registry and has implementation authority, but the registrar's cooperation is still required in practice for the transfer mechanics. The Canadian Presence Requirement adds a threshold eligibility check that does not appear in most other ccTLD systems. And the absence of a native UDRP obligation means a prior gTLD-style arbitration award does not carry automatic weight at a .ca registrar. These distinctions matter operationally, not just theoretically.

If your enforcement problem spans both a .com and a .ca — a common scenario for Canadian brands targeted across zones — the two proceedings run under different policies, different forums, and different registrar obligations, and they must be managed on separate tracks simultaneously. We regularly advise on multi-zone enforcement where the complainant holds transfer orders in one zone and is building toward the equivalent in another.

Related at COGNOMEN

• Court action and domain theft recovery — full service overview for gTLD and ccTLD disputes
• Registrar-lock escalation for .biz — when and how to force compliance after a dispute decision
• Domains registered before a trademark — analysis of the evidentiary challenge across zones