When to Drop a Domain: The Decision Nobody Enjoys
Dropping a domain feels like admitting the registration was a mistake, which is why most portfolios carry names years past the point anyone would defend them. But every name renewed by default adds to renewal drag, and drag is what turns a portfolio with decent sales into a money-loser.
The drop decision gets easy once you make it about the next year's money instead of the last few years' story.
The only question that matters
Would you register this name today, at its renewal price, knowing what you now know? Not "might someone someday want it" — someone might someday want anything. The question is whether this name, this year, at this cost, is a bet you'd place fresh.
What you paid for it, how long you've held it, and how clever it felt at registration are all irrelevant to next year's renewal. That money is spent either way.
Sunk cost is the enemy
The sunk cost fallacy has a specific domain-investor flavor: "I've already put five renewals into this name, I can't drop it now." Read that back — it argues that having lost money on a name is a reason to keep losing money on it. The renewals you've paid don't make the name more likely to sell; they just make the story more painful.
A useful mental trick: imagine your portfolio vanished and you were handed its cash value. Which names would you re-buy? Anything you wouldn't re-buy, you're only holding out of inertia.
Never lose a domain to a missed renewal
Sourdough tracks every expiry date via live RDAP data and emails you a renewal ladder before anything drops. 7 days free, then $10/mo. $0 due today.
Signals a name is a drop candidate
- •Zero inquiries over multiple years of holding, despite being listed and findable.
- •The trend or naming style it rode has visibly passed.
- •You can't articulate the specific buyer who would want it, in one sentence.
- •Renewal cost is high relative to any realistic sale price — common in premium-priced TLDs.
- •It exists only because it was cheap to register that day.
The annual pruning pass
Do drops in one deliberate annual pass rather than name-by-name at each expiry, when time pressure biases you toward renewing. Sort the portfolio by upcoming renewal date, mark every name renew/list/drop, and let the drop names lapse on schedule. Before a name lapses, it's worth a last cheap-exit attempt: a low fixed price or accepting a standing offer beats a drop that returns nothing.
This is much easier when renewal dates and per-domain costs are in one place — a renewal alert ladder that surfaces names 60–90 days out, like Sourdough's, effectively runs the pruning calendar for you.
Dropping cleanly
Turn off auto-renew on drop-listed names well ahead of expiry, and confirm the registrar actually shows it off — an unwanted auto-renewal is the mirror image of a lost name. Know that a dropped name typically passes through grace, redemption, and pendingDelete before release, and once it drops, getting it back means competing for it. Drops should be decisions you'd be comfortable seeing someone else catch.
Frequently Asked Questions
How do I decide whether to renew or drop a domain?
Ask whether you would register the name today at its renewal price, knowing everything you've learned holding it. Past spend is sunk and irrelevant. If the answer is no and a quick low-priced exit attempt finds no buyer, let it lapse deliberately.
Can I get a domain back after dropping it?
During the registrar grace period you can usually renew normally, and during redemption you can typically recover it for an extra fee, commonly in the tens to low hundreds of dollars. After pendingDelete the name is released and you're competing with drop-catchers like anyone else — so treat a drop as final.
How many domains should I drop each year?
There's no fixed percentage — it depends on how disciplined your acquisitions were. The healthier framing: every name should re-win its place annually. Portfolios that never drop anything are almost always carrying dead weight that a one-question test would clear out.