CheckMyUsername

How we check

Most username checkers show a confident green tick for every platform. We think that confidence is often fake, so this page explains exactly what CheckMyUsername does, platform by platform — including where the honest answer is “nobody can check that from the web”.

Usernames: the public profile test

When you run a check, our server requests the name's public profile page on each platform — the same address anyone can type into a browser. In general: if the platform answers “this page does not exist”, the name is unused and we report Available. If a real profile answers, we report Taken. If the platform blocks the request, times out, or answers with something that is not a profile (a login wall, a JavaScript app shell), we report Cannot verify and give you the link to check manually. We never convert an unclear answer into a confident one.

Platform by platform

GitHub

GitHub serves a public profile page for every account, and returns a clear 404 for names that do not exist — so GitHub results are among the most reliable we offer.

YouTube

Every YouTube channel has a public handle URL (youtube.com/@name). YouTube returns a 404 for handles that do not exist, which makes handle checks reliable.

Instagram

Instagram shows most profile content only to logged-in users, so automated checks are frequently blocked by a login wall. When that happens we say “Cannot verify” rather than guessing — use the manual link to confirm in your browser.

TikTok

TikTok embeds the account's data in its public profile page, including an explicit “account not found” code for names that do not exist — which lets us give a real answer most of the time.

X (Twitter)

X serves a public page for every account and a clear not-found response for names that were never registered, so X checks are usually conclusive.

Twitch

Twitch loads channel pages with JavaScript and does not offer a public availability lookup, so server-side checks are unreliable. We attempt a conservative check and fall back to “Cannot verify” — confirm with the manual link.

Reddit

Reddit has public profile pages, but it rate-limits automated requests aggressively. When Reddit blocks our check we report “Cannot verify” instead of guessing.

Discord

Discord usernames are not public web addresses — there is no profile URL to visit and Discord offers no public availability lookup. Nobody can honestly check Discord availability from the web, so we always report “Cannot verify” for Discord and validate the format instead.

GitLab

GitLab offers a public user lookup (the same one its own website uses): it returns the account record for names that exist and an empty result for names that do not — so GitLab results are among the most reliable we offer. If GitLab's bot protection blocks the lookup, we report “Cannot verify” instead of guessing.

Kick

Every Kick channel has a public page at kick.com/name, and Kick returns a clear 404 “Channel Not Found” page for names that do not exist — so Kick results are reliable.

Steam

This checks your Steam custom URL (steamcommunity.com/id/name) — the unique, linkable part of a Steam identity. Steam serves the profile for names that exist and an explicit error page for names that do not, which lets us give a real answer. Display names are different: they are not unique, so we never check those.

Substack

Every Substack writer has a public profile at substack.com/@name. Substack embeds the profile's handle in that page when the handle exists, and answers unknown handles with a search page instead — so we can usually give a real answer, and say “Cannot verify” when the response is neither.

Domains: registries first, DNS as witness

For .com and .net we query Verisign's official RDAP registry service — the same source registrars use. A record means Registered; a registry “not found” means Available. For .io, .ai, .app, .dev and .co we query the registry's RDAP service through the public RDAP bootstrap, and because some registries' bootstrap answers are incomplete, we cross-check a negative answer against live DNS before calling a domain available. If the signals disagree or a registry doesn't answer, we say Cannot verify.

The limits you should know about

The identity score, explained

Every full check also shows an identity score (0–100) for the name. It is a transparent heuristic — not a valuation, not a trademark opinion — built from four published factors, so you can reproduce any score by hand from the results on the page:

Bands: 85+ Excellent, 65–84 Strong, 45–64 Workable, below 45 Weak. A high score means “easy to own consistently and easy for people to use” — nothing more, and it never overrides a platform's own answer.

Platforms we do not check — and why

We tested more platforms than we ship. Two well-known ones failed our honesty bar when we verified their behaviour by hand in November 2026, so they are deliberately not in the checker:

If either platform opens a public, conclusive lookup, we will add it the way we added GitLab (public user lookup), Kick (real 404s), Steam (explicit error page for free custom URLs) and Substack (handle data in the profile page, search page for free handles) in November 2026 — verified by hand first, documented here.

What we don't do

We don't use unofficial APIs, scraped databases or leaked data, and we don't store the names you check beyond a short-lived technical cache. The check runs on public information that you provide, about names — never about people.