Do I need a verification bot or is Discord's built-in protection enough?

For most course and SaaS servers, built-in verification level, AutoMod, onboarding and raid alerts are enough. Add a CAPTCHA or security bot if you are public, large, or already being raided.

Why are members getting scam DMs from accounts in my server?

Spam accounts join to see the member list and DM people. Use the DM spam settings in Safety Setup, raise the verification level, and tell members staff never DM first.

Does a paid community still get spam bots?

Far less. If access is granted only after payment through a role bot like Whop or LaunchPass, bots can't get past the paywall. Free lobby channels can still be targeted.

How to stop spam bots joining my Discord

Updated November 12, 2026 · Moderation

Layer it: raise the verification level, turn on AutoMod's mention spam and suspected spam rules, gate chat behind rules acceptance or onboarding, enable Discord's raid and DM spam protections in Safety Setup, and add a security bot like Wick if you are a target. During an active raid, pause or delete your invite links first, then clean up.

Anti-spam layers on Discord and what each one stops
Layer	Where	What it stops	Cost
Verification level	Server Settings > Safety Setup	Fresh throwaway accounts posting instantly	Free, built in
AutoMod mention + spam rules	Server Settings > Safety Setup > AutoMod	Mass-mention raids, scam links, known spam	Free, built in
Rules acceptance / Onboarding	Onboarding or Safety Setup (Community servers)	Drive-by bots that never click through	Free, built in
Raid protection & DM spam settings	Server Settings > Safety Setup	Join waves and members DMing scams to your members	Free, built in
Pause invites	Server menu security actions / Invites list	New joins while a raid is in progress	Free, built in
Security bot (e.g. Wick)	Bot dashboard	Raids, nukes, compromised admin accounts	Free tier + premium; check vendor
Paid gate (Whop/LaunchPass)	Your checkout	Almost all spam: bots don't pay	Platform fees; check vendor

1. Raise the verification level

In Server Settings > Safety Setup, set the verification level. 'Low' requires a verified email; higher levels add an account-age wait, a wait after joining, or a verified phone number. For a public course or SaaS server, a medium-to-high level stops most freshly created bot accounts. Community servers must be at least 'verified email'.

2. Turn on AutoMod's spam rules

Full walkthrough: Discord AutoMod setup guide.

Mention spam with a low limit, block + alert + timeout.
Suspected spam content: block + alert.
A custom keyword rule for scam bait: *free nitro*, *gift*, *airdrop*, *dm me*, look-alike domains.
A member profile filter for impersonation names like *support* or *admin* plus your brand.

3. Gate chat behind your rules

On a Community server, require new members to accept your rules before they can talk, and use Onboarding questions to assign a member role. Spam scripts often fail at this step. If you want channels fully hidden until acceptance, see how to hide channels until rules are accepted.

4. Raid protection and DM spam

Safety Setup includes raid protection and DM spam settings: alerts when an unusual wave of joins or DMs happens, sent to a mod channel, plus options that make it harder for new members to DM others. Turn the alerts on and point them at #mod-log. Tell members in #rules that staff will never DM them first; most server spam today is scam DMs, not channel posts.

5. Add a security bot if you are a target

Large, public or crypto-adjacent servers get hit by coordinated raids. Security bots such as Wick add anti-raid lockdowns, join-age gates and anti-nuke protection (stopping a compromised admin from deleting channels). Give the bot only the permissions it asks for and keep its role above the roles it manages. For paid communities, the strongest filter is the paywall itself; see how to charge for Discord access.

When you are being raided right now

Pause invites (security actions in the server menu) or delete your public invite links from Server Settings > Invites.
Temporarily raise the verification level to the highest setting.
Turn on slowmode in the channels being hit.
Bulk-remove the raid accounts (a moderation bot's purge or ban tools help) and review #mod-log.
Rotate to a fresh invite link once things are quiet, and lower the verification level again.

Quick answers

how to stop spam bots joining my discord: Raise the verification level, enable AutoMod's mention spam and suspected spam rules, require rules acceptance or onboarding before members can chat, turn on raid and DM spam alerts, and only share invite links you can rotate.
Do I need a verification bot or is Discord's built-in protection enough?: For most course and SaaS servers, built-in verification level, AutoMod, onboarding and raid alerts are enough. Add a CAPTCHA or security bot if you are public, large, or already being raided.
Why are members getting scam DMs from accounts in my server?: Spam accounts join to see the member list and DM people. Use the DM spam settings in Safety Setup, raise the verification level, and tell members staff never DM first.
Does a paid community still get spam bots?: Far less. If access is granted only after payment through a role bot like Whop or LaunchPass, bots can't get past the paywall. Free lobby channels can still be targeted.

What to do next

Every LaunchMyServer template ships with a mod-log channel, staff roles, a rules channel and an anti-spam checklist ready to apply.

Browse templates Take the 6-question planner

Related guides

Sources

Checked: November 12, 2026. Discord changes features and menus often; if something looks different, the official help center is the source of truth. LaunchMyServer is not affiliated with Discord.