Step-by-step: defend a generic-word .au domain

Step-by-step: defend a generic-word .au domain. UDRP and ccTLD domain recovery and defense across .au. Email the firm to assess your case. Transparent fees, re…

A letter arrives. A brand owner has filed — or threatens to file — an auDRP complaint against a .au domain you registered years ago. The name is a common dictionary word, a geographic term, or a descriptive phrase you chose for its plain meaning. Your first instinct may be to assume you are in a weak position. That instinct is often wrong.

Defending a generic-word .au domain under the auDRP turns on one central question: can the respondent demonstrate a legitimate interest in the name that predates or is independent of the complainant's trademark rights? The auDRP tracks the three elements of the UDRP, with the bad-faith limb reading broadly in some respects — meaning the complainant's burden is real, and a well-prepared respondent can defeat it. The 20-day response window is hard; missing it is the most preventable error in the process.

This guide walks each step of the defense — from reading the complaint to requesting an RDNH finding — and flags the trap concealed at every stage.

What governs a .au domain dispute, and how does it differ from the UDRP?

The auDRP is Australia's adaptation of the UDRP, administered by the .au Domain Administration (auDA). It closely tracks the three elements of Paragraph 4(a): confusing similarity to a trademark, no rights or legitimate interests in the domain, and registration or use in bad faith. That last element matters enormously to respondents. Where the UDRP is cumulative — requiring that the domain was registered AND used in bad faith — the auDRP's bad-faith limb is treated more broadly in some respects, and how panels read that distinction can affect the outcome of your case.

auDA publishes the auDRP Rules and the auDRP Supplemental Rules. Forum-selection under auDRP is handled similarly to the UDRP: the complainant selects a provider from the auDA-approved list. WIPO handles a significant share of these proceedings. Panels are appointed in much the same way as under the UDRP, and the same safe-harbor provisions — Paragraph 4(c)'s three recognized grounds of legitimate interest — are available to respondents. Understanding which version of these provisions applies in the .au context is the first step of any defense, and the place where a poorly guided respondent most often concedes ground they did not need to concede.

One cross-zone consideration is worth stating at the outset. If the same complainant also holds the .com or another gTLD variant, the relevant dispute procedures are separate. A UDRP proceeding for the .com does not bind the auDRP panel, and vice versa. We regularly advise registrants who face parallel proceedings across zones, where strategy in each forum has to be coordinated without being conflated.

For an assessment of whether the auDRP applies to your .au and what your response window is, contact info@cognomenlaw.com.

How do you read the complaint before drafting a response?

The complaint lands — usually by email from the provider — and the 20-day response clock starts running from formal commencement, not from the date you first see it. Before you write a single word of a response, read the complaint analytically. Three questions govern everything that follows.

First: what trademark does the complainant actually hold? A registered trademark in Australia, a CTM covering Australia, a well-known mark under the Paris Convention — each has a different weight. A common-law mark based on use is also cognizable under the auDRP, but the complainant must prove it. Generic or highly descriptive terms are notoriously difficult to protect as trademarks, and panels have consistently held that trademark registrations in descriptive marks do not automatically defeat a respondent's legitimate interest in using the same word in its ordinary sense.

Second: what is the alleged bad faith? Complaints against generic-word domains often rely on circumstantial inferences — the domain was registered shortly after the complainant's brand launch, or it resolves to a competitor's content. If neither is true of your domain, say so specifically and with evidence. A complaint that relies on inference alone is vulnerable.

Third: is the complaint legally or factually thin? Panels may find Reverse Domain Name Hijacking — a formal finding that the complaint was filed in bad faith against a legitimate registrant — where the complainant knew or should have known it could not succeed. An RDNH finding carries no monetary penalty, but it is a reputational sanction against the complainant. We have defended .au domains where RDNH was the appropriate conclusion because the complainant's mark postdated the registration by years. Identifying that possibility early shapes the entire tone and structure of the response.

What are the Paragraph 4(c) safe harbors, and how do you build the record for each one?

The three safe harbors in Paragraph 4(c) are the respondent's primary affirmative tools. Each requires a concrete evidentiary record. Asserting them in the abstract is not enough — panels expect documented facts, and a bare assertion without supporting evidence is treated as no evidence at all.

Safe harbor one: bona fide use before notice of the dispute. If, before you received any notice of the complaint, you were using — or making demonstrable preparations to use — the domain in connection with a genuine offering of goods or services, that use is recognized as a legitimate interest. What does "demonstrable preparations" mean? Internal product plans, domain development logs, hosting records, correspondence with a web developer, business name registrations, or an active website are all usable. The trap here is underestimating how much proof is needed. A parked page with no development history is unlikely to suffice.

Safe harbor two: commonly known by the name. If the registrant is an individual, business, or organization that is genuinely known by the domain name or a name corresponding to it, that fact supports legitimate interest. For a generic word this is harder to establish than it sounds — the registrant must be known by the specific name, not merely by a business that operates in the relevant field. Business registration records, ABN listings, longstanding use in trade, or public directory entries can all contribute to the record here.

Safe harbor three: legitimate noncommercial or fair use. Commentary, criticism, and genuinely noncommercial use are recognized, provided the site does not mislead users as to source or association. A generic informational resource — a site about the word's subject matter — can qualify, but the content must be substantive and the domain must not be designed to intercept the complainant's customers.

In our practice we build the evidentiary file around whichever safe harbor is strongest on the facts, then construct the remaining two as secondary supports where the evidence exists. The trap respondents fall into most often is focusing only on the first safe harbor and ignoring the others, or conversely, claiming all three without documentary support for any of them.

What evidence decides the outcome of an auDRP defense?

Evidence, assembled before the response deadline, is what determines whether a defense succeeds or fails. A compelling legal argument is only as strong as the facts that support it. The following categories are the ones that move panels.

Registration date relative to the complainant's trademark. If your .au registration predates the trademark — the application date, not just the registration date — the bad-faith element becomes very difficult for a complainant to establish. Pull the WHOIS history, the auDA creation date, and the trademark register and set them side by side. We have seen complaints collapse entirely at this step because the complainant overlooked a two-year gap between the domain registration and its own trademark filing.

Domain creation date is the anchor. Renewal does not reset it. Keep that record.

Development and use history. Web archive records (screen captures from archived sources, hosting invoices, analytics exports, email records on the domain), business registration records, and correspondence all document genuine use. The older and more continuous the evidence, the stronger the legitimate-interest argument. Gaps in use are not automatically fatal — panels have accepted dormant domains where the respondent had a plausible forward-looking plan — but unexplained long gaps combined with a generic name pointing at a pay-per-click page are exactly the pattern panels treat as bad faith.

The nature of the generic word itself. Panels have consistently held that a complainant with a registered trademark in a word that is also a common dictionary term faces a higher burden in establishing that the domain was registered with the complainant in mind. Evidence of the word's broad ordinary usage — dictionary definitions, evidence of widespread third-party use in commerce — is admissible and useful. The more parties use the word generically, the less plausible the inference that your registration targeted the complainant.

In a recent matter (a .au generic-word domain, autumn 2024), we assembled a documentary timeline showing the registrant had held the domain for nearly a decade, with uninterrupted hosting invoices and an archived website predating the complainant's Australian trademark by roughly three years. The complaint was denied. The outcome turned on the timeline, not on legal argument alone.

When is an RDNH finding realistic, and how do you seek one?

An RDNH finding is available where a panel concludes that the complaint was brought in bad faith or used to deprive a registrant with legitimate interests of their domain. It is not awarded lightly — panels set a real threshold — but in our experience it is underutilized by respondents who do not ask for it explicitly.

The fact patterns that most reliably produce RDNH findings are well-established in UDRP and auDRP precedent. They include: the complainant's trademark postdates the domain registration and the complainant knew this; the complaint relies solely on trademark rights in a highly descriptive or generic term without additional evidence of targeting; and the complaint was filed after a failed negotiation for purchase, suggesting it was used as leverage rather than as a genuine rights-enforcement proceeding.

How do you seek it? Explicitly. In the response, after addressing each of the three elements, include a standalone section requesting an RDNH finding and laying out the specific facts that support the request. Reference the applicable standard under the auDRP rules. A bare request without factual support fails; a well-constructed argument with documentary backing gives the panel a credible path to making the finding.

One caution: RDNH is not the primary goal of a defense. The primary goal is defeating the transfer order. RDNH is a secondary remedy pursued where the facts warrant it. Do not let the pursuit of RDNH divert resources from the core defense.

What are the practical steps and the trap hidden in each one?

The steps below follow the auDRP procedural sequence. Each carries a specific risk that respondents in generic-word cases commonly encounter.

1. Receive and date-stamp the commencement notice. The 20-day response window runs from the formal commencement date set by the provider. Read the commencement notice carefully — not the complainant's letter to you, but the provider's formal notification. The trap: treating the complainant's demand letter as the start of the clock. The clock starts at formal commencement. Missing the deadline results in a default decision, and default panels overwhelmingly favor complainants.
2. Audit the domain record immediately. Pull the WHOIS history, the auDA creation date, all hosting records, all archived versions of the site, and any business records connected to the domain. The trap: waiting until day fifteen to start gathering evidence. Some records — particularly web archives and legacy hosting invoices — take time to obtain. Start on day one.
3. Identify the strongest safe harbor and build the evidentiary file around it. Map the complainant's trademark registration or use-based claim against your registration date, development history, and current use. The trap: relying on the generic nature of the word alone, without connecting it to a documented legitimate interest. "It's a common word" is a starting point. It is not a defense by itself.
4. Request additional time if genuinely needed. The provider may grant a brief extension for good cause. The trap: assuming an extension will be granted. It may not be. Plan to file within the original window.
5. Draft the response with the three elements in sequence. Address element one (confusing similarity) concisely — it is often not seriously contested. Address element two (legitimate interest) with full documentary support. Address element three (bad faith) by identifying the specific bad-faith theory the complainant advances and refuting it factually. The trap: writing a long narrative that omits direct engagement with the complainant's specific allegations. Panels expect a structured rebuttal.
6. Include the RDNH request where the facts support it. If the complainant's trademark postdates your registration, say so prominently. The trap: burying the RDNH argument in the conclusion. If you are going to seek it, seek it clearly and early in the response.
7. Review and file. Check that every exhibit is referenced in the body of the response and that the response meets the provider's page or word limits. The trap: attaching exhibits that are not mentioned in the text. Panels read responses carefully; they do not hunt for exhibits the respondent forgot to discuss.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. For a read on whether the three auDRP elements are met, reach us at info@cognomenlaw.com.

How does the .au defense compare to defending across other zones?

The right strategy depends on the zone and the goal. If the same name is disputed as a .com, the standard UDRP applies at WIPO or the Forum, with a filing fee starting at USD 1,500 for a single-member panel and a response window of 20 days. The legal standard is nearly identical to the auDRP, but the panel pool and the precedent library are different — and because UDRP panels have decided tens of thousands of cases, the generic-word doctrine is more extensively developed there.

If the disputed domain is a .uk rather than a .au, the Nominet DRS applies. The Nominet test is "abusive registration" — and critically, the DRS reads "registered OR used" abusively, a single-limb test that is in some respects a lower bar for complainants than the UDRP's cumulative standard. Nominet also provides a free mediation stage before any expert decision, which creates an early-exit option for both parties. The DRS framework is different enough from the auDRP that strategy for a .uk dispute must be rebuilt from scratch, not recycled from the .au response.

For a .de, there is no UDRP equivalent at all. Disputes go to the German courts, with a DENIC DISPUTE entry available to block transfer during litigation. The cost and timeline are substantially higher than an administrative procedure, and local litigation counsel in the relevant jurisdiction handles the court action.

In a recent matter involving parallel .com and .au registrations (spring 2025), we coordinated the respondent's defense across both proceedings simultaneously — synchronizing the evidentiary record so that the generic-word documentation deployed in the auDRP was consistent with, but independently adapted for, the UDRP response. The trap in parallel proceedings is filing inconsistent positions. Panels read each other's published decisions, and contradictions between a UDRP response and an auDRP response — even in separate proceedings — can surface at the most inconvenient moment.

See also our guide to what happens when you registered a domain before the complainant filed its trademark application, and the worked example of defending through a national ccTLD dispute procedure, both of which address closely related evidence questions.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs – full service overview
• FAQ: registered before the trademark application – does it guarantee a win?
• Case study: defending through a national ccTLD dispute procedure