Bad Usernames
API service that checks whether a username should be blocked, reserved, or treated as unsafe. Based on the bad_usernames list, with an English-first scope and selected multilingual reserved words where they are likely to matter.
- Development
- Alpha
- Release
- Released
- Deployment
- Live
- Latest update
- — badusernames.flurdy.io is live
- Recently updated
- Live
- Code available
Links
- Project site
- github.com/flurdy/bad_usernames_api
- Live site
- badusernames.flurdy.io
Dates
- Created
- 2019-08
- Updated
- 2026-07-09
Versions
- In development
- v0.0.1α
License
- Type
- Proprietary
Characteristics
Tags
Technologies
News
- 2026-Jul-09
- badusernames.flurdy.io is live
- 2019-Aug-30
- Added Badusernames to code.flurdy.com
Comments
- 2026-Jun-30
- Scope should be multilingual where it is practical and high-value, such as common reserved/system words like admin or support in major languages, but intentionally English-first to avoid an unbounded language-maintenance problem.
- 2026-Jun-30
- Keep the public project and service name as Bad Usernames for now: it is direct, searchable, and matches the existing bad_usernames repository. A more distinctive branded name can be revisited later if the service grows beyond username blocklist checks.