A domain database can supply a large candidate list, but your working research list should be smaller and more explicit. Keep the origin, purchase route and reason for interest beside each name so later checks do not depend on memory.
This workflow shows how to turn database results into a decision queue. It does not assume that every record is currently available or that buying an old name brings useful traffic.
Choose the candidate category first
ExpiredDomains.net provides deleted, pending-delete and marketplace list categories. Select the category appropriate to your buying route and read the service’s current coverage information.
For an auction or backorder source, open the actual provider’s documentation. NameJet’s guide describes its acquisition workflow, which is different from an ordinary new registration.
Our database overview explains coverage, field definitions and freshness. Your list should preserve those distinctions rather than labelling every row “available”.
Create the fields your decision requires
| Field | Purpose |
|---|---|
| Exact domain and extension | Prevent spelling or asset confusion. |
| Source URL and check date | Return to the evidence and assess freshness. |
| Acquisition stage | Distinguish registration, auction and release attempts. |
| Observed price and renewal cost | Assess the complete commitment. |
| Reason for interest | Connect the name to a project or buyer use. |
| Unresolved question and next action | Make manual research purposeful. |
Retain the original currency and identify metric providers. Mark unavailable values as unknown. A blank traffic or backlink field is not verified zero, and a failed status lookup is not confirmed availability.
Remove duplicates without losing provenance
Normalise ordinary spelling and compare exact names carefully. The same candidate may appear through several sources. Keep one working row with relevant source links rather than counting it several times.
Do not silently combine different extensions or similarly spelt names. They remain distinct assets, even when their business ideas overlap. Preserve the exact address throughout the checks and checkout process.
Assign useful research states
Use states such as rejected, needs history review, needs link inspection, eligible for price assessment and unavailable. Add a short reason when moving a row. Our discovery-funnel guide provides the broader selection process.
Keep rejection reasons searchable so the same unsuitable name does not repeatedly enter the queue through a different source.
For an illustrative queue, a clear gardening name might need archive review, while an ambiguous abbreviation could be rejected on naming fit. These are hypothetical decisions, not evidence that a particular category sells well.
Refresh the fields that affect commitment
Check the live listing and current total price immediately before bidding or registering. ICANN’s status-code guide explains lifecycle terms relevant to those checks.
Historical notes can remain useful longer, but important links or service conditions may change. Record which evidence was refreshed and which uncertainty remains. End the queue with a documented decision, rather than a spreadsheet that merely grows after every search.