NamingSignalalpha

App name generator · evidence included

Generate app names that survive the obvious checks.

Describe the app, audience, and reason to switch. NamingSignal creates a broad field, checks the domain endings you choose, and keeps app, package, and developer-name collisions visible before a favorite becomes expensive.

Step 1 · Your project

Describe what you’re naming

One sentence is enough. NamingSignal analyzes it, infers the brief, and checks availability in one run.

Saved in this browser
Try an example
0 / 250,000 bytes

Infers your target customer, desired outcome, and naming guidance from the description. Everything stays editable, and skipping it is fine: the same analysis runs automatically when you generate.

Checking .com · .app · .io · .ai · any ending can passDomain endings, search breadth, and handle checks
Customize
1. Which domain endings can win?

Select the endings you would genuinely launch on. Up to five can be checked in one run.

“Likely unregistered” is a calibrated registry signal at check time, not a purchase guarantee. Unsupported or timed-out checks stay unresolved.
2. How broad should the search be?

More candidates improve the odds in crowded domain namespaces.

FunctionalOutcomeMetaphorLateral
3. Which handles should we check?

Advisory only. A taken handle never blocks a name. GitHub gets an exact automated check, other platforms get one-click manual links, and the deep check suggests handle alternatives when the exact one is taken.

Your naming run

Generate 150 names · check 600 domainsAcross .com, .app, .io, .ai · keep names where at least one selected domain passes.
01

Built from the product

Use one sentence, a prompt, or a README instead of generating from a single category keyword.

02

App-aware collision checks

Review selected domains plus Apple, GitHub, npm, and PyPI signals where those sources can answer reliably.

03

Shortlist with reasons

Keep score dimensions, hard blockers, unknowns, and rejection reasons separate from taste.

Practical answers

Before you name, check, or ship

Availability is time-sensitive evidence. A final choice still needs current registrar verification, spoken testing, cultural review where relevant, and appropriate legal clearance.

Does NamingSignal guarantee that an app name is available?

No. It reports source-backed observations and calibrated inferences. App stores, registrars, common-law use, and trademarks still require current manual and professional review.

Can I start from an app README or product prompt?

Yes. Paste bounded text, upload a README, or provide a safe public URL, then inspect and edit the brief before generating names.

What makes this different from a random app-name list?

The generator and checker share one decision record: product context, distinct creative directions, domain evidence, namespace signals, scores, blockers, and shortlist actions.