When to drop a domain

A domain is the cheapest commitment device in software. Twelve dollars and you have a real artefact for the half-formed idea in your head. The downside is that the cost compounds. A domain you bought in a moment of excitement is the same renewal charge as a domain you actually use, every year, forever.

So the question is not whether to drop. It is which ones, and when.

The honest test

Run this on every domain you are about to renew:

Have I used this domain in the last 12 months?Used means pointed somewhere, sent a single email from, mentioned in a meaningful conversation, or actively planning to use in the next 12 months.
Would I buy it today at the renewal price?Not the original price. The renewal price. Some registrars inflate the second year significantly.
Is there a specific concrete plan attached to this domain?A line on a calendar, a doc, a person waiting on it. Not a vibe.

Two no answers and a yes: probably drop. Three nos: definitely drop. The rare two-yes-one-no domain is worth keeping for another year if the no is question one and you genuinely believe the plan will execute.

The categories that should usually go

Names you bought from a 2am brainstorm

You have not opened that doc in nine months. The product idea has changed since. You bought four domains for it and only one survived. The other three should go.

Misspellings of names you own

Defensive registrations sound smart. They are usually theater. The number of typo-squatting incidents you will actually prevent in 12 months is zero. Drop them unless the misspelling matches a high- traffic search you have actual data on.

Names tied to dead projects

If a project is properly dead, its domain is just paying tribute. Dropping it is closure. Keeping it is denial.

TLDs that did not become a thing

You bought a .ninja or a .rocks in a moment of optimism in 2014. If you have not used it by now, you will not. The renewal cost might be reasonable, but so is letting it go.

Domains in dead categories

Investor portfolios accumulate names in categories that turned out not to be lucrative (Web3 names that are not the canonical name, AI-generated buzzword .ai names that lost their resonance). Treat them like equities in a sector you no longer believe in.

The categories that should usually stay

Your name, your handle, your brand. Annoying to lose, hard to get back.
Domains pointing to live products or live identities.
Domains with measurable inbound (real traffic, real backlinks, real email).
Names that genuinely capture a category you are betting on.

The graceful drop

When you decide to drop, do it properly:

Turn off auto-renew first. If you are inside the auto-renew window, contact support.
Add a note in your portfolio manager with the drop reason and target date. Future-you will want the context.
Update DNS so nothing breaks when the domain goes inactive. Remove email forwards. Audit any service still referencing it.
If the domain has any commercial value, consider listing it on a marketplace before letting it expire. Some names are worth more than the renewal.
Mark it as Bucket 3 in your portfolio and check back at expiry.

The pattern that prevents the problem

Better than a yearly cull is a system that prevents the build-up. When you buy a new domain, tag it with a project. If you delete the project, the domains in it surface for review. If a project goes dormant for over a year, its domains surface for review.

Lemon Domains does this naturally: domains live in projects, projects have names, projects can be archived. The structure does the work so you do not have to.

The shorter version

You bought the domain because you cared. If you do not care anymore, stop paying for it.