Using NameBio / DNJournal for .au: why thin liquidity changes the worksheet

A buyer opens NameBio and filters by keyword. They find thirty reported .com sales with disclosed prices, date stamps, and venue labels. The sample feels robust. They switch the extension filter to .au or .com.au and find three rows — one from 2019, one with no disclosed amount, and one that is a different keyword entirely but matched the search term as a substring. The buyer screenshots the .com chart, converts the median to AUD, and calls it their ceiling. That ceiling is borrowed liquidity, not Australian market evidence.

This article explains why thin Australian .au and .com.au public sale liquidity changes the domain name valuation worksheet itself — not just the comp figures you write down, but the structure of the fields, the confidence scoring you apply, the extension and channel filters you use, and what a domain broker or operator still asks before treating a sparse sample as decision fuel. It is for Australian buyers and sellers who know how to read DNJournal and NameBio correctly (as described in how to read DNJournal and NameBio without fooling yourself) but discover that the Australian extension sample is too thin to fill a standard comp sheet. It narrows to the worksheet-structure changes that follow from low public disclosure rates in the .au / .com.au aftermarket, and to the operator practices domain name brokers use when public rows cannot answer the valuation question alone.

This piece does not give legal, tax, or investment advice. It does not appraise any named domain, guarantee what a name will sell for, invent asking or closing prices, invent .au or .com.au comps where the public sample is thin, promise rankings or traffic, or commit Perfect Domain to any purchase or sale. It describes worksheet adjustments, not a method for manufacturing Australian market prices from offshore data.

Thin liquidity here means a low rate of publicly disclosed .au or .com.au domain sales relative to the rate of actual transactions. It does not mean nobody is buying Australian domains. It means most .au and .com.au deals close privately — brokered directly, sold within networks, or transferred as part of business acquisitions — and never appear as NameBio rows or DNJournal line items with disclosed amounts.

The practical consequence for a buyer or seller building a domain name valuation worksheet is that the public sample is often too sparse to support statistical confidence. A keyword with fifty disclosed .com sales over five years might have three disclosed .com.au sales over the same period, and those three may not be comparable — different lengths, different use cases, different disclosure contexts (auction vs private sale vs portfolio transfer). The standard comp-sheet method described in comparable domain sales: how to use them assumes a sample deep enough to filter by relevance and still have rows left. When the .au sample is three rows total, filtering leaves you with zero or one, and one comp is not a market.

Thin liquidity also means that offshore .com or .net sales dominate the NameBio chart for most keywords, creating pressure to treat international reported closes as local proxies. That pressure is the mistake this article addresses. Borrowing a .com ceiling for a .au target without adjusting the worksheet for extension mismatch, eligibility constraints, and liquidity gaps is how buyers invent floors and sellers invent asks, neither of which survive negotiation with a serious counterparty who knows the Australian sample is thin and will not accept borrowed figures as evidence.

When public .au or .com.au comp rows are scarce, the standard domain name valuation worksheet fields (described in domain name valuation worksheets for AU buyers: fields that matter before comps) do not disappear. They expand. You cannot skip the pre-comp fields just because NameBio has no rows. You add fields that document the sample gap, label any offshore proxy rows clearly, and record how you will handle the missing local data before you negotiate.

The first new field is sample size and coverage window. Instead of writing 'median of fifteen .com sales 2022–2026' you write 'two disclosed .com.au sales 2020–2026, one auction result, one private brokered; median not calculable; no sales for this exact keyword in .au extension; next-closest match is [string] with one 2023 result.' That field is not optional when the sample is thin. It is the disclosure that prevents your domain broker or your negotiation counterparty from mistaking a thin sample for robust liquidity. If you do not write the sample-size note, your comp column looks like it has the same statistical weight as a fifty-row .com chart, and it does not.

The second new field is confidence scoring by row. When you have thirty .com comps, you can afford to include a few weak matches and still have a median that reflects genuine market activity. When you have two .au rows, every row is weight-bearing, and you must label confidence explicitly. A confidence column might read: 'Row 1: exact keyword .com.au, auction close 2023, reported amount, HIGH confidence as ceiling reference; Row 2: partial keyword match .au, private sale 2020, amount unverified, LOW confidence, appendix only; Row 3: offshore .com reported close 2025, string match but unrestricted extension, MEDIUM confidence as category climate, not a local floor.' Without that scoring, readers treat all three rows as equivalent evidence, and they are not.

The third field is extension and channel filter documentation. When the local sample is thin, you will be tempted to include .com, .net, or new gTLD rows to pad the sheet. That temptation is fine as long as you label those rows clearly as cross-extension references and explain why you believe the buyer pools overlap. The field reads: 'Extension filter: target is .com.au; included .com rows from NameBio as offshore ceiling context only; excluded .ai and .io rows (tech-category bias, different buyer eligibility); no same-extension comps available for this keyword; relying on broker floor guidance + offshore .com ceiling + thin local auction sample.' That filter note is what separates a comp sheet with honest gaps from a comp sheet that pretends a .com median is a .au market price.

The fourth field is 'headline only' versus 'usable local signal' tagging. When you find a .au or .com.au row in NameBio, you must decide: is this row structurally similar enough to your target to inform your ceiling or floor, or is it only proof that someone somewhere bought a .au domain? A 2019 .com.au sale of a four-word descriptive phrase is not usable local signal for a 2026 acquisition of a two-word exact-match brand. It is a headline that proves .com.au domains change hands. Tag each .au row as 'headline only' or 'usable signal' and write one sentence defending the usable-signal tags. If you cannot write that sentence, the row stays headline-only, which means it goes in the appendix, not the decision column.

These expanded fields add friction. That friction is the cost of honesty when liquidity is thin. Skipping them does not make the worksheet faster. It makes the worksheet fiction, and fiction does not survive a negotiation with a domain broker who knows the Australian sample and will ask you to defend every figure you claim as market evidence.

The most common mistake when .au comps are thin is to take the .com sample median, convert it to AUD, and label it as the Australian market ceiling. That conversion is arithmetic. It is not domain name valuation. The .com buyer pool is unrestricted — any global entity can acquire and hold a .com. The .au and .com.au buyer pools are eligibility-constrained — you must satisfy auDA's Australian presence or business connection requirements to hold the name. That eligibility gate reduces the addressable buyer pool, which affects liquidity and pricing, but by how much depends on the specific string and use case, not a universal discount percentage.

Converting a .com price also ignores the disclosure gap. The .com sample you are converting is reported liquidity — deals that were public enough to appear in NameBio or DNJournal. The .au market includes both the thin public sample and the larger private sample that never disclosed. You do not know whether the private .au deals closed above, below, or in line with the converted .com figures because they are private. Treating the converted .com number as the .au ceiling assumes the private .au market behaves like the public .com market, and that assumption has no supporting evidence when the .au public sample is three rows.

For Australian sellers, this matters because a buyer who sees a .com median converted to AUD and labelled as 'the market' will negotiate as if that figure is the ceiling, not the floor. If the seller's ask is above the converted .com number and the seller cannot produce disclosed .au comps that justify the premium, the buyer will treat the ask as speculative. For Australian buyers, it matters because a domain name broker or seller who quotes a figure 'based on .com comps' without disclosing the conversion method, the sample size, and the eligibility adjustment is either guessing or inflating. Either way, the number is not grounded in Australian disclosed liquidity, and the buyer should ask for the underlying worksheet before accepting it as a negotiation anchor.

The correct use of offshore .com rows when .au liquidity is thin is as category climate context, not as plug-in pricing. A .com reported close tells you that someone, somewhere, valued that keyword highly enough to pay the disclosed amount in an unrestricted global market. It does not tell you what an eligibility-constrained Australian buyer will pay for the .au or .com.au variant. To get from the .com context to a .au working range, you still need the full valuation worksheet described in domain name valuation worksheets for AU buyers: fields that matter before comps — intended use, eligibility path, budget ceiling, time-to-close, alternatives if acquisition fails, and risk tolerance for thin comps. If those fields are blank, converting a .com number to AUD does not fill them. It just gives the blank fields a currency symbol.

When a buyer or seller briefs a domain name broker on a .au or .com.au acquisition or sale and the public NameBio sample for that keyword is zero rows or one unusable row, the broker does not throw up their hands and say 'there is no market.' They ask a different set of questions, because the absence of public disclosure does not mean the absence of private transactions. What the broker asks instead is what this article has been building toward: the fields that replace statistical comps when statistical comps do not exist.

First question: what is your intended use, and is it an exact-match brand, a category-descriptive redirect, or a defensive hold? The answer defines the buyer pool and the urgency. An exact-match brand buyer who needs the .com.au string to launch their business has a different ceiling than a category buyer who wants the name as a traffic redirect and has five other acceptable alternatives. Use case is always part of the worksheet (see how Perfect Domain scopes a domain name appraisal brief: process, not a price), but when comps are thin, it moves from context to weight-bearing field. If the broker does not know your use case, they cannot distinguish between 'this is the only string that works' and 'this is one of several acceptable strings,' and that distinction is the difference between a negotiable ask and a take-it-or-leave-it floor.

Second question: what offshore .com or .net sales have you seen, what did you conclude from them, and why do you believe those conclusions transfer to the Australian extension? The broker is not asking you to defend a conversion formula. They are asking you to show your reasoning so they can check it for the common thin-liquidity traps: mistaking a .com median for a .au floor, ignoring eligibility constraints, treating one offshore sale as a trend, or borrowing a viral .ai headline without noting the category mismatch. If your reasoning is 'NameBio shows .com at X, so .au should be Y,' the broker will push back and ask you to fill the fields that connect X to Y. If you cannot, the offshore row stays in the appendix, and the broker works from use case and alternatives instead of from borrowed comps.

Third question: have you spoken to anyone privately who bought or sold a similar .au or .com.au string, and if so, what did they tell you about pricing, timing, and negotiation climate? Private knowledge — 'I know someone who paid $50k for a two-word .com.au in 2024' — is not a NameBio row, but it is still evidence if you can verify the basics (year, string type, channel). The broker will ask you to label it as unverified private knowledge, not as a reported comp, but it can still inform the working range when public rows are absent. What the broker will not do is take your private-knowledge figure at face value without asking follow-up questions: Was that an auction, a brokered deal, or a direct negotiation? Was the buyer strategic or speculative? Did the deal include other assets or just the domain? Was the amount in AUD or converted? Private knowledge without context is rumor. With context, it is a data point the broker can weigh against the thin public sample.

Fourth question: what is your walk-away if the seller (or buyer) will not move, and what alternatives do you have if this negotiation fails? This question (covered in detail in how Australian sellers should brief a domain name broker on walk-away vs ask) matters even more when comps are thin, because thin comps mean higher negotiation uncertainty. If your walk-away is firm and you have no alternatives, the broker knows they are negotiating with low flexibility on your side, and they will not waste time chasing a price the seller will never accept or the buyer will never pay. If your walk-away is negotiable and you have three other acceptable strings, the broker can test the market without committing you to a ceiling you cannot defend. Walk-away is always part of the brief. When liquidity is thin, it becomes the anchor, because comps cannot play that role.

These questions are not a workaround for missing comps. They are the valuation inputs that matter more than comps when the sample is sparse. A domain broker who skips these questions and just quotes you a figure 'based on market data' when the market data is two NameBio rows from 2020 is either inventing the number or relying on private deal knowledge they are not disclosing. Either way, you should ask them to show you the worksheet. If they cannot, the figure is not grounded, and you are negotiating blind.

On Perfect Domain valuation worksheets for Australian .au and .com.au acquisitions and sales, when the NameBio or DNJournal sample for the target keyword and extension is fewer than five disclosed rows in the past five years, we write a field at the top of the comp section that reads: 'Thin local sample: [X] disclosed .au / .com.au sales for this keyword 2021–2026; relying on offshore .com ceiling context + buyer use case + walk-away + private market knowledge; no statistical median calculable.' That field is not buried in a footnote. It is the first thing the client and any reviewing broker or board member reads before they see the comp rows.

We refuse to hide that note because hiding it is how thin samples get mistaken for robust liquidity. A comp sheet with ten rows looks authoritative. If eight of those rows are .com or .net and only two are .au, and the sheet does not label the split, the reader assumes all ten rows are local evidence. That assumption survives until the negotiation counterparty asks 'which of these are actually .au sales?' and the answer is 'two,' at which point the entire comp sheet loses credibility. Writing the thin-sample note upfront prevents that credibility collapse and sets realistic expectations: the Australian public sample is sparse, so the worksheet will rely more heavily on use case, alternatives, and walk-away than on statistical comps.

We also label every cross-extension row explicitly in the confidence column. A .com row on an Australian .au acquisition worksheet gets tagged 'offshore unrestricted-extension ceiling context only; not a local comp; eligibility-constrained buyer pool difference not quantified.' A .ai row gets tagged 'tech-category climate; different extension and buyer pool; appendix only; does not inform .au floor.' A .net row gets tagged 'secondary unrestricted extension; thinner liquidity than .com; treat as lower-bound offshore reference if used at all.' Those tags take up space. They also prevent the mistake where someone glances at the comp sheet, sees ten rows, and assumes all ten rows support the proposed ceiling or floor without reading the extension column.

The operator detail that matters most is that we will not convert a .com median to AUD and present it as the .au market price, even when the client asks us to. We will present the .com median as offshore category context, note the currency and conversion rate if relevant, and then write a separate Australian working range based on the full worksheet (use case, eligibility, alternatives, walk-away, thin local sample note, and any private market knowledge the client has shared). If the client wants a single number to take to a board or a negotiation, we write two numbers: the offshore .com context figure and the Australian working range, each labelled clearly. If those two numbers are far apart and the client asks why, we explain the eligibility constraint, the liquidity gap, and the lack of disclosed .au comps, and we show them the thin-sample note. What we do not do is invent a percentage discount from .com to .au and apply it universally, because that percentage does not exist. It varies by keyword, by use case, by buyer urgency, and by whether the .au name is being acquired as a brand exact-match or a category redirect.

This refusal to convert and label offshore figures as local prices is the practice that costs us deals where the buyer or seller wanted a neat comp-based number and we could not provide one honestly. It is also the practice that keeps our worksheets defensible when a negotiation counterparty asks to see the underlying data. If we wrote 'market price based on NameBio comps' and the NameBio sample is two rows, we would lose that negotiation immediately. By writing 'thin local sample, offshore context only, working range based on use case and walk-away,' we set the expectation that this is not a statistical valuation, it is a structured negotiation informed by sparse public data and the client's specific constraints. That expectation is honest, and honesty is what makes thin-liquidity worksheets usable instead of fictional.

If you are an Australian buyer or seller preparing a domain name valuation worksheet for a .au or .com.au acquisition or sale, and you open NameBio and discover the extension sample is three rows or fewer, do not panic and do not borrow a .com median as a substitute. Add the worksheet fields described above: sample size and coverage window, confidence scoring by row, extension and channel filter documentation, 'headline only' versus 'usable local signal' tagging, and the four broker questions (intended use, offshore reasoning, private knowledge, walk-away and alternatives). Those fields turn a thin sample into a defensible brief. Skipping them and padding the sheet with unlabelled .com rows turns a thin sample into fiction.

If you are working with a domain broker on an Australian acquisition or sale and the broker quotes you a ceiling or floor 'based on market data' without showing you the worksheet, ask to see the sample size, the extension split, and the confidence scoring. A professional broker will have those fields ready because they know thin .au liquidity is the norm, not the exception, and they have built their worksheets to handle it. A broker who cannot show you those fields or who says 'NameBio shows the market is X' without noting that NameBio shows two .au rows and fifty .com rows is either inexperienced with the Australian market or is deliberately obscuring the sample size to make their figure look more robust than it is. Either way, you should not negotiate based on a number you cannot verify.

For offshore .com or .net context, use the reported closes as category climate (what has the international unrestricted market paid for this keyword class?) but not as a plug-in ceiling or floor for the Australian extension. Write the offshore rows in a separate appendix section, label them clearly as 'cross-extension reference only,' and note the eligibility and liquidity differences that prevent direct comparison. Then write your Australian working range in the decision column based on the full worksheet fields, not as a conversion from the offshore appendix. If your working range is wide because the sample is thin and your alternatives are flexible, write that range honestly. A wide range with honest gaps is more negotiable than a narrow range built on borrowed liquidity that collapses when the counterparty asks for the supporting evidence.

Thin Australian .au and .com.au public sale liquidity is not a problem you solve by pretending the liquidity is not thin. It is a constraint you document on the worksheet so that everyone involved in the negotiation — buyer, seller, broker, board, counsel — knows the public sample is sparse and the valuation is informed by use case, alternatives, and walk-away rather than by statistical comps. That transparency is what separates a professional domain name valuation brief from a NameBio screenshot with a currency conversion and a circled median. One survives negotiation. The other does not.

This piece complements how to read DNJournal and NameBio without fooling yourself, which covers chart hygiene and the difference between reported and estimated sales. For the full pre-comps worksheet that these thin-liquidity fields extend, see domain name valuation worksheets for AU buyers: fields that matter before comps. For how to build a comp sheet when you do have multiple rows, see comparable domain sales: how to use them. For the broader scoping questions a domain broker asks before treating any public sale as decision fuel, see what Perfect Domain asks before treating a public sale as decision fuel.

For the distinction between offshore .com ceiling context and Australian extension working ranges, see using an international headline as a comparable for an Australian acquisition. For what a domain name broker does when public comps cannot answer the valuation question alone, see what does a domain broker do and how Perfect Domain scopes a domain name appraisal brief: process, not a price.

Perfect Domain works with Australian buyers and sellers on premium .au and .com.au acquisitions and sales. When NameBio or DNJournal samples are thin, we document the sample gap, label cross-extension rows explicitly, and build the working range from use case, alternatives, and walk-away rather than from borrowed offshore liquidity. If you are preparing a valuation brief for an Australian domain and the public comp sample is sparse, contact Perfect Domain through the site. We will not invent a local price from a .com chart. We will build a defensible thin-liquidity worksheet that survives negotiation with a counterparty who knows the Australian sample is sparse and expects the brief to acknowledge it honestly.