How to bring a court action when UDRP cannot reach a .au domain

How to bring a court action when UDRP cannot reach a .au domain. UDRP and ccTLD domain recovery and defense across .au. Email the firm to assess your case.

A cybersquatter registers a .au domain that matches your Australian trademark, points it at a pay-per-click page, and ignores every takedown notice. You know the UDRP applies to .com. Does it reach .au? The honest answer is: not automatically, and not always in the way brand owners expect.

Australia's .au namespace operates under the auDRP – a distinct procedure administered through auDA-accredited providers that closely tracks the three UDRP elements but is not identical to the global UDRP. Where the auDRP fails, is unavailable, or produces an insufficient remedy, a court action under Australian anticybersquatting and trademark law becomes the correct route. The governing national procedure in .au applies, with local litigation counsel in the relevant jurisdiction handling the action in the federal or state courts.

This page identifies when the court route is the right one for a .au domain, what evidence drives the outcome, and how to begin.

Why the UDRP does not automatically cover .au domains

The global UDRP applies to domains registered under gTLDs (.com, .net, .org, and others) and to ccTLDs that have separately adopted it. Australia's .au Registry authority – auDA – has not adopted the standard UDRP. Instead it has implemented the auDRP, a locally adapted version with its own rules, its own accredited providers, and its own eligibility requirements for both complainants and registrants.

That distinction matters practically. A brand owner who has filed dozens of UDRP complaints against .com typosquats cannot simply replicate that process for a .au domain. The procedural rules diverge, and – critically – the bad-faith limb in the auDRP is sometimes treated as reading "registered OR used" abusively in certain respects, which is a lower cumulative bar than the UDRP's strict "registered AND used in bad faith." Treat any element-level nuance of the auDRP qualitatively; confirm current rules with counsel before relying on procedural specifics.

Where does this leave a brand owner whose .au domain is abusively held? If the auDRP procedure is available and the fact pattern fits, it is usually the faster route. But three situations push the analysis toward court action instead: when the auDRP produces no usable remedy, when the domain was acquired through theft or account compromise rather than straightforward cybersquatting, and when the brand owner needs damages as well as a transfer order.

When does a court action beat the auDRP for a .au domain?

A court action is the correct route when the auDRP either cannot reach the situation or cannot deliver what the brand owner actually needs. The four most common triggers are set out below.

Domain theft and account compromise. The auDRP is an arbitration procedure for disputes between a complainant with trademark rights and a registrant who obtained the domain through registration. It does not handle the situation where a legitimate registrant's account was compromised and the domain was transferred to a bad actor without the owner's consent. In that scenario – account hijacking, social-engineering the registrar, unauthorized transfer – the proper route is registrar escalation first, then court action if escalation fails. We regularly advise Australian and foreign rights-holders whose .au domains have been taken through credential theft rather than registration: the legal theory is different, the evidence required is different, and the registrar-lock mechanics are the first lever to pull.

Need for monetary damages. The auDRP, like the UDRP, offers only transfer or cancellation. It cannot award damages, costs, or compensation for business disruption caused by the unauthorized use of the domain. Australian court proceedings under the applicable trademark and consumer protection legislation can, in principle, reach a monetary award where losses are pleaded and proven. For a brand owner whose .au site was impersonated for months, the financial exposure may dwarf the value of the domain itself.

Judgment required for enforcement. Some situations call for a court order that can be enforced against a registrar or a hosting provider. A UDRP or auDRP decision binds the registry and registrar to implement a transfer, but it is not a judicial order. Where a registrar has been uncooperative, or where a related injunction (for example, against the use of infringing content on the diverted site) is also needed, court proceedings are the appropriate vehicle.

Parallel gTLD and ccTLD abuse. A cybersquatter rarely stops at one zone. A brand owner who finds the same bad actor holding both the .com and the .au version of its name may pursue the .com through the UDRP while the .au is addressed through the auDRP – or through court if the auDRP produces an insufficient result. Coordinating the two timelines, and ensuring that a settlement in one forum does not prejudice the other, requires careful cross-zone planning.

If you are facing a .au domain dispute and are unsure whether the auDRP or a court action is the right path, contact info@cognomenlaw.com for an assessment of the three elements and the realistic options.

How does registrar-lock and transfer-reversal work in a .au dispute?

The registrar-lock mechanism is often the first practical step, regardless of whether the dispute ultimately proceeds through the auDRP or the courts. A domain under a registrar lock cannot be transferred to a new registrant, deleted, or modified while the lock is active. In a theft or hijacking scenario, getting that lock in place before the bad actor moves the domain to a second registrar is critical – once a domain has been transferred out and the registrar changed, recovery becomes significantly more complex.

In a straightforward cybersquatting case – where the registrant obtained the domain through registration, not theft – a lock is typically not the immediate concern. The domain is already registered in the bad actor's name, and the question is whether the auDRP or a court order will compel the registry to transfer it to the rightful owner.

In a theft or account-compromise case, the sequence we advise clients to follow is:

1. Document the compromise immediately: preserve screenshots of the RDDS/WHOIS record before and after the unauthorized transfer, recover account-access logs where the registrar will provide them, and note the exact timestamp of the unauthorized activity.
2. Contact the registrar's abuse or escalation team, citing the unauthorized transfer and requesting an immediate registrar lock on the current registration.
3. If the registrar is uncooperative or the domain has already been moved, contact the registry (auDA for .au) directly, citing the unauthorized transfer and requesting a registry-level lock.
4. If those escalation steps produce no result within a matter of days, or if the domain is being actively used to redirect your customers or intercept your communications, court proceedings for an urgent interlocutory injunction become the appropriate next step.

The speed of steps one through three determines whether a court application is necessary at all. In many account-compromise cases we have handled, prompt and well-documented registrar escalation has reversed an unauthorized transfer without litigation. But where escalation fails, having already preserved the documentary record dramatically shortens the time to a court hearing.

What evidence decides the outcome of a .au court action?

The evidence required for a .au court action differs depending on whether the theory is cybersquatting (bad-faith registration) or theft (unauthorized transfer). Both require a foundation of documentary proof gathered quickly and preserved carefully.

For a cybersquatting claim: the core evidence is your trademark rights (registration certificate, first use, scope of registration), proof that the domain is confusingly similar to your mark, and proof of the registrant's bad faith in obtaining and using the domain. Bad faith can be demonstrated by the content of the site (parking page, pay-per-click links in your industry, competing offers), the registrant's communications (a demand to sell the domain at a price above registration cost is a classic indicator), the timing of registration relative to your brand's launch or trademark filing, and any pattern of similar registrations across multiple domains.

For a theft or hijacking claim: the evidence is more operational. You need to show that you were the prior registrant, that the transfer occurred without your authorization, and that the current holder obtained the domain through a compromise of the registration process. Evidence typically includes: historical RDDS/WHOIS records showing your registration, correspondence with the registrar confirming the unauthorized transfer, account-access logs, and any communications from the party who now holds the domain.

In a recent matter (a .au account-compromise case, autumn 2024), we coordinated the documentary preservation and registrar escalation for a rights-holder whose domain had been moved to an overseas registrar within hours of an account breach. The registrar escalation produced a lock within two days; court proceedings were prepared but not ultimately required. The lesson: evidence gathered in the first 48 hours is the most important evidence in a hijacking case.

For a cybersquatting court action, the timeline is longer. Court proceedings in the relevant Australian jurisdiction follow their own case-management timelines; an urgent interlocutory application can in principle produce interim relief within days, but a final hearing on the merits is typically a matter of months, not weeks. The auDRP, where available, is faster for a straightforward cybersquatting case.

How does a .au court action compare to the auDRP?

The right route depends on the fact pattern, the remedy needed, and whether the auDRP is even available for the dispute. Here is how the comparison works in practice.

If the domain is a .au and the dispute is a straightforward case of bad-faith cybersquatting by a registrant who obtained the domain through registration, the auDRP is usually the faster and less expensive route. It produces a transfer or cancellation order. It does not require Australian courts. Local litigation counsel is not strictly necessary, though guidance on the auDRP filing requirements is advisable.

If the domain was stolen – that is, transferred away from a legitimate registrant without consent – the auDRP is the wrong tool entirely. A court action (or registrar escalation backed by the threat of a court action) is the correct route. The evidence burden is different, the legal theory is different, and the urgency is higher.

If the brand owner needs damages as well as a transfer order, only a court action can provide both. The auDRP, like the UDRP, is remedially limited to transfer or cancellation.

If the dispute involves both a .com and a .au held by the same bad actor, a dual-track approach is often sensible: a UDRP complaint (at WIPO, the Forum, or another accredited provider) for the .com, running in parallel with an auDRP filing or a court action for the .au. The filing fees for a WIPO UDRP single-panel complaint start at USD 1,500; the auDRP and Australian court costs are separate and should be confirmed with local litigation counsel in the relevant jurisdiction. Coordinating the two proceedings – in particular, managing settlement discussions so that resolution of one does not inadvertently waive claims in the other – requires attention from the start.

In a recent matter (a dual-zone dispute, .com and .au, spring 2025), we managed the UDRP filing for the .com while coordinating with local litigation counsel on the auDRP filing for the .au. The .com transferred within two months through the standard UDRP timeline; the .au was resolved through the auDRP in a comparable period. Neither proceeding required court action, but the option was kept open until both decisions were in hand.

For a read on whether a court action or the auDRP fits your .au situation, email info@cognomenlaw.com. We assess the three elements, the evidence, and the realistic timeline before you commit to a route.

What does a .au court action actually cost?

The cost of a court action for a .au domain dispute depends heavily on whether the proceedings are contested, how complex the trademark evidence is, and whether an urgent interlocutory application is needed. Australian court proceedings are handled by local litigation counsel in the relevant jurisdiction; COGNOMEN coordinates the domain-disputes strategy and the cross-zone elements while local counsel manages the court filings.

As a general market reference: uncontested or urgent interlocutory applications are typically less expensive than full contested hearings on the merits. Legal fees for contested Australian IP litigation are substantially higher than for UDRP proceedings; describe qualitatively only, confirm specific ranges with local litigation counsel before proceeding. The auDRP, where available, is materially less expensive than court action for a straightforward cybersquatting dispute.

For a pure account-compromise or theft case where registrar escalation succeeds, court action may not be needed at all. The cost of escalation – primarily the legal work of documenting the compromise and communicating with the registrar and registry – is substantially lower than the cost of litigation.

When weighing cost against remedy, keep the following in mind: the auDRP and the UDRP do not award damages. If the domain has been used to divert your customers, intercept your email, or conduct fraud in your name, the commercial loss may justify the higher cost of court proceedings even if the domain transfer could be obtained more cheaply through arbitration.

What is the cross-border dimension for .au domain disputes?

Many .au domain disputes involve registrants who are not located in Australia. The registrant may be in a different country, the registrar may be offshore, and the domain name may be used to target Australian consumers while the underlying server is elsewhere. This is a common fact pattern in our practice, and it affects both the route chosen and the evidence required.

The auDRP is designed to reach registrants regardless of their physical location, because the dispute resolution clause is part of the registration agreement that every .au registrant accepts. A court action in Australia may face additional complexity if the registrant is outside the jurisdiction – service of process, enforcement of any judgment, and the reach of Australian law all become relevant. Local litigation counsel in the relevant jurisdiction will advise on those specifics.

For foreign brand owners targeting a .au squatter, the auDRP is often the more practical first resort. It does not require the complainant to be physically present in Australia, and it operates on a documents-only basis. A court action for a foreign brand owner against an offshore registrant requires careful planning around jurisdictional service and enforcement before proceedings are commenced.

More than 87 ccTLDs have appointed WIPO as their dispute-resolution provider and effectively use the UDRP or a close variant. Australia's .au is not among them. That means the global UDRP infrastructure a brand owner may be familiar with from .com disputes does not extend to .au, and the assumption that the same complaint template, the same filing process, and the same timeline apply is a mistake that can cost weeks.

Where the same bad actor holds registrations in multiple ccTLDs – say, .au, .uk, and .de – each requires its own procedure: the auDRP for .au, the Nominet DRS for .uk (which offers a free mediation stage before any expert decision), and court proceedings in Germany for .de (since DENIC offers no arbitration procedure equivalent to the UDRP). Managing those three proceedings in parallel, with consistent evidence and coordinated timelines, is precisely the kind of cross-zone dispute work we handle.

Related at COGNOMEN

• Court recovery and anticybersquatting litigation across gTLDs and ccTLDs
• Step-by-step guide to recovering a stolen or hijacked .com domain
• Respondent defense for generic domain names, including RDNH findings