by marteinn

This is a opinionated blacklist of words that you might not like to see used as usernames in your se...

457 Stars 28 Forks Last release: Not found MIT License 146 Commits 24 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


This is a opinionated blacklist of words that you might not like to see used as usernames in your service (think, or

The editable blacklist can be found in list_raw.txt and is categorized into six sections:

  • Privileges User privilege terms to prevent faked authority. Example: root, super
  • Code: Programming terms that you might want to avoid in a url. Example: void, null
  • Terms: Various technical terms. Example: request, system
  • Financial: This is for the spammers/scammers. Example: payment, invoice
  • Sections: Common website pages and sections. Example: faq, help
  • Actions: User actions. Example: delete, create

You can try the blacklist using the tool Username checker.

Please note that this list does not contain any curse words, there are other lists for that.

How it works

This repro contains standard data files, just pick the format of your choosing.


Blacklist has been ported to different languages.


Want to contribute? Awesome.

  • Checkout the origin/develop branch
  • First edit
  • When you are done, run
    python scripts/
  • ... This script will update the various list files.
  • Done? Send a pull request.

Release start

These hooks will automatically bump the application version when using

git flow release ...
chmod +x $PWD/git-hooks/
ln -nfs $PWD/git-hooks/ .git/hooks/post-flow-release-start
ln -nfs $PWD/git-hooks/ .git/hooks/post-flow-hotfix-start

Git workflow and release management

This project uses gitflow and semantic versioning.


The-Big-Username-Blacklist is released under the MIT License.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.