Platforms — unclaimed

MECHANICS

How the scanning actually works.

Every scan follows the same shape, tuned per platform: generate a batch of candidates, check each one at a pace that platform actually tolerates, and report exactly what came back — nothing inferred, nothing reserved.

GENERATE

Random characters within a length range, or variations built around a base word you supply.

FILTER

Candidates that the platform's own naming rules would reject outright are dropped before a single check runs.

CHECK

One at a time, never concurrently, at a randomized delay tuned to what each platform actually tolerates.

CLASSIFY

Every result — hit or miss — is logged. Nothing is held, reserved, or claimed on your behalf.

WALKTHROUGH

One scan, start to finish.

Say you want variations on the word “ember” across Telegram. You type a base word and a length range once. From there, roughly this happens:

00:00.0 generating candidates from "ember" — 40 requested 00:00.1 22 valid after filtering telegram's naming rules 00:00.1 starting sequential checks, ~1.4s average delay 00:31.4 ember.hq checked TAKEN 00:33.0 emberhq checked AVAILABLE 00:34.6 the.ember checked TAKEN 00:36.1 ember_official checked AVAILABLE ... 01:02.8 22 checked — 6 available, 14 taken, 2 limited 01:02.8 results saved — nothing claimed, nothing reserved

Discord

CHECKED AGAINST

Discord's own unauthenticated username-availability endpoint.

PACE

The most conservative of the three — Discord's rate limit is aggressive enough to lock a run out after roughly twenty checks, so every scan stays well under that line by default.

DISTINCT STATUS

Also reports DENIED for names Discord's validation rejects outright — not a failure, just not checkable.

CHECKED AGAINST

Telegram's public t.me profile pages.

PACE

Polite and strictly sequential, with automatic backoff on rate limits and an early abort if too many checks fail in a row — a broken run stops itself instead of burning through candidates.

DISTINCT STATUS

No DENIED state — invalid and unregistered both simply read as not found.

TikTok

CHECKED AGAINST

The real status signal embedded in TikTok's own profile page — not the visible page text, which appears regardless of whether the account exists.

PACE

More headroom than Discord's, though still rate-limit aware — no login, no proxy, no workaround for a limit if one is hit.

DISTINCT STATUS

No DENIED state, same as Telegram — TikTok doesn't distinguish invalid from not-found at the HTTP level.

RESULT STATUSES — WHAT EACH ONE MEANS

AVAILABLE Nobody's claimed it. Yours to take, directly on the platform.

TAKEN Already claimed by someone else.

LIMITED The platform rate-limited the check itself — not a verdict either way. The scan backs off and, where possible, retries.

ERROR A network problem or an unexpected response — also not a verdict. Logged honestly rather than guessed at.

DENIED Discord only — rejected by the platform's own naming rules before a check was even needed.

unclaimed_ only ever reads availability. No candidate is ever registered, reserved, or claimed by us on any platform — scanning and claiming stay two separate, manual steps, always in your hands.

MECHANICS, ANSWERED

Common questions.

What does “live” actually mean?

Every check happens in real time against the platform itself when you run a scan — not against a cached list or a snapshot from earlier. What's shown is what's true right now, for that one moment.

What happens if I get rate-limited?

The scan backs off automatically and reports it honestly as LIMITED rather than guessing whether a name is open. Each platform's pacing is tuned specifically to make this rare.

How accurate is it?

As accurate as the platform's own response. unclaimed_ doesn't infer or estimate — every status comes directly from what that platform returned for that exact candidate.

Can two people scan the same name and get different answers?

Only if the name's availability actually changed between checks — same as it would if you checked it by hand twice, minutes apart.