Name creator + availability checker

Describe it. Get names you can actually use.

Start with one sentence or a full README. NamingSignal creates 100–200 options, checks the domain endings you choose, and ranks the survivors: names whose preferred domains came back likely unregistered.

Unlike a chat answer, every availability claim here comes from a live registry check with a source and a timestamp, and you can re-run it. Using Claude Code or Codex? One paste sets up the API

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

What does your business, product, or project do?

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.

Any selected endingAt least one must be likely unregisteredEvery selected endingAll selected domains must pass

“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.