metricname

Guidesby the numbers

How to Read a Domain Sale Comp (NameBio, DNJournal, and What a "Comparable" Means)

A comp is a reported sale, not a price tag on your domain. What NameBio and DNJournal each actually cover, why the reported price is gross not net, why some comps are self-reported and unverified, what makes one comp actually comparable to your domain, and a checklist before you cite one in a negotiation.

A comp is a reported sale, not a price tag

“Comp” is short for comparable sale — a domain that already changed hands, cited as evidence for what a similar domain might be worth. A comp is not a price on your domain. It’s one data point from a market where, as our what a domain is actually worth guide covers, most names never generate a data point at all. Reading a comp well means treating it as evidence to weigh, not a number to copy.

Two databases, two different jobs

Domainers say “check NameBio” the way developers say “check Stack Overflow” — as shorthand for the whole category. In practice, two separate sources do most of the work, and they answer different questions:

  • NameBio is the aggregator: a searchable, filterable database spanning both marketplace and self-reported sales, built for asking “what does a typical sale in this category look like?” Its strength is volume — it’s where our own appraisal engine reads category medians (documented on the appraisal tool’s methodology).
  • DNJournal is the editorial record: weekly sales charts published for decades, each entry traceable to a named venue and archive page. Its strength is verifiability — every row links to the exact report it came from, which is why it’s the source behind the comps shown on this site.

Neither is more “correct” than the other; they trade off coverage against traceability. DNJournal skews to the top of the market — its charted venues have floors around $2,000 — so a DNJournal-sourced comp set tells you what strong sales of a shape look like, not the median outcome. That’s why our tool pairs DNJournal comps with NameBio-derived category ranges rather than using either alone.

Reading a comp row, field by field

A typical comp — on NameBio, DNJournal, or the comps section under an appraisal on this site — carries the same handful of fields. Here’s what each one tells you, and what it quietly doesn’t:

FieldWhat it tells youWhat it doesn’t
DomainThe exact SLD + TLD that soldWhether it’s actually comparable to yours (see below)
PriceThe reported gross sale figureWhat the seller netted after commission
Date / yearWhen the sale was reportedHow current that price still is in a moving market
VenueWhere the sale happened or was reported (broker, auction, private)Whether the sale actually closed and funded
Source linkA page you can open and check yourselfNothing — this is the one field worth trusting outright

The two gaps worth dwelling on are price and venue, because both quietly overstate what a comp is telling you.

“Reported price” is a gross figure

Marketplace sales carry a commission the reported price doesn’t show. Afternic charges a flat 10% and Sedo’s fee runs 10–20% depending on how the sale closed (Domain Name Wire’s commission survey). A domain reported at $10,000 through a marketplace may have netted the seller $8,000–$9,000 — and if you’re the one estimating what a comparable sale would net you, the gross figure is the wrong number to anchor on. Private and broker-negotiated sales sidestep marketplace commission but introduce their own opacity: a “venue” like a named broker doesn’t tell you the split they took.

Not every comp has been verified

NameBio’s coverage is large partly because it accepts self-submitted sales alongside marketplace feeds — investors reporting their own deals, with proof requested but not independently audited the way an exchange’s own feed is. The domain-investing community’s own guidance is blunt about the failure mode: an unconfirmed auction bid, a sale that never actually funded, or an inflated self-report can sit in the database looking identical to a verified marketplace transaction (NamePros’ own reporting guidance). This doesn’t make the aggregate data useless — outliers wash out across hundreds of rows — but it means a single comp, especially an unusually high one, deserves the same skepticism you’d give an asking price.

The rule of thumb: one comp is an anecdote, a handful of comps in the same shape is evidence, and the shape they’re missing — the domains that never sold at all — is usually the more important number. That’s the floor-verdict logic behind our own appraisal engine.

What makes a comp actually comparable

The word “comparable” is doing a lot of work in “comparable sale,” and it’s the step most appraisals skip. A comp is only useful in proportion to how closely it matches your domain’s shape. In rough priority order:

  • Same pattern class first. A one-word .com and a two-word .com are different markets; comparing across class before matching within it overstates or understates by multiples.
  • Same TLD, when available. TLD multipliers vary widely (our own TLD comparison quantifies this) — a .com comp says little about a .io domain’s value.
  • Overlapping words or meaning. A comp that shares an actual dictionary word with your domain is worth more as evidence than one that merely shares a length.
  • Similar length. Character count correlates with value within a class; a 4-letter and a 14-letter domain rarely belong in the same comp set.
  • Recency. The domain aftermarket moves — a five-year-old comp is weaker evidence than one from this year, all else equal.

A mixed-TLD comp list is normal and not a red flag by itself — DNJournal’s charted venues skew to strong sales, so a same-TLD match at the top of the market isn’t always available. What matters is whether the page showing you the comp is honest about the match quality, or presents every row as equally strong evidence regardless of fit.

How the comps on this site are picked

Since we’re asking you to read comps skeptically, here’s ours held to the same standard. Every appraisal on this site ranks its candidate comps by the same deterministic order described above — pattern class first, then same-TLD, then word overlap, then length proximity, then recency — and shows the top three to five matches with a direct link to the DNJournal report each one came from. Nothing about the ranking is manual or judgment-based; it’s the same rule for every domain. And comps are never folded into the appraised range itself — they’re displayed evidence, sitting next to a range computed from NameBio’s category data, so you can check whether the two agree.

When no comp in our set matches a domain’s shape, the record says so instead of stretching a comp from a different class to fill the space — an empty comps section is a more honest answer than a misleading one.

Before you cite a comp in a negotiation

  • Does it match on class, TLD, and length — or just happen to be the highest number you found?
  • Is the source link live? A comp you can’t verify against its original report is a claim, not evidence.
  • Is the price gross or net? If you’re estimating your own proceeds, subtract marketplace commission before comparing.
  • How old is it? A comp from several years ago is weaker evidence in a market that has since moved.
  • Is it one comp or several? A single high outlier proves a buyer existed once — not that one exists for you now.

Applied honestly, comps are the closest thing domain valuation has to ground truth. Applied carelessly — one favorable number, gross price, unverified, wrong class — they’re a negotiating tactic wearing the costume of data. The fields are the same either way; reading them is the difference.

This guide is for informational purposes only. It is not financial, legal, or investment advice, and it is not a certified appraisal. A domain’s real price is set by what a specific buyer actually pays — no article or model can know that in advance, and we say so instead of pretending otherwise.

Last reviewed: July 2026 · Against NameBio, DNJournal, and the marketplace-commission and reporting-verification sources linked in the body.