Bulk search guide
How to review a large domain list without false positives
Bulk domain search is most useful when it makes a long list easier to review without weakening the meaning of availability. This tool accepts up to 5,000 .com names and compares them with DomainShelf's registry-verified catalog. It is a fast database lookup, not 5,000 simultaneous registrar requests.
That distinction protects both speed and accuracy. A verified match has prior authoritative availability evidence and is rechecked before purchase. A name that is not in the catalog remains unknown here; it is never silently labeled unavailable or available.
How the 5,000-name catalog search works
The workflow is designed for quick ingestion, ordered results, and a clean handoff to deeper research.
1. Paste or import a list
Add bare labels or .com domains separated by spaces, commas, semicolons, or lines. CSV and TXT files are accepted up to the stated file limit. Bare labels receive .com, inputs are normalized, and duplicate names are removed.
2. Match the verified catalog
The database is searched in submitted order. No live registrar traffic runs in catalog mode, so the request can return quickly without turning a high-volume public query into an unsafe burst against an upstream provider.
3. Filter, sort, and export
Review verified matches separately from unknown names, sort by input order, spelling, length, score, or listed price, and export the complete result set as CSV. Only 100 rows render per page to keep the browser responsive.
Read the statuses before using the data
A bulk result is valuable only when every state has a precise meaning. The export preserves those meanings so downstream spreadsheets and reviews do not convert uncertainty into a claim.
Verified available
The name appears in the current publishable catalog because it passed an authoritative registrar check within the catalog's freshness policy. It is still not reserved and receives another availability check before purchase.
Not in verified catalog
DomainShelf has no publishable catalog match for that submitted name. The domain may be available, registered, unsupported, stale, or simply not researched yet. Use the exact search for a current answer on a priority candidate.
Score and price fields
These fields help compare published DomainShelf candidates; they are not registry appraisals or predictions of resale value. A high score does not alter availability, trademark risk, renewal cost, or buyer demand.
Good uses for bulk domain search
Naming workshops
Collect ideas from several participants, normalize the combined list, and identify catalog matches without manually searching one row at a time. Keep unknown candidates for a later exact-check shortlist.
Portfolio triage
Compare a structured acquisition list and export a durable review file. Input-order sorting preserves an existing priority sequence, while length and score sorting reveal different editorial cuts.
Agency or client review
Prepare a transparent deliverable that distinguishes verified catalog candidates from unresearched names. This is more defensible than presenting every blank DNS result as available.
Tips for cleaner, faster batches
Use one candidate per row
A simple single-column file is easiest to audit, although the importer also recognizes common separators. Remove commentary and unrelated spreadsheet fields before upload.
Keep your source order
Put the strongest names first if priority matters. You can return to input-order sorting after exploring alphabetical, shortest-first, score, or price views.
Exact-check the finalists
Run current registrar checks on the small set you might act on. Catalog evidence is deliberately revalidated because domain status can change after publication.
Questions people ask before the next step
Short answers to the decisions that most often change how these results should be used.
- Does bulk search check all 5,000 names live?
- No. The current tool searches DomainShelf's indexed, verified catalog with zero live registrar calls in the request. That architecture keeps the interface fast and avoids pretending a partial or rate-limited scan is complete.
- What does not in catalog mean?
- It means only that no current publishable catalog record matched the submitted .com name. It does not establish that the domain is registered, unavailable, available, valuable, or safe to use.
- Why are duplicate names removed?
- Duplicate removal keeps the 5,000-name allowance focused on unique candidates, prevents repeated rows from distorting counts, and produces a cleaner export. The first normalized occurrence determines its input position.
- Will exporting include results outside the visible page?
- Yes. Pagination limits browser rendering to 100 rows at a time, while CSV export uses the complete returned result set. Filters affect on-screen review, not the meaning of the saved status fields.
- Can I import extensions other than .com?
- This catalog workflow is intentionally .com-focused, and bare labels become .com names. Use the extension directory to compare TLD choices and the exact domain search to request current evidence for a complete non-.com candidate.