How does UsernameChecker know if a GitHub username is taken?

For GitHub we query the public Users API. HTTP 200 means the login exists (taken). HTTP 404 means GitHub does not currently have that login (likely available). Results can still change if GitHub rate-limits the request.

Is this a people-finder or OSINT tool?

No. UsernameChecker is a branding and handle-availability tool. It does not identify people, scrape private data, or map accounts to real-world identities.

Are availability results guaranteed?

No. Platforms can block automated checks, show soft 404 pages, or reserve names. Always confirm on the service itself before you register or buy a brand.

What are GitHub username rules?

GitHub logins may be 1–39 characters, use letters, numbers, and single hyphens, and cannot start or end with a hyphen or contain consecutive hyphens. See our GitHub username guide for examples.

Free handle checker

Check if a username is available

See whether a handle looks free or taken on GitHub, social networks, and storefronts. Built for creators and developers choosing a brand — not for finding people.

Try a GitHub login such as octocat or open the full platform checker.

How the checker works

UsernameChecker looks up a candidate handle the same way open-source availability tools do: it asks each platform whether that public profile URL or API endpoint exists. We do not log into accounts, we do not scrape private pages, and we do not sell contact lists.

You enter a handle. We normalize @name and reject strings that look like file probes rather than usernames.
We probe public endpoints. GitHub uses the official Users API. Other networks use public profile URLs or documented JSON endpoints where they exist.
You verify on the site. A “likely available” result is a hint. Register the name on GitHub or the app itself before you print it on packaging.

GitHub checks use the public Users API

GitHub is the most reliable network in this checker because it publishes a documented API. For a login such as octocat we request https://api.github.com/users/octocat with a descriptive User-Agent. A 200 response means the username is taken. A 404 response means GitHub does not currently have that user. Rate limits (403/429) are reported as unknown rather than guessed.

That approach matches how community checkers such as socialscan treat GitHub: availability via the Users API, not HTML scraping. Read the full rules on our GitHub username guide.

What we check — and what we do not

The tool covers developer profiles (GitHub, GitLab), social apps (Instagram, TikTok, YouTube, X), and storefronts (Etsy, Shopify). It does not check domain names, email addresses, or trademark databases. It is not a reverse-image search and not a “find this person” directory.

Use it when you are naming a product, open-source project, or shop.
Use the username choosing guide if you need ideas that still pass GitHub’s character rules.
Do not use it to harass, impersonate, or investigate private individuals.

Why results can disagree with the live site

Some networks return a marketing page for missing users (a soft 404). Others hide profiles, require login, or throttle bots. We label those rows unknown. GitHub is usually clearer because the Users API returns a real 404. Always click through before you commit to a brand.

Frequently asked questions

Is UsernameChecker free?

Yes. The public checker is free. The site may show Google ads to cover hosting. See the privacy policy for cookies and ad partners.

Do you store the usernames I search?

Recent public searches may appear on the recent searches page and in the sitemap so Google can index example checks. Do not search secrets, passwords, or private identifiers.

Can I check several names at once?

Yes. Separate handles with spaces or commas. Each name is still subject to length and character rules (up to 39 characters, matching GitHub’s maximum).

How do I contact you?

Email contact@usernamechecker.net or use the contact page.