Suggested Keywords

We plan to sunset Spam Defender later in the summer of 2023. Until then, Spam Defender will remain online, but no further development will take place.

We recommend that you install Hashbot as the best protection for your community.

Here's a list of recommended keywords to block in your server. To block a new keyword, use the /block keyword command. After blocking a new keyword, run the /scan keywords command to scan your server for matching usernames.

If you'd like to block this full list of keywords in your server, you can use the /block defaults command.

Good to know: Keywords will match any part of a username, so the keyword help would match the username helpdesk, the keyword announcement would match the username Minting Announcements, etc.

admin
alert
announcement
assist
automate
automatic
binance
bonus
captcha
coinbase
collab.
collabland
customer
desk
doodle3lander
doodles3lander
giveaway
guide
helper
info
mee6
mee 6
mee.6
metamask
moderator
moonokaybear
news|
news |
notification
official
presale
pre-sale
pre sale
probot
postsale
post-sale
post sale
raffle
release
server
service
support
sushiswap
ticket
uniswap
verification
verify
welcome
.land
|bot
| bot
|news
| news

Good to know: In general, it is not recommended to block mod, bot, or other short keywords that could be found in the username of a real user. For example, the name Modhi would be banned if you blocked the keyword mod.

What's the difference between blocking a username and a keyword?

Blocked usernames only match full names. Blocking the username luke would only catch users named luke, Luke, ŁÜKĘ, etc.

On the other hand, blocked keywords match all partial names. Blocking the keyword luke would catch users named luke, lukenamop, ŁÜKĘnamop, etc.

If I block the username of one of my team members, would they be banned?

No, they would not be banned! Spam Defender automatically ignores any users with any of the following permissions: Manage Channels, Manage Roles, Manage Server, Kick Members, Ban Members, and Manage Messages. If you have any team members that don't have one of these permissions, you can use the /whitelist @user command to manually protect them.

Last updated