Today I ran a hand-registration research pass using two different input sources: recent sales keywords and a large uploaded candidate list.
The goal was not to prove that hand-regs are easy.
The goal was to see whether any available .com name could survive a stricter investor filter:
Can I explain the buyer, use case, risk, and holding logic before I spend the registration fee?For this public post, the strongest candidate was:
CertificateOps.comIt was not an automatic buy. It was the only name from the sales-keyword batch that deserved deeper validation before registration.
View today's full SparkNamer hand-reg table
The full SparkNamer table includes the generated names, uploaded-list survivors, rejected candidates, WHOIS status, risk notes, buyer-thesis notes, validation priority, and final watch / skip / register decisions.
Research Result First
Today's research was based on two input layers:
1. Recent sales keywords from UnreportedSales
2. An uploaded prefix/suffix .com candidate listThe important result:
No automatic A-level hand-reg buy today.That is not a failed research day.
It is actually the point of the newer filter.
The goal is not to find a name to buy every day. The goal is to avoid adding weak available .com names just because they passed a registrar search.
The strongest names from today's final filter were:
| Domain | Priority | Decision | Reason |
|---|---|---|---|
| CertificateOps.com | B+ | Final validate / possible buy | B2B security / PKI operations angle. Best candidate from the sale-keyword batch, but still needs buyer count, DotDB, exact phrase, Wayback, and registrar checkout. |
| TicketEcho.com | B | Validate only | Clean enough ticketing/events phrase from the uploaded list. Needs exact phrase and buyer validation. |
| EmergingApi.com | B | Validate only | Developer/API tooling angle. Natural enough to inspect, but not an automatic investor buy. |
| FiberAssistant.com | B | Validate only | AI assistant / telecom-fiber support angle. Needs real buyer evidence. |
| VerifySmiles.com | B | Validate only | Dental/identity/verification angle is possible, but the use case must be proven. |
| ViaCertified.com | B | Validate only | Certification/trust angle. Needs phrase validation before buying. |
| TraceBranding.com | B | Validate only | Branding/marketing phrase. Possible agency/tool use case, but buyer demand is unproven. |
My practical recommendation:
Do not batch-buy from this run.
If buying anything, validate CertificateOps.com first.
Treat the uploaded-list names as watch/validation candidates only.Starting Signal
The recent sales keyword input came from UnreportedSales data for June 10, 2026.
The sale keywords I extracted included:
aide
agentic
certificate
IQ
auto
group
cannabis
aged
well
steel
engine
demand
pros
tech / tecSome useful sale examples behind those keywords:
| Sold Domain | Sale Price | Pattern Clue |
|---|---|---|
| HumanAide.com | $2,495 | Human / aide / assistant-style naming |
| AgenticCertificate.com | $250 | Agentic + certificate / trust / credential naming |
| SteelEngine.com | $28,650 | Industrial noun + machine/tech word |
| DemandPros.com | $3,600 | B2B demand / sales / marketing keyword |
| CrownAutoGroup.com | $30,000 | Brand + auto + group business naming |
I did not treat these sales as proof that every similar keyword is valuable.
I treated them as seed signals.
The rule was:
A sale creates a hypothesis.
It does not create permission to buy weak leftovers.Batch 1: Sales-Keyword Candidate Generation
From the sales keywords, I generated two-word .com candidates using B2B modifiers such as:
Ops
Desk
Pilot
Flow
Guard
Proof
Audit
Ledger
Metrics
Signal
Logic
Quote
ClaimsThen I ran the batch through two checks:
1. .com zone-file check
2. Direct Verisign WHOIS checkThe result:
| Step | Count | Meaning |
|---|---|---|
| Generated candidates | 220 | Two-word .com names created from recent sale keywords and B2B modifiers. |
Already delegated in .com zone | 193 | Most clean two-word names were already taken or delegated. |
Not found in .com zone | 27 | Possible available candidates requiring WHOIS confirmation. |
| Confirmed available by direct WHOIS | 25 | Available at registry during research. |
| Taken after WHOIS confirmation | 2 | Not found in zone was not enough; WHOIS caught the difference. |
This is an important lesson:
Zone-file absence is not the final answer.
Direct WHOIS still matters.Sales-Keyword Final Candidates
The available names from the sales-keyword run were mostly not strong enough for a buy.
The best final set:
| Domain | Status | Priority | Decision | Use Case | Risk |
|---|---|---|---|---|---|
| CertificateOps.com | Available at registry | B+ | Final validate / possible buy | Certificate lifecycle operations, TLS/SSL/PKI automation, security operations | Exact alt-TLD count was 0 in local files; buyer count and exact phrase must be checked. |
| CertificateDesk.com | Available at registry | B | Validate only | Certificate request desk, PKI support workflow, internal IT certificate support | May sound like an internal helpdesk more than a product category. |
| CertificatePilot.com | Available at registry | B | Validate only | AI/copilot-style certificate management automation | More brandable than exact-match; buyer intent is less direct. |
| CertificateProof.com | Available at registry | B- | Validate only | Certificate verification, proof of certification, compliance evidence | Better alternatives like CredentialProof or CertificateVerify may be stronger. |
| DemandClaims.com | Available at registry | B- | Validate only | Legal demand letters, claims workflows, insurance/legal automation | Phrase is ambiguous outside legal context. |
| AideMetrics.com | Available at registry | B- | Watch | AI aide / assistant analytics | Aide is likely weaker buyer language than agent or assistant. |
| AideSignal.com | Available at registry | C+ | Watch | Assistant signal monitoring or care-aide tracking | Needs a very specific buyer/use-case thesis. |
| DemandAide.com | Available at registry | C+ | Watch | Demand generation assistant / sales AI aide | Feels generated; better alternatives likely exist. |
| SteelClaims.com | Available at registry | C+ | Watch | Steel warranty, construction claims, industrial claims workflow | SteelEngine.com sold high, but this phrase is much weaker. |
| DemandFleet.com | Available at registry | C+ | Watch | Fleet demand planning, logistics capacity, on-demand fleet operations | May be backwards compared with natural buyer language. |
My read:
CertificateOps.com was the only name worth deeper validation.
Everything else stayed in validate/watch.Batch 2: Uploaded Prefix/Suffix Candidate List
The second input was an uploaded file:
prefix_master_0.0.1.txt_suffix_master_0.0.1.txt_com_2026-06-08_16-45-59_missing_from_A.txtThis file had 552 lines.
After parsing and normalizing valid .com domains:
541 valid .com domains checked
473 available at registry
68 taken
0 unknownThat is a useful reminder:
Many available names are still available for a reason.Availability is only the first gate.
The second gate is quality.
The third gate is buyer count.
The fourth gate is renewal discipline.
Uploaded List: Final Filtered Result
After direct WHOIS and heuristic filtering, these were the stronger names kept for review.
This is not a buy list.
It is a validation list.
| Domain | Priority | Decision | Score | Category | Risk |
|---|---|---|---|---|---|
| TicketEcho.com | B | Validate only | 63 | Ticketing/events | Needs buyer-count and exact phrase validation. |
| EmergingApi.com | B | Validate only | 62 | Developer/API tooling | Needs buyer-count and exact phrase validation. |
| FiberAssistant.com | B | Validate only | 62 | AI assistant / productivity | Needs buyer-count and exact phrase validation. |
| VerifySmiles.com | B | Validate only | 62 | Verification / trust | Needs buyer-count and exact phrase validation. |
| ViaCertified.com | B | Validate only | 61 | Certification / trust | Needs buyer-count and exact phrase validation. |
| TraceBranding.com | B | Validate only | 60 | Branding/marketing | Needs buyer-count and exact phrase validation. |
| GridTickets.com | B- | Watch / low priority | 59 | Ticketing/events | Likely weak leftover unless specific buyer evidence appears. |
| HopResearch.com | B- | Watch / low priority | 59 | Research/analytics | Likely weak leftover unless specific buyer evidence appears. |
| JobClassroom.com | B- | Watch / low priority | 59 | Education | Likely weak leftover unless specific buyer evidence appears. |
| RebelEarning.com | B- | Watch / low priority | 59 | Education | Likely weak leftover unless specific buyer evidence appears. |
| VectorRoof.com | B- | Watch / low priority | 59 | Contractor/local service | Likely weak leftover unless specific buyer evidence appears. |
| AwardSeal.com | B- | Watch / low priority | 58 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| BeePrivacy.com | B- | Watch / low priority | 58 | Privacy/security | Likely weak leftover unless specific buyer evidence appears. |
| CircleMCP.com | B- | Watch / low priority | 58 | AI/developer protocol tooling | Likely weak leftover unless specific buyer evidence appears. |
| DockerMonitor.com | B- | Watch / low priority | 58 | Monitoring / DevOps | Likely weak leftover unless specific buyer evidence appears. |
| FocusRegistry.com | B- | Watch / low priority | 58 | Infrastructure / registry tooling | Likely weak leftover unless specific buyer evidence appears. |
| HostingMaps.com | B- | Watch / low priority | 58 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| InputConnect.com | B- | Watch / low priority | 58 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| LaunchCache.com | B- | Watch / low priority | 58 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| LoveMCP.com | B- | Watch / low priority | 58 | AI/developer protocol tooling | Likely weak leftover unless specific buyer evidence appears. |
| MemoMCP.com | B- | Watch / low priority | 58 | AI/developer protocol tooling | Likely weak leftover unless specific buyer evidence appears. |
| TeaPicture.com | B- | Watch / low priority | 58 | Developer/API tooling | Likely weak leftover unless specific buyer evidence appears. |
| DebitMail.com | B- | Watch / low priority | 56 | Payments | Likely weak leftover unless specific buyer evidence appears. |
| DeerVisa.com | B- | Watch / low priority | 56 | Immigration / travel services | Likely weak leftover unless specific buyer evidence appears. |
| EmailTale.com | B- | Watch / low priority | 56 | Messaging | Likely weak leftover unless specific buyer evidence appears. |
| FinancePride.com | B- | Watch / low priority | 56 | Finance | Likely weak leftover unless specific buyer evidence appears. |
| GrowthSample.com | B- | Watch / low priority | 56 | Marketing/growth | Likely weak leftover unless specific buyer evidence appears. |
| MoviePayment.com | B- | Watch / low priority | 56 | Payments | Likely weak leftover unless specific buyer evidence appears. |
| OliveAgTech.com | B- | Watch / low priority | 56 | Agriculture tech | Likely weak leftover unless specific buyer evidence appears. |
| PharmaWerx.com | B- | Watch / low priority | 56 | Healthcare/pharma | Likely weak leftover unless specific buyer evidence appears. |
| PlaneContract.com | B- | Watch / low priority | 56 | Legal/contract workflow | Likely weak leftover unless specific buyer evidence appears. |
| AnchorClassroom.com | B- | Watch / low priority | 55 | Education | Likely weak leftover unless specific buyer evidence appears. |
| NanoLabResearch.com | B- | Watch / low priority | 55 | Research/analytics | Likely weak leftover unless specific buyer evidence appears. |
| SynthLearning.com | B- | Watch / low priority | 55 | Education | Likely weak leftover unless specific buyer evidence appears. |
| TeachSelling.com | B- | Watch / low priority | 55 | Education | Likely weak leftover unless specific buyer evidence appears. |
| AccountAGI.com | B- | Watch / low priority | 54 | AI | Likely weak leftover unless specific buyer evidence appears. |
| AgencyInvite.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| AgiPortrait.com | B- | Watch / low priority | 54 | AI | Likely weak leftover unless specific buyer evidence appears. |
| ExactSpeech.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| GuestCollab.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| RetainFast.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| SavingWorx.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| SecurityShots.com | B- | Watch / low priority | 54 | Security | Likely weak leftover unless specific buyer evidence appears. |
| VetPrints.com | B- | Watch / low priority | 54 | Needs manual category | Likely weak leftover unless specific buyer evidence appears. |
| Web3Sell.com | B- | Watch / low priority | 53 | Web3 | Likely weak leftover unless specific buyer evidence appears. |
| ZeroTrustMusic.com | B- | Watch / low priority | 53 | Security | Likely weak leftover unless specific buyer evidence appears. |
Why Most Names Stayed Out Of The Buy List
The uploaded list contained many available domains, but many had one or more problems:
- unclear buyer category
- awkward word order
- speculative Web3/crypto wording
- sensitive or trademark-adjacent terms
- playful brandables without obvious commercial buyer path
- too many stronger alternatives likely available on marketplaces
Examples of names I would not treat as investor-grade without a very specific development plan:
AppleMansion.com
AndroidZeta.com
BlogJesus.com
CryptoEscort.com
RegenSex.com
ZeroTrustMusic.com
WildlifeSwag.com
WiredJoker.comSome may be usable for a project.
That is different from being good passive resale inventory.
Updated Pattern Lesson
Today's run reinforced a rule I am starting to trust more:
Available .com is suspicious until proven otherwise.This does not mean available domains are always bad.
It means the burden of proof is higher.
Before buying, I want to see:
| Filter | What I Need To See |
|---|---|
| Natural phrase | The name should pass the radio test and not feel backwards. |
| Buyer count | At least 30 plausible buyers before buying, especially for hand-reg inventory. |
| Better alternatives | If many stronger names are available or cheaply listed, this one is probably weak. |
| Exact phrase / DotDB | Exact phrase evidence and alt-TLD registrations improve confidence. |
| Use-case clarity | I should be able to explain who would use it in one sentence. |
| Sales execution | If there is no obvious outbound path, the name should be much stronger. |
| Renewal rule | Define before buying: renew only with inquiry, traffic, buyer response, or stronger market evidence. |
What I Would Do Next
If I continue this batch, I would not register from the table immediately.
I would run deeper validation on only these:
CertificateOps.com
TicketEcho.com
EmergingApi.com
FiberAssistant.com
VerifySmiles.com
ViaCertified.com
TraceBranding.comFor each one:
1. Registrar checkout price
2. DotDB exact phrase count
3. Google exact phrase check
4. Wayback history check
5. Trademark/common-risk scan
6. Build 30-50 possible buyers
7. Compare better alternatives on Afternic/Sedo/AtomOnly after that would I decide whether any name deserves a registration fee.
Final Takeaway
Today's research produced a lot of available domains.
But the real output was discipline:
Generated list: useful.
Available list: interesting.
Final buy list: almost empty.For hand-registration investing, that is probably healthy.
The more I research this, the more I think the edge is not in generating names.
The edge is in rejecting almost all of them.
Review more filtered hand-reg ideas on SparkNamer
If you want the full filtered shortlist instead of only the public example, join the sticky email box and I will send the next batch directly.