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

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

A UDRP panel orders transfer. The registrar does not act. For domains in the .au zone, that gap between a decision on paper and a domain in hand is not hypothetical – it is a recurring problem with its own procedural logic, and recent developments in the auDRP and Australian registry practice have shifted how that problem is solved.

Enforcing a UDRP-style decision against a non-compliant registrar for a .au domain requires moving outside the arbitration channel entirely. The auDRP – Australia's adaptation of the UDRP – applies the same three-element test as the global policy, but implementation authority rests with the registrar and, ultimately, with .au registry mechanics. Where a registrar fails or refuses to act, the practical route is court action combined with registrar-lock escalation and documented evidence of the registrar's non-compliance.

This alert sets out what changed, who is affected, and the immediate next step.

What Changed in .au Enforcement Practice

The .au domain space underwent a consolidation in recent years, with auDA – the .au Domain Administration – tightening eligibility and registrar compliance obligations. That consolidation affected how transfer orders are processed after a decision. Registrars operating under the updated auDA framework carry clearer obligations to implement a valid dispute-resolution outcome. Where they still fail to act, the evidentiary record of that failure now carries more weight in court proceedings, because the registrar's duty is better-documented in the current rules.

Separately, the auDRP itself reads the bad-faith limb with some flexibility compared to the global UDRP standard. Panels have treated the bad-faith element in certain respects as capable of being satisfied by use alone, even where registration intent is harder to prove. That nuance matters for complainants who secured a transfer order but now face a registrar unwilling to implement it – the underlying decision may rest on a slightly different factual foundation than a .com UDRP, and any court application to enforce it must reflect that.

Who Is Affected by These Developments

Three groups are directly in scope. First, brand owners who have already obtained an auDRP transfer decision and are waiting on a registrar to implement it. Second, complainants whose cases are pending and who need to understand the enforcement backstop before they invest in a filing. Third, registrants who received a decision against them and whose registrar is being pressured to transfer – the same mechanics apply in reverse, and a registrar's delay can create a window to seek a stay or to pursue further relief.

For any party in the first group, the clock matters. Registrar inaction is not indefinite; auDA oversight creates a formal escalation path, but that path has its own timelines and requires a documented paper trail from day one.

To weigh your options for enforcing an auDRP decision or escalating registrar non-compliance, email info@cognomenlaw.com.

What to Do Now

The immediate steps follow a clear sequence. Document the decision and the date it was issued. Send formal written notice to the registrar referencing the decision and the auDA implementation obligation. Record every response – or non-response. If the registrar does not act within a reasonable period, escalate to auDA directly, citing the documented non-compliance. If auDA escalation does not produce implementation, the next step is court action in the relevant Australian jurisdiction, handled with local litigation counsel, seeking an order directed at the registrar as the party in control of the registration record.

Evidence of account compromise – where the underlying dispute involves a stolen or hijacked domain rather than a straightforward transfer order – strengthens the court application considerably. Access logs, registrar account records, and prior WHOIS/RDDS data showing the legitimate registrant's control are the documents to assemble before any court filing.

The decision on whether to pursue the arbitration-plus-escalation route or go directly to court depends on the registrar's responsiveness, the age of the decision, and the commercial urgency of the domain. In our practice, we assess those factors before recommending which path to take, because a failed escalation attempt that produces no response from the registrar is itself useful evidence in a subsequent court proceeding.

Related at COGNOMEN

• Court action and domain theft recovery – when arbitration is not enough
• How to enforce a UDRP decision for a .io domain where implementation stalls
• Filing a UDRP complaint for a .com – frequently asked questions