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

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

A panel has ruled in your favor. The decision orders transfer of a .au domain. Yet days pass, then weeks, and the registrar has not moved the name. This situation is rarer than it sounds – but when it occurs, it is acutely damaging. Every day of delay is another day the registrant, or whoever currently controls the domain, can redirect traffic, scrape inbound inquiries, or simply hold the name hostage while you exhaust administrative options.

To enforce a UDRP decision a registrar will not implement for a .au domain, a complainant's fastest lever is a direct escalation to the registry authority – auDA, the .au domain administration – which can compel registrar action independently of the registrar's cooperation. Where that escalation fails, or where the underlying domain is a .com.au or .net.au with a contested chain of title, a court application in the relevant Australian jurisdiction is the next route. The auDRP (Australia's adaptation of the UDRP) governs .au disputes; its bad-faith limb has been read in some respects as "registered or used" rather than the UDRP's cumulative standard, a distinction that can affect the strength of the enforcement posture. Legal fees for court-based enforcement are substantially higher than arbitration fees and are billed at an hourly rate; the decision whether to proceed should be made with full knowledge of that cost basis.

This page explains the registrar-non-implementation problem, the step-by-step escalation sequence in the .au zone, the evidence needed, the court route, and the realistic next step for each scenario.

Why Does a Registrar Fail to Implement a .au auDRP Decision?

Non-implementation is almost always procedural, not defiant – but the effect on the prevailing party is the same either way. The most common causes in the .au zone are: (1) a technical lock applied by the registrant immediately before or after the decision, preventing outbound transfer; (2) a competing legal claim notified to the registrar after the decision was issued, which the registrar treats as a reason to pause; (3) an alleged account compromise that the registrar is investigating; and (4) simple administrative delay or error at the registrar level.

auDA's dispute policy and the auDRP rules impose an obligation on the registrar to implement a valid transfer order. The registrar is not a neutral bystander once a decision issues. If a registrar treats a baseless third-party claim as sufficient reason to suspend implementation indefinitely, that registrar is arguably in breach of its registrar accreditation agreement with auDA. That breach point is the foundation of the escalation strategy described below.

What makes the .au zone distinct from a standard .com non-implementation? The ccTLD layer. auDA has direct contractual authority over every accredited .au registrar. That authority does not exist in the gTLD space in the same direct way. A complainant who wins an auDRP decision and faces a non-implementing registrar is therefore not limited to a court action – the registry channel is available and should be used first.

How Does the auDRP Differ From the Standard UDRP?

The auDRP closely tracks the three UDRP elements under Paragraph 4(a) – confusing similarity, no rights or legitimate interests, and bad faith – but with nuances that matter at the enforcement stage. Specifically, the bad-faith limb under the auDRP has been treated in some decisions as satisfied by registration or use in bad faith, rather than requiring both concurrently as the UDRP consensus position demands. That reading does not change the panel's decision once issued, but it bears on whether a court reviewing the underlying claim would see the same strength of legal ground.

The .au zone also imposes additional eligibility requirements on registrants – a connection to Australia through an Australian Business Number, a registered company, or a registered trademark in Australia. A registrant who held the domain through a fraudulent eligibility claim has less ground to resist enforcement in court. We regularly review eligibility records when advising complainants on whether a court application to compel transfer is likely to succeed.

The distinction between .com.au, .net.au, and .au (the new direct-registration second-level) also matters. Procedures are broadly uniform under auDA's rules, but the chain-of-title analysis and the specific registrar agreements differ. Any court application must be targeted at the correct registrar entity and must identify the correct registry record.

For an assessment of your domain dispute – including whether auDA escalation or a court application is the right next step – contact info@cognomenlaw.com.

What Is the Step-by-Step Enforcement Sequence for a Non-Implementing Registrar?

Enforcement proceeds in three tiers. Skipping a tier is rarely worth the cost premium; completing each tier creates an evidentiary record that supports the next.

Tier 1 – Formal registrar demand. A written demand to the registrar, citing the decision reference, the transfer obligation under the auDRP rules, and a specific compliance deadline of 10 business days, is the mandatory first step. The letter should attach the decision, the registry record confirming the complainant's winning status, and a screenshot of the current domain status. Most registrars act at this stage. The ones that do not usually cite one of the four causes listed above.

Tier 2 – auDA escalation. If the registrar does not comply within the stated deadline, a formal complaint to auDA's compliance team is the next step. auDA has the authority to direct a registrar to implement a valid decision and, in serious cases, to initiate accreditation review. The escalation letter to auDA should attach all correspondence with the registrar, the decision itself, and a brief chronology. In our practice, auDA escalation resolves most non-implementation problems that survive the Tier 1 demand. The authority of the ccTLD registry over its registrars is a genuine operational lever that has no equivalent in the gTLD space.

Tier 3 – Court application. Where Tier 2 does not produce compliance – or where a competing legal claim has been filed in a court that stays the registrar's hand – a court application in the relevant Australian jurisdiction is the appropriate route. The application seeks an order compelling the registrar to execute the transfer, or in some circumstances a declaration confirming the complainant's entitlement to the domain. This is handled with local litigation counsel in the relevant Australian jurisdiction. Legal fees at this stage are substantially higher than the two preceding tiers and are billed at an hourly rate; the realistic cost range should be assessed before filing.

What Evidence Decides the Outcome at Each Tier?

The panel has already ruled – the merits are established. At the enforcement stage, the evidentiary battle shifts to why the registrar has not acted and whether any competing claim is legally colorable.

The core evidence package for Tiers 1 and 2 consists of: the auDRP decision document (certified copy); the WHOIS or RDDS record showing no transfer has occurred; all registrar correspondence; any lock or status flags applied to the domain after the decision issued; and, if relevant, any screenshots showing the domain is still being used by the registrant in a manner inconsistent with the transfer order. That package is assembled once and updated as each tier proceeds.

For a court application, two additional categories matter. First, evidence of the registrar's specific obligation – the relevant clause of the registrar accreditation agreement with auDA, and the equivalent provision of the auDRP rules imposing the transfer duty. Second, if a competing claim has stayed the registrar's hand, the complainant must be able to show the court that the competing claim is not supported by a colorable legal basis, or at minimum that the balance of convenience favors immediate transfer pending resolution of that claim.

Account compromise adds a layer. If the registrant argues the domain was transferred to a third party through unauthorized access after the decision issued, the registrar may freeze all action pending its own investigation. In that scenario, the complainant should obtain a certified RDDS history showing the registration event, identify any unauthorized nameserver changes, and, if possible, obtain a report from auDA's RDDS showing the pre-compromise status. We have assembled exactly this type of evidence record in previous enforcement matters.

What the evidence record must never do is assume the panel's job is complete. A court is not bound by the auDRP decision; it will hear the merits if a genuine dispute is raised. A complainant who arrives in court with nothing more than "we won the arbitration" is not prepared. The full factual and trademark record must be ready to deploy.

When Does a Court Route Beat the auDRP Arbitration Path?

The right route depends on the zone, the goal, and the specific obstacle. Consider the following scenarios.

If the domain is a .com.au and the registrar has simply failed to act without citing any competing claim, Tier 2 auDA escalation is the fastest path. A court application for the same result would take weeks longer and cost significantly more. The escalation channel exists precisely for this situation.

If a third party has filed a court claim in an Australian court and served the registrar with notice of that claim, the registrar may be legally constrained from transferring the domain until the court resolves or dismisses the competing claim. In this scenario the complainant should consider joining that proceeding or bringing a separate application for an interlocutory order. The balance of convenience typically favors the party with a valid arbitration decision in hand, though no outcome is guaranteed.

If the domain is a .au (direct registration, the newer second-level namespace) and the registrant has filed for insolvency after the decision issued, the domain may be treated as an asset of the insolvency estate. A court application in that scenario requires coordination with the insolvency proceeding and should involve local litigation counsel with insolvency experience in addition to domain expertise.

If the dispute spans both a .com.au and a .com, a different problem applies: the UDRP decision on the .com does not bind the .au registrar, and the auDRP decision on the .com.au does not bind the .com registrar. Two separate implementation tracks run in parallel. Coordination between them – particularly on timing, so that neither registrar uses the other's delay as a reason to pause – is a material practical issue. We have managed parallel-zone enforcement tracks in this region and advise structured written sequencing to prevent the gap from widening.

In a recent matter (a .com.au enforcement dispute, early 2026), we escalated a non-implementing registrar to auDA within fourteen days of the decision issuing, secured written confirmation from auDA of its direction to the registrar, and achieved transfer within three weeks of the original decision. The registrant had applied a registrar lock post-decision; the auDA direction cut through that obstacle without a court filing.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. To weigh auDA escalation against a court application for your case, email info@cognomenlaw.com.

What Are the Cost Structures for Each Enforcement Route?

Transparency on fees is a practical requirement at the enforcement stage, where the complainant has already incurred costs in the arbitration and is assessing whether continued pursuit is justified.

Tier 1 and Tier 2 – the registrar demand and auDA escalation – are document-intensive but not hearing-intensive. Legal fees for these steps are at the lower end of the hourly billing range and are typically completed within a few days of billable time. The registrar bears no filing fee at this stage; the cost is purely legal time.

A court application carries materially higher fees. Preparation of the originating process, the supporting affidavit, and any interlocutory application requires significantly more time than the arbitration filing itself. Court filing fees in Australian jurisdictions vary by court and by the relief sought; they are modest by international standards but add to the total. Legal fees at the court stage are billed hourly and should be budgeted as a four-figure minimum for a straightforward uncontested application and higher if the registrant or a third party contests.

The relevant comparison is always cost of enforcement against value of the domain. For a domain with substantial brand or commercial value, even court-level fees are proportionate. For a domain of modest intrinsic value, the answer may be different – and we will say so clearly rather than recommend a course of action that does not serve the client's interests.

One cost-reduction option worth knowing: if the court application is uncontested and the documentation is clean, some Australian courts can deal with it on the papers without a hearing. That reduces the time and fee substantially. The availability of that procedure depends on the specific court and the nature of the relief sought.

How Does This Compare to Enforcement for .com and Other gTLD Decisions?

The .au enforcement path has a structural advantage over gTLD enforcement: the ccTLD registry layer. When a UDRP decision on a .com is not implemented, the complainant's options are (a) wait and escalate through ICANN's formal processes, which are slow, or (b) go to court. The registry for .com has no direct relationship with the complainant in the way auDA does with parties in the .au zone.

For a .com non-implementation, ICANN's Compliance team can be contacted, but the process is slower and less directly targeted than an auDA escalation. Court in the US or the registrar's home jurisdiction is often the practical next step for a non-implementing .com registrar. Legal fees are at least comparable to the Australian court route, and the cross-border dimension adds complexity.

For .eu non-implementation, the EURid / ADR.eu framework has its own enforcement mechanics, including the possibility that EURid itself can revoke a domain that a registrar fails to transfer after a valid ADR decision. The .eu remedy can also include revocation rather than transfer, which is structurally different from the .au position. We handle .au and cross-zone enforcement as connected matters where both zones are affected.

For .uk Nominet DRS decisions, Nominet as the registry has direct authority to implement a transfer and does so routinely after a valid expert decision, which largely eliminates the non-implementation problem in that zone. The .au zone is closer to the .uk model – registry authority is real and exercisable – than to the gTLD model.

In another recent matter (a cross-zone enforcement involving both .com.au and .net.au, autumn 2025), the registrant had allowed both domains to fall into an account-compromise dispute after the auDRP decision issued. We coordinated registrar escalation, an auDA complaint, and a parallel RDDS-history review for both domains simultaneously, achieving transfer of both within approximately six weeks without a court filing.

Related at COGNOMEN

• Court action and domain theft recovery – the full service range
• FAQ: enforcing a UDRP decision through the app process
• FAQ: reversing an unauthorized domain transfer in the .eu zone