Today I ran another hand-registration research pass from recent sales signals.
The filter stayed intentionally strict:
Available .com is suspicious until proven otherwise.That is still the right mindset.
The goal was not to generate a long list of names to buy.
The goal was to see whether any available .com could survive:
- clear business use
- buyer category clarity
- natural two-word structure
- outbound path before purchase
- better-alternative risk
- final registrar and market validation
The strongest public candidate from today's run was:
LabIntake.comIt is not an automatic buy.
It is a final-validate candidate.
View today's full SparkNamer hand-reg table
The full SparkNamer table keeps the generated names, availability status, source-sale signal, pattern evidence, alt-TLD notes, buyer category, outbound count, sales execution score, risk notes, and next validation action.
Research Result First
Today's hand-reg research started from recent UnreportedSales signals and ended with a small A / A- validation list.
That is a good result.
For hand-reg investing, most names should fail.
The public shortlist below shows 4 of the 8 final validation names.
The other half stays in the working SparkNamer table with the full notes, buyer categories, and validation actions.
| Domain | Status During Research | Priority | Decision | Reason |
|---|---|---|---|---|
| LabIntake.com | Available at registry during research | A | Final validate / possible buy | Best balance today. Short, natural healthcare/lab workflow phrase with a clear B2B use case and an identifiable buyer pool. |
| PermitIntake.com | Available at registry during research | A | Final validate / possible buy | Strong legaltech, govtech, construction, and immigration intake phrase. Needs buyer-list and exact-phrase validation before purchase. |
| EndpointInventory.com | Available at registry during research | A- | Final validate / possible buy | Very clear IT/security concept for tracking managed devices and endpoints, but the name is longer and may face stronger aftermarket alternatives. |
| InvoiceRisk.com | Available at registry during research | A- | Final validate / possible buy | Clear fintech/fraud/AP controls phrase with one partial exact alt-TLD signal. Functional rather than highly brandable, so outbound matters. |
My current recommendation:
Do not buy all 8 names.
Validate the top 3 first.
If buying anything, start with LabIntake.com only after final checks.Starting Signal
The input came from recent UnreportedSales signals.
The useful sale signals for today's batch were:
| Sold Domain | Pattern Signal | Research Translation |
|---|---|---|
| RashPay.com | Payment / fintech / pay signal | Invoice, risk, remit, audit, fraud, and payment-operations names. |
| OverseeAgent.com | AI agent oversight signal | Agent supervision, workflow, compliance, and monitoring names. |
| ChatAi.org | AI/chat demand signal | Useful market context, but not directly copied into weak .com combinations. |
| GenoConnect.com | Genomics / health connection signal | Lab, genetic, patient, intake, consent, and test-request workflow names. |
| CompanyComputer.com | Business IT / computer service signal | Endpoint, inventory, device, asset, and MSP-oriented names. |
| GainVisa.com and GainCitizenship.com | Immigration service signal | Permit, immigration, green card, intake, proof, and document workflow names. |
I did not treat the sales as proof that every adjacent keyword is valuable.
I treated them as starting hypotheses.
The rule was:
Recent sale signal + commercially familiar B2B workflow language.But a sale signal does not create permission to buy weak leftovers.
Availability Filter
The pipeline was strict:
1. Generate A-threshold candidates from the sale signals
2. Check the 2026-06-05 CZDS .com zone file
3. Remove names already delegated in the zone file
4. Run direct Verisign WHOIS on the remaining names
5. Apply the stricter A-level business filter
6. Keep only names that support outbound before purchaseThe numbers:
| Step | Count | Meaning |
|---|---|---|
| Generated candidates | 334 | A-threshold candidates created from the sale signals. |
Already delegated in .com zone | 290 | Most stronger-looking names were already registered or delegated. |
| Remaining after zone check | 44 | Possible available names requiring direct WHOIS confirmation. |
| Confirmed available by direct WHOIS | 41 | Available at registry during research. |
| Kept after stricter A-level business filter | 8 | Only names with clear business use and a plausible outbound path survived. |
That funnel is the point.
334 generated
41 WHOIS-available
8 final validation candidates
1 best public candidate
0 automatic buysWhy LabIntake.com Stood Out
LabIntake.com was the cleanest candidate because the phrase is immediately understandable.
Possible use cases:
Lab sample intake
Patient intake
Test request intake
Clinical lab onboarding
Genomics testing workflow
Healthcare compliance intakeThat matters because the buyer does not need a long explanation.
The domain points to a specific B2B workflow:
collecting, routing, and organizing lab requests before testing beginsPossible buyer categories:
Genomics labs
Clinical testing platforms
Lab workflow SaaS
Patient intake tools
Healthcare compliance tools
Telehealth testing platformsThe one-line pitch from the research table was:
Launch a simpler intake workflow for lab samples, patient forms, and test requests.That is the kind of sentence I want before buying a hand-reg.
It does not prove the name is valuable.
It proves the name is clear enough to validate seriously.
LabIntake.com Scorecard
| Factor | Read | Why It Matters |
|---|---|---|
| Structure | Strong | Two-word .com with no filler word. |
| Use case | Strong | Lab intake is a real workflow phrase across healthcare, testing, forms, and onboarding. |
| Buyer clarity | Strong | Labs, lab software vendors, intake platforms, and genomics companies can be manually researched. |
| Outbound buyer count | Promising | The research estimate was 40-80 possible buyers, but that still needs manual validation. |
| Exact alt-TLD evidence | Weak | Local alt-TLD evidence was 0 partial, so DotDB and exact phrase checks matter. |
| Category risk | Medium | Healthcare names need compliance, privacy, and buyer-list validation before registration. |
| Overall | A-level consideration | Best balance today, but still a final-validate candidate rather than an automatic buy. |
My read:
LabIntake.com is the best candidate today.
But best in batch does not mean buy blindly.Why PermitIntake.com Also Matters
PermitIntake.com was the second strongest name.
It has a very clear workflow:
permit application intake
construction permit intake
immigration permit intake
government document intake
legal application intakePossible buyer categories:
Permit expediters
Immigration lawyers
Govtech SaaS
Construction permitting platforms
Document intake toolsThe phrase is natural.
The buyer path is plausible.
The risk is that it may be stronger as a SaaS or lead-gen project than as passive resale inventory.
That is not a dealbreaker.
It just means the validation should focus on buyer count and exact phrase usage before registration.
The IT And Fintech Names
EndpointInventory.com was the clearest IT/security name from the batch.
The use case is direct:
endpoint inventory
IT asset discovery
MSP reporting
device inventory
cybersecurity complianceThe phrase is standard enough that buyers can understand it quickly.
The weakness is length.
For enterprise software, that may be acceptable.
For passive domain resale, I still want to compare stronger alternatives before buying.
InvoiceRisk.com was the cleanest fintech/risk name.
It fits:
invoice fraud
payment risk
AP controls
factoring risk
B2B credit workflowsIt was also the only final candidate with partial exact alt-TLD evidence:
1 partial: appThat improves confidence slightly, but not enough to skip validation.
The phrase is functional.
Functional names need a clear outbound list.
Names I Would Validate Hard, Not Buy Blindly
The final 8 names were not equal, so I am only showing the public half here.
I would separate the visible names like this:
| Tier | Domains | Action |
|---|---|---|
| Top validation | LabIntake.com, PermitIntake.com, EndpointInventory.com | Run registrar, DotDB, exact phrase, buyer-list, and better-alternative checks first. |
| Secondary validation | InvoiceRisk.com | Validate only if the top group does not clear the bar or if the buyer list looks unusually strong. |
That tiering matters.
The mistake would be turning a validation list into a shopping list.
The hidden half stays private because the full table is the working research asset, not just a blog example.
Updated Lesson
Today's run reinforced the same rule again:
Availability is not the edge.
Rejection is the edge.The research value came from cutting the list down:
334 candidates generated
290 already delegated
41 WHOIS-available
8 kept for final validationThat means 33 WHOIS-available names still did not make the final A / A- public list.
This is healthy.
If the filter is working, most available names should feel easy to reject.
Next Validation Steps
Before buying even LabIntake.com, I would run:
1. Registrar checkout availability and price
2. DotDB exact phrase and alt-TLD count
3. Google exact phrase search
4. Wayback history check
5. Trademark/common-risk scan
6. 30-50 buyer prospect list
7. Better-alternative comparison on Afternic, Sedo, Atom, and registrar search
8. Renewal rule before purchaseThe renewal rule should be decided before buying.
For example:
Renew only if there is inquiry, traffic, buyer response, real development use, or stronger market evidence.Without that rule, hand-regs slowly become portfolio clutter.
Final Takeaway
The best candidate from today's run was:
LabIntake.comThe second tier was:
PermitIntake.com
EndpointInventory.com
InvoiceRisk.comBut the practical recommendation is still conservative:
Do not buy all 8 blindly.
Validate the top 3 first.
Treat LabIntake.com as the main final-check candidate.The real lesson:
A good hand-reg is not just available.
It must have a buyer, a use case, a clean phrase, and a reason to survive renewal.Review more filtered hand-reg ideas on SparkNamer
If you want the full filtered shortlist instead of only the public example, join the email list and I will send the next batch directly.