FAQ: structure escrow for a .au domain purchase
FAQ: structure escrow for a .au domain purchase. UDRP and ccTLD domain recovery and defense across .au. Email the firm to assess your case. Transparent fees, r…
A .au domain changes hands — and the buyer wants to know the name is clean, the seller is legitimate, and the funds move only when the registry confirms the transfer. That is the core problem that escrow solves in a .au domain transaction. Structuring it correctly requires an understanding of Australia's eligibility rules, the auDRP dispute history risk, and the mechanics of how .au registrar transfers actually settle.
To structure escrow for a .au domain purchase, the parties place the agreed purchase price with a neutral escrow agent, the seller initiates the registrar transfer to the buyer's account, and funds are released only after the registry confirms the transfer is complete. Because .au carries strict eligibility requirements for registrants, due diligence on chain of title and any prior auDRP dispute history is a necessary step before funds are committed. A poorly structured acquisition can leave the buyer holding a domain that cannot be transferred — or one that is subject to a pending or recently decided dispute.
The questions below address how escrow works for .au domains, what evidence is needed, whether multi-domain transactions are possible, and what the realistic outcomes are.
What does it mean to structure escrow for a .au domain purchase?
Structuring escrow for a .au domain purchase means using a neutral third party — the escrow agent — to hold the buyer's funds while the domain transfer completes through the .au registry. It is a transactional control mechanism, not a dispute mechanism. The escrow agent releases funds only on a defined trigger: typically, confirmation that the domain now resolves to the buyer's registrar account and that the registrar lock has been removed and re-applied in the buyer's name.
For a .au domain, two additional layers apply. First, Australia's .au namespace imposes eligibility requirements — the registrant of a .au second-level domain (such as a .com.au) must have an Australian Business Number, an Australian Company Number, or another qualifying connection. A buyer who does not meet those requirements cannot hold the domain, and a transfer instruction will fail at the registry level. Escrow does not cure an eligibility defect. Eligibility must be confirmed before the escrow agreement is signed.
Second, the auDRP — Australia's adaptation of the UDRP — creates a chain-of-title risk. If the domain was previously the subject of an auDRP complaint, or if the current registrant acquired it through a path that involved a transfer during a live dispute, the domain may carry a reputational or procedural taint. A new registrant is not automatically insulated from a complainant's re-filed claim if the circumstances warrant it. Due diligence on prior dispute history is therefore part of a correctly structured .au escrow, not an optional extra.
In our practice, we regularly advise buyers who have already agreed on a price but have not yet checked eligibility or dispute history. That sequence — price first, diligence second — is the most common structural mistake in .au domain acquisitions.
How long does it take to structure escrow for a .au domain purchase?
The timeline to structure escrow for a .au domain purchase depends on three phases: due diligence, escrow setup, and the registrar transfer. A straightforward transaction between two eligible parties, with clean dispute history and an agreed form of escrow agreement, can move from signed heads-of-terms to completed transfer in a matter of days. More complex transactions — multi-domain lots, a seller whose eligibility status is unclear, or a domain with prior auDRP activity — routinely take several weeks.
Due diligence is the phase most buyers underestimate. Checking eligibility, pulling the WHOIS/RDDS record, reviewing any auDRP filings, and confirming there is no active registrar lock or transfer-hold all takes time to do properly. A domain under a registrar lock cannot transfer regardless of what the escrow agreement says. Confirming the absence of a lock — and the reason any lock was placed — is a separate inquiry.
The escrow setup phase is typically the shortest. A standard escrow agreement can be drafted and executed in one to three business days once the parties agree on the release trigger and the escrow agent. The registrar transfer itself, once initiated, is governed by the .au registry's own processing schedule and any inter-registrar transfer policies in place at the time. Verify the current transfer timing with the receiving registrar before committing it to the escrow agreement as a drop-dead date.
What does it cost to structure escrow for a .au domain purchase at auDRP?
The cost question has two distinct parts, and mixing them is a common source of confusion. Escrow fees and auDRP dispute fees are separate things. A standard domain escrow transaction does not involve auDRP at all — auDRP is a dispute-resolution mechanism for contested domains, not a transfer mechanism for agreed sales. If you are asking about the cost of buying a .au domain through escrow, that cost is the escrow agent's fee (typically a percentage of the purchase price, often in the low single digits) plus any legal or advisory fees for due diligence and agreement drafting.
If, on the other hand, a dispute arises — for instance, the seller turns out not to have good title, or a third party challenges the transfer — then auDRP proceedings become a separate cost item. The auDRP tracks the three-element structure of the UDRP: confusing similarity to a mark, absence of legitimate interest, and registration or use in bad faith. Filing fees for auDRP proceedings are set by the applicable providers and should be verified with the current provider at the time of filing, as they are subject to change. Legal fees for an auDRP complaint or defense in a straightforward case are a separate cost, in the range commonly seen for comparable UDRP proceedings.
Our published approach is to separate these cost categories clearly. Pre-acquisition due diligence and escrow structuring carry one fee basis. Dispute work, if it becomes necessary, carries a different basis. We describe both in plain terms before any engagement begins.
What evidence is needed to structure escrow for a .au domain purchase?
Evidence in a .au domain escrow transaction serves two functions: it supports the due-diligence review before funds are committed, and it forms the record if a dispute arises afterward. What you need differs by function, but assembling both sets of evidence at the outset is the efficient approach.
For pre-acquisition due diligence, the core evidence set includes: the current WHOIS/RDDS record (confirming the registrant of record, the registrar, and the domain's status); the seller's eligibility documentation (ABN, ACN, or other qualifying basis, matched to the registrant-of-record name); any public record of prior auDRP filings or proceedings involving the domain; the registration date and any transfer history visible in the registry data; and confirmation that no registrar lock, hold, or pending transfer flag is active on the domain.
If the domain corresponds to a trademark — whether the buyer's own mark or a third party's — the trademark registration details are relevant to assessing the risk that a complainant could mount an auDRP challenge against the new registrant after transfer. A domain that is identical or confusingly similar to a registered Australian trademark, with no obvious legitimate-interest story for the buyer, is a domain worth examining carefully before the escrow funds are committed.
For the escrow agreement itself, the key evidence elements are: the agreed purchase price and the escrow release trigger; the eligibility confirmation from the buyer; the agreed registrar for the receiving account; and the domain's current status at the registry. We have defended registrants who acquired .au domains without assembling this record — and found that the absence of documented diligence made an already difficult position harder to explain to a panel.
Can I structure escrow for a .au domain purchase for more than one domain at once?
Yes. A single escrow arrangement can cover multiple .au domains, provided the agreement clearly defines the release trigger for each domain individually or for the lot as a whole. The choice between individual and lot-based release triggers matters: if one domain in a multi-domain transaction is subject to a registrar hold, a lot-based trigger stalls the entire transaction. Individual triggers give the buyer the flexibility to complete clean transfers while holding funds for the delayed domain.
Multi-domain transactions also multiply the due-diligence obligations. Each domain in the lot requires its own eligibility check, its own dispute-history review, and its own registrar-status confirmation. A seller offering ten .au domains as a portfolio lot may hold them across different registrars, with different lock statuses and different eligibility bases. Consolidating that due diligence into a coherent pre-signing review is where experienced counsel adds measurable value.
The auDRP, for reference, permits a single complaint to cover multiple domains where they share the same registrant. That procedural fact is relevant to a multi-domain acquisition in both directions: a buyer acquiring a portfolio from a seller with a disputed history faces a bundled complaint risk, and a buyer who later needs to enforce against a multi-domain cybersquatter can address all the domains in one proceeding rather than filing separately.
In a recent matter (a .au portfolio acquisition of several names, early 2026), we completed due diligence across the lot, identified one domain with an unresolved prior auDRP inquiry, and structured the escrow to hold that domain's allocated price in reserve while the seller addressed the status issue. The remaining domains transferred on schedule.
What are the possible outcomes when you structure escrow for a .au domain purchase?
The possible outcomes of a correctly structured .au domain escrow transaction range from clean completion to partial completion to a failed transaction — and, in the worst case, a post-transfer dispute that unwinds or clouds the buyer's title. Understanding each outcome in advance shapes how the escrow agreement should be drafted.
Clean completion is the expected outcome when eligibility is confirmed, no dispute history attaches to the domain, no registrar lock is present, and the transfer completes within the agreed window. The escrow agent releases funds, the buyer is registered as the new registrant of record, and the transaction closes.
Partial completion arises in multi-domain transactions where one or more domains cannot transfer within the agreed timeline — because of a lock, an eligibility issue, or a registry processing delay. A well-drafted escrow agreement anticipates this by providing either a price reduction, a holdback, or an extension right for the delayed domains.
A failed transaction occurs when an eligibility defect is discovered after funds are committed but before transfer, or when the seller cannot demonstrate good title. In that scenario, the escrow structure matters enormously: funds should return to the buyer without dispute if the release trigger was not met. A poorly drafted agreement can make even a straightforward refund contentious.
Post-transfer disputes are the least common but highest-stakes outcome. If a third party files an auDRP complaint against the new registrant — arguing that the domain is confusingly similar to their mark and was registered or used in bad faith — the buyer must defend on the merits. The auDRP applies its own version of the three-element test, with the bad-faith limb read in a manner that may differ at the margins from the standard UDRP formulation. Panels have considered the effect of a change of registrant in the chain-of-title analysis; that question is fact-specific and should be assessed before acquisition, not after.
Related at COGNOMEN
About COGNOMEN
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants — including respondent-side defense and reverse domain name hijacking. Our approach to transactions covers pre-acquisition due diligence, chain-of-title review, escrow structuring, and portfolio brand-protection monitoring across gTLD and ccTLD zones, including .au. To discuss a domain, contact info@cognomenlaw.com.
For an assessment of your .au domain acquisition or escrow structure, contact info@cognomenlaw.com.
Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
Related
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.