github.com/<name> and the dev category
GitHub username search
A GitHub username search checks whether github.com/<name> belongs to a user or an organization. UsernameLookup links the public profile and checks the same handle on GitLab, package registries, developer forums and the rest of 300+ public sites.
A GitHub handle rarely lives alone
Developers and open source projects tend to use one handle for the code host, the packages they publish and the forums they answer in. Searching the dev category shows that footprint in one run. These are the kinds of places the same name usually appears.
| Kind of site | Examples | Why the handle matters there |
|---|---|---|
| Other code hosts | GitLab, Bitbucket, Codeberg | Mirrors and forks often sit under the same owner name. |
| Package registries | npm, PyPI, RubyGems, crates.io | Package publishers and scopes often reuse the GitHub name, and copycat publishers try lookalikes. |
| Container registries | Docker Hub | Image names are prefixed with the publisher handle. |
| Developer forums and blogs | DEV Community, Hashnode | Write ups and answers carry the same handle as the code. |
| Coding profiles | Kaggle, LeetCode, Replit | Public profiles for competitions and practice projects. |
Examples show typical places, not a promise that each one answers in every run. Sites that block or time out are reported as unknown.
Check handles from your own tooling
Developer teams usually want this in a script, not a browser tab. The same lookup is available through the API with a Bearer key. A run returns while checks continue, with a poll URL to fetch the rest.
Invalid handles return 422 with invalid_username, and going over your plan quota returns 429 with a Retry-After header, so a loop can back off cleanly.
curl -H "Authorization: Bearer $UL_KEY" \
https://usernamelookup.com/api/v1/username/octo-dev
# one row of the sites[] array
{ "site": "GitHub", "category": "dev",
"status": "found",
"profile_url": "https://github.com/octo-dev",
"response_ms": 233 }Invented handle. Full field list on the username API page.
GitHub username rules
GitHub names are short on special characters. Only letters, digits and single hyphens are allowed, which means an underscore handle from another network does not carry over as is.
Because users and organizations share one namespace, a company that wants its brand as a GitHub organization competes with every individual who might have picked the same name. Checking early matters.
- up to 39 characters the maximum handle length
- a-z 0-9 - letters, digits and hyphens only
- no leading or trailing hyphen and never two hyphens in a row
- one namespace shared by users and organizations
- github.com/<name> the profile URL the search opens
Common reasons to search a GitHub name
Naming a project
Before publishing an open source library, a maintainer checks that the organization name is free on GitHub and that the package name is open on the registries the project will publish to.
Protecting a brand
A company sees its name used by an unrelated GitHub organization or a package publisher with a near identical name. Monitoring watches for typos, homoglyphs and separators and alerts the team by Slack or a signed webhook.
Reviewing a signup
A developer platform gets a new account that lists a GitHub handle. Trust and safety checks that the public profile exists and whether the handle has a public footprint elsewhere, as one input to a review.
For checks that go beyond developer sites, use the full username finder. Teams watching for copycat organizations and package publishers should read about fake account detection.
Unknown results and the line we do not cross
GitHub itself answers public profile requests clearly most of the time, but it does limit anonymous traffic, and the smaller registries and forums in the dev category vary a lot. Some render their profile pages with scripts or answer every URL with the same page. Where the signal is not clear, the row is unknown and links to the page so you can look.
The search only touches public profile URLs. It does not read repositories, commits or contribution history, and it never tries to work out who runs an account. A shared handle across code hosts is a hint that the profiles may be related, never proof. If your handle appears and you want it removed, use opt-out.
A user or organization answered at github.com/<name>.
GitHub returned its page for a missing account.
Rate limit, script rendered page or no answer in time.
Questions about GitHub username search
Does GitHub username search cover organizations too?
Yes. Users and organizations share one namespace on GitHub, so github.com/<name> answers for either. A found result means the name is taken by a user or an organization, and the link shows which.
Which developer sites are checked besides GitHub?
The dev category of the catalog: other code hosts such as GitLab and Bitbucket, package registries, container registries, developer forums and coding profile sites, wherever a public profile URL exists for a username.
Can I check many GitHub names from a script?
Yes. The API takes GET /api/v1/username/{username} with a Bearer key and returns every site row with its status and profile URL. Pro includes 1,000 API calls a month and Investigator 10,000.
Do you read repositories or commits?
No. The search checks whether a public profile exists and links to it. It does not read repositories, commits, contribution graphs or anything behind a login.
Search a GitHub handle across dev sites
Check github.com/<name> and the same handle on code hosts, package registries and developer forums.