How to read DNJournal and NameBio without fooling yourself

You open DNJournal in one browser tab and NameBio in another. Someone drops a chart screenshot into the deal channel with a circled row and a short caption: "Comps look strong." Ten minutes later the acquisition brief has a new ceiling, or the seller brief has a new floor, and nobody can say whether the circled figure was reported, estimated, converted, or simply listed.

This article is for Australian buyers, sellers, and operators who use public domain sales charts as research inputs and need a reading method that does not invent liquidity. It sits next to what a public seven-figure domain sale actually proves (what a named headline proves) and comparable domain sales: how to use them (how to build a comp sheet). The new ground here is narrower: how to read DNJournal and NameBio themselves — reported versus private, FX conversion traps, and chart lag — without fooling yourself.

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 prices, promise rankings or traffic, or commit Perfect Domain to any purchase or sale. Named public closes are cited only as reported by their source publications; Perfect Domain did not broker those transactions and cannot verify undisclosed terms.

DNJournal and NameBio are the two public archives most brokers and serious buyers cite when they talk about "the market." They are useful. They are not a complete ledger of every domain transaction, and they are not a valuation engine.

• DNJournal: a long-running trade publication that reports selected verified domain sales, often with narrative context (buyer, seller, broker, or delayed-disclosure notes). A DNJournal row with a named price and string is usually treated as a reported close, not a marketplace ask.
• NameBio: a searchable public sales database that aggregates reported domain transactions across many sources and presents them as chartable rows (string, extension, date, amount, and sometimes venue). Coverage is broad; verification depth varies by source row.

Neither service claims to capture every private brokered deal, every NDA close, or every portfolio transfer that never hits a press desk. Public rows are a sample of disclosed liquidity. Treating the sample as the whole market is the first way people fool themselves.

Before you paste a figure into a board pack, label the row:

• Reported close: a named amount tied to a named string, published by a credible source after a sale. Example pattern from recent public coverage: DNJournal-reported closes such as AI.com at USD $70m, Icon.com at USD $12m, and Club.com at USD $10m (report dates and any "sold earlier" notes belong on the same line as the figure).
• Delayed disclosure: the sale closed earlier under NDA or quiet escrow; the chart date is the disclosure date, not necessarily the negotiation window. Club.com is a clean illustration of that gap when the report notes an earlier close.
• Marketplace ask / Buy Now: a live list price. It proves seller posture, not paid consideration.
• Private / unverified: a number someone heard on a call, saw in a Discord, or inferred from a "sold" landing page with no published amount. Useful as a rumour to chase; useless as a comp until sourced.

Perfect Domain's rule is blunt: if we cannot write "reported by [source] on [date] as [currency] [amount] for [exact string]," the figure does not enter the decision column of a comp sheet. It can sit in a parking lot labelled "unverified lead," but it does not move a walk-away or an ask.

Sales charts compress messy timelines into one date cell. That cell might mean report date, close date, escrow release date, or the day a secondary source scraped the primary report. Lag shows up in three common ways:

• Report date after close date: especially on brokered mega-sales that stay quiet until a disclosure window opens.
• Source republish lag: NameBio (or another aggregator) may show a date when it ingested a DNJournal or marketplace report, not when cash moved.
• Category climate drift: a 2024 close disclosed in 2026 can look like "current" liquidity if you only read the chart month.

When an Australian buyer uses a lagged USD row to justify a 2026 .com.au budget, they are mixing eras. Write both dates when you know them. If you only have the report date, say so in the brief: "Report date only; close may be earlier."

Most premium international rows are in USD. Australian buyers and sellers almost always need an AUD working number for boards, tax conversations, or personal budgets. Conversion is fine. Silent conversion is how a working assumption hardens into a fake reported price.

• Keep the reported figure in its original currency on the primary line.
• Add a second line for the AUD conversion with FX rate, rate date, and the words "working assumption for budgeting."
• Never quote the converted AUD figure as "the sale price" in a memo, listing brief, or seller update.
• Revisit the rate if the deal window stretches; last month's conversion is not today's board number.

Example of clean labelling (illustrative FX only, not a Perfect Domain quote): "DNJournal reported Club.com at USD $10m (report April 2026; earlier close noted). Working AUD conversion for budgeting at [rate] on [date] ≈ AUD $Xm — assumption, not a reported price." If you cannot fill those brackets, you are not ready to use the row in a decision.

Even a perfectly labelled USD row can be the wrong tool for an Australian acquisition if you skip jurisdiction. Public charts are heavy on .com and light on .au / .com.au liquidity. That is not a criticism of DNJournal or NameBio; it reflects where disclosed volume concentrates.

• .au and .com.au eligibility: buyers need qualifying Australian presence (or other auDA-pathway eligibility). A global chart buyer who cannot take the name is not your comparable demand.
• Transfer timing: many gTLD transfers clear faster than some .au pathways that need eligibility review. Chart "speed" stories rarely map 1:1 (see how long a brokered domain purchase takes).
• Thin local comps: fewer public .au closes means you will feel pressure to stretch a .com headline into a local floor. Stretching without a written eligibility and buyer-pool note is inventing a market.
• Escrow and FX together: Australian wires, GST conversations, and USD escrow instructions add friction the chart row never shows (see domain escrow: how premium domain payments work).

If your target is a .com.au or .au string, treat international chart rows as ceiling context for the global category — not as a plug-and-play ask or walk-away for the Australian name.

Perfect Domain's first-hand process when a client pastes a DNJournal or NameBio screenshot is a five-field worksheet before we discuss emotion or strategy:

1. Exact string and extension as printed (including the dot).
2. Source name and URL or issue reference (DNJournal article, NameBio row link, or both).
3. Amount with currency as printed — no silent AUD rewrite.
4. Date type: report date, close date, or "unknown / chart date only."
5. Row class: reported close, delayed disclosure, marketplace ask, or unverified.

We refuse to put an incomplete row into the decision column of a buyer or seller brief. Incomplete rows can stay in a research appendix. That refusal is not pedantry; it is how we stop a screenshot from becoming an invented floor. The same discipline applies when the client wants a free tool figure promoted into an ask (see domain name appraisal for sellers).

Pattern recognition helps more than another tutorial. Watch for these:

• Averaging unlike rows: blending a reported seven-figure .com close with Make Offer chatter and an expired-auction result, then calling the average "the market."
• Plural / singular bleed: treating Clubs.com evidence as Club.com evidence (or the reverse).
• Extension bleed: citing .com liquidity as proof for .ai, .io, or .com.au without a separate buyer-pool note.
• Venue confusion: marketplace "sold" badges without amounts treated as verified closes.
• Screenshot without source: a chart image that lost its URL, date filter, and currency header in transit through Slack.

Each of those errors is reversible if you catch it in the worksheet. Once the bad number is in a board deck, reversing it costs trust.

Reading DNJournal and NameBio well does not mean collecting more rows. It means upgrading the quality of the few rows you keep. A strong brief after chart work usually has:

• Three to seven labelled reported closes that share length, extension family, and plausible buyer use with your target — or an explicit note that public comps are thin.
• At least one sentence on what the public sample cannot show (private NDA volume, Australian eligibility constraints, FX).
• A separate budget line for your walk-away or ask that does not equal any single viral row.

If your brief is only a screenshot and a circled number, you have not finished reading the chart. You have only finished looking at it.

If you are preparing an Australian acquisition or sale and your research already includes DNJournal or NameBio rows, Perfect Domain can review the labelled worksheet with you. Send the exact strings, source links, printed currencies, and date types — not a lone screenshot. We will say which rows belong in the decision column, which belong in the appendix, and where FX or lag is doing quiet damage.

We will not invent a price from a chart, certify a valuation, or treat an unverified figure as a close. If your brief is still "What is this domain worth based on this viral row?" without source labels, start with the worksheet above first. When the labels are filled in and you want an operator pass on how those public sales inform process — not fantasy pricing — contact Perfect Domain through the site with that pack attached.