Brandable vs keyword: two different games
We keep these in separate mental buckets:
— Keyword/exact-match: buyer is searching for the term, demand is measurable, sale is faster but ceiling is capped.
— Brandable (invented words): no search demand to lean on, slower sit, but a funded startup can pay a multiple of cost.
— Marketplace fit: keyword names move on Afternic; brandables sit better on Brandbucket/Squadhelp with their curation.
📌 Pick of the day: don't list a made-up brandable on Afternic and expect traffic to sell it. Venue mismatch kills more flips than price.
Why it matters: the same name priced right on the wrong platform is invisible.
We keep these in separate mental buckets:
— Keyword/exact-match: buyer is searching for the term, demand is measurable, sale is faster but ceiling is capped.
— Brandable (invented words): no search demand to lean on, slower sit, but a funded startup can pay a multiple of cost.
— Marketplace fit: keyword names move on Afternic; brandables sit better on Brandbucket/Squadhelp with their curation.
📌 Pick of the day: don't list a made-up brandable on Afternic and expect traffic to sell it. Venue mismatch kills more flips than price.
Why it matters: the same name priced right on the wrong platform is invisible.
Closing the deal without getting burned
The sale isn't done at "yes." Mechanics threads every flipper should bookmark:
Use escrow, always
— Escrow.com or marketplace-native (Dan/Afternic). Never "send PayPal F&F first"
— Buyer pays in, you push the domain, escrow releases. Boring = safe
Push vs. transfer
— Same registrar: instant account push, no 60-day lock drama
— Cross-registrar: auth code + transfer, slower, mind the post-transfer lock
The 60-day trap
— A name you just acquired can't transfer out for 60 days — disclose if selling fast
📌 Pick of the day: keep buyer and yourself on the same registrar when possible — the push is instant and dispute-proof.
The sale isn't done at "yes." Mechanics threads every flipper should bookmark:
Use escrow, always
— Escrow.com or marketplace-native (Dan/Afternic). Never "send PayPal F&F first"
— Buyer pays in, you push the domain, escrow releases. Boring = safe
Push vs. transfer
— Same registrar: instant account push, no 60-day lock drama
— Cross-registrar: auth code + transfer, slower, mind the post-transfer lock
The 60-day trap
— A name you just acquired can't transfer out for 60 days — disclose if selling fast
📌 Pick of the day: keep buyer and yourself on the same registrar when possible — the push is instant and dispute-proof.
FAQ: How do I avoid buying a trademarked name by accident?
A UDRP complaint can wipe your name and your reputation. Quick screen:
Before you bid
— Search the exact term on the USPTO TESS database (free) and the EUIPO register.
— Plug it into a general web search — if a real company actively uses it, walk away.
Red flags
— Coined brand words, misspellings of big brands, or 'brand + keyword' combos (nikeshoes-style). All UDRP magnets.
📌 Pick of the day: generic dictionary words and descriptive phrases are the safest flips. If a name only has value because it echoes a known brand, that value isn't yours to sell.
(Source: USPTO TESS and WIPO's UDRP case index, both free to search.)
—
Для любителей tool comparisons — @stack_compare
A UDRP complaint can wipe your name and your reputation. Quick screen:
Before you bid
— Search the exact term on the USPTO TESS database (free) and the EUIPO register.
— Plug it into a general web search — if a real company actively uses it, walk away.
Red flags
— Coined brand words, misspellings of big brands, or 'brand + keyword' combos (nikeshoes-style). All UDRP magnets.
📌 Pick of the day: generic dictionary words and descriptive phrases are the safest flips. If a name only has value because it echoes a known brand, that value isn't yours to sell.
(Source: USPTO TESS and WIPO's UDRP case index, both free to search.)
—
Для любителей tool comparisons — @stack_compare
How to actually read a drop list
Most people scroll the daily expired feed and quit at page two. A tighter way to triage:
Sort first
— By referring domains, not by "backlinks" (the second number is mostly spam)
— By Wayback age: a name registered in 2009 with a 14-year gap is a redirect risk, not a gem
Kill fast
— Anything with a Chinese/PBN footprint in the anchor cloud
— Hyphens and numbers unless the keyword is genuinely premium
Keep
— Clean .com, one dictionary word or tight two-word brandable, real archived content
The skill isn't finding good names — it's discarding 95% in ten minutes so you can study the 5%.
📌 Pick of the day: filter every list by "first seen in Wayback before 2015" and read only those.
Most people scroll the daily expired feed and quit at page two. A tighter way to triage:
Sort first
— By referring domains, not by "backlinks" (the second number is mostly spam)
— By Wayback age: a name registered in 2009 with a 14-year gap is a redirect risk, not a gem
Kill fast
— Anything with a Chinese/PBN footprint in the anchor cloud
— Hyphens and numbers unless the keyword is genuinely premium
Keep
— Clean .com, one dictionary word or tight two-word brandable, real archived content
The skill isn't finding good names — it's discarding 95% in ten minutes so you can study the 5%.
📌 Pick of the day: filter every list by "first seen in Wayback before 2015" and read only those.
Backorder stacking, explained plainly
A name you want is pending delete. Do you place one backorder or several? Roundup of how the pros split it:
The case for stacking
— Each registrar has different catch infrastructure; more orders = more shots at the drop
— DropCatch, SnapNames and Dynadot Backorder catch different names well on different days
The catch (literally)
— If two of your own backorders catch, you don't pay twice — but if it goes to auction, you're now bidding against nobody and everyone
— Stacking only helps on contested names; for a quiet drop, one order is plenty
📌 Pick of the day: stack only when a name shows 3+ backorders already placed — otherwise you're paying for redundancy nobody needed.
A name you want is pending delete. Do you place one backorder or several? Roundup of how the pros split it:
The case for stacking
— Each registrar has different catch infrastructure; more orders = more shots at the drop
— DropCatch, SnapNames and Dynadot Backorder catch different names well on different days
The catch (literally)
— If two of your own backorders catch, you don't pay twice — but if it goes to auction, you're now bidding against nobody and everyone
— Stacking only helps on contested names; for a quiet drop, one order is plenty
📌 Pick of the day: stack only when a name shows 3+ backorders already placed — otherwise you're paying for redundancy nobody needed.
Pricing an end-user sale without guessing
The hardest part of flipping isn't buying — it's naming a number that doesn't scare off or underprice. Threads worth reading on comps:
Where to anchor
— NameBio sold-comps for the exact keyword, last 24 months only (older data lies)
— Filter by extension: a .com comp doesn't price your .io
Read the buyer, not the name
— A funded startup pays 5 figures for the same string a solo founder won't touch above $800
— Check their LinkedIn headcount and last raise before you reply
Common trap
— Quoting your cost-plus margin instead of the buyer's value. They don't care you paid $12.
📌 Pick of the day: pull 5 NameBio comps before every outbound — it turns "make an offer" into a defendable ask.
The hardest part of flipping isn't buying — it's naming a number that doesn't scare off or underprice. Threads worth reading on comps:
Where to anchor
— NameBio sold-comps for the exact keyword, last 24 months only (older data lies)
— Filter by extension: a .com comp doesn't price your .io
Read the buyer, not the name
— A funded startup pays 5 figures for the same string a solo founder won't touch above $800
— Check their LinkedIn headcount and last raise before you reply
Common trap
— Quoting your cost-plus margin instead of the buyer's value. They don't care you paid $12.
📌 Pick of the day: pull 5 NameBio comps before every outbound — it turns "make an offer" into a defendable ask.