devbio
FeaturesExamplesMarketplaceToolsBlogsPricingFAQ
Sign inClaim your slug
All free tools

Username availability checker

One handle. Every platform a developer cares about. We probe each in parallel and show what's free, what's taken, and which platforms refuse to tell us straight.

On this page

  • Why one handle everywhere
  • Where we check
  • Why some show “unknown”
  • Privacy
  • FAQ
Guide

One developer. Fifteen platforms. Pick the handle once.

Inconsistent handles are a quiet career tax. Someone reads your blog post, wants to follow you on GitHub, finds nothing; they don't try harder. The fix is dull and obvious: one handle, every platform. This tool is the fastest way to see whether yours is still on offer.

Why one handle everywhere

Your name is a search term. When someone hears about you in a Slack DM and types @yourname into GitHub or X, the lookup either lands on you or it lands on nothing. Consistent handles compound: more inbound from blog backlinks, more clean references in podcast credits, fewer "I think this is the guy who…" intros.

You also pay the tax in reverse — every time someone wants to mention you in their post and types out three different handles, you've lost a beat of attention to the formatting friction. Reduce the surface.

Lock down your handle

Get devbio.me/yourname before someone else does.

devbio is the canonical hub link for your developer identity. Your bio, projects, GitHub, MRR, resume — one URL.

devbio.me/
devbio

The developer-first bio platform.

© 2026 devbio.me

Product
ComponentsExamplesMarketplaceResume builderPricingBlogs
Free tools
All toolsOpen Graph previewerMRR calculatorUsername availabilityTech-stack badges
Company
Twitter

Where we check

The list, grouped by what it tells us:

  • Identity — devbio, Product Hunt, Medium. These are profile-shaped URLs people land on when they're looking for you specifically.
  • Developer — GitHub, GitLab, npm, PyPI, Hugging Face, dev.to, Hashnode. Code, packages, models, writing.
  • Social — Twitter / X, Bluesky, Mastodon (instance: mastodon.social), Reddit, LinkedIn. Where conversations happen.

We probe each platform's public profile URL in parallel. When the URL returns a profile page, the handle is taken. When it returns 404, the handle is available. When the platform refuses to answer that question (more on that below), we mark the result "unknown" and link the URL so you can verify in a tab.

Why some platforms show "unknown"

A few platforms deliberately make availability hard to probe. Bluesky uses opaque DIDs and renders client-side, so a HEAD request reveals nothing. Twitter / X serves a 200 response for every URL — the "not found" state lives inside the JavaScript bundle. LinkedIn blocks crawlers entirely.

We could lie and call those "available" — that's what some checkers do. We'd rather mark them honestly and link the URL. False positives lead to bad decisions (you pick a handle, find out later it was actually taken on X).

Privacy

We don't log handles or store check history. The probes happen server-side because most platforms block CORS, but the only thing that hits our database is your devbio claim if you go on to sign up. No tracking pixels. No analytics on tool input.

FAQ

What if my preferred handle is taken on one platform?
You have three options, in order of preference: (1) pick a different handle that's free everywhere, (2) suffix a single underscore on the platform where it's taken and keep your canonical handle elsewhere, (3) reach out to the owner — handles get released to graveyards on every platform after enough inactivity, and on GitHub specifically you can request the handle if the user hasn't logged in for a year.
Can I check a specific Mastodon instance?
Not yet — we probe mastodon.social only, which catches the long tail of indie devs. Self-hosted instances by definition can't be checked without knowing the URL. Future: a dropdown for the top 5 instances.
What's a good length for a developer handle?
5-12 characters. Long enough to feel deliberate, short enough to fit in a Twitter handle and an email prefix. Avoid numbers when you can — they read as "the second person who wanted this handle, settling."
Should I match my handle to my devbio slug?
Yes. That's the whole point — one canonical handle that resolves to your bio. devbio reserves the matching slug for you the moment you claim it, even if you don't publish for weeks.
Why isn't [some platform] on the list?
We added the platforms most developers care about in 2026. Drop us a suggestion on the GitHub repo if you'd like one added — Stack Overflow, Replit, CodeSandbox, Stackblitz, JSFiddle are likely next.
GitHub
Privacy
Terms