GuidesEspañolContact

How to protect your Discord server from raids

A raid is a mass of accounts joining a server to flood it with spam, insults or malicious links. It is prevented with several layers: entry verification, AutoMod, closed permissions, an anti-raid bot and a clear plan for what to do when it happens. No single layer is enough on its own.

  • ⏱ 3 min read
  • 7 sections
  • 2 diagrams

Updated:

What a raid is and why it happens

A coordinated group joins your server at once, usually with lots of new accounts, and starts posting spam, insults or dangerous links. Creator servers are a frequent target because they are visible, and a big stream can attract real new members and people who want to cause trouble at the same time.

First layer: what Discord already gives you

Before you install anything, use what Discord itself has:

  • Server verification level: it can require a verified email, a minimum account age or time in the server, or a verified phone.
  • AutoMod: filters words, blocks suspicious links and detects mention spam.
  • Mandatory two-factor authentication for anyone with moderation permissions.
  • Pausing invites if you are under attack.
Four layers of raid protection on Discord: verification level and AutoMod, locked permissions, captcha and an anti-raid bot.
Each layer stops what got past the one before.

Second layer: permissions that are properly closed

Most of the damage depends on what a newcomer can do. Take away from @everyone the ability to mention everyone, upload files, embed links or create invites, and give those permissions only to verified roles. Check that no bot role has more permissions than it needs.

Third layer: captcha verification

A verification channel where a new member solves a captcha before seeing the rest of the server stops bots and automated accounts. Whoever does not verify does not get into the conversation channels.

Fourth layer: an anti-raid bot

An anti-raid bot watches what a person cannot watch 24 hours a day:

  • It detects spikes in joins within seconds.
  • It checks the age of the accounts that join.
  • It applies an automatic action: kick, ban or lock the server temporarily.
  • It logs everything so you can review afterwards.

What to do if a raid is already happening

With the server under attack, the order matters:

  • Pause invites and raise verification to the maximum.
  • Turn on the bot’s lockdown mode, or temporarily limit the writing channels.
  • Ban the raid accounts in bulk, not one by one.
  • Check the logs to understand how they got in.
  • Tell your community what happened and that it is under control.
Five steps to stop a raid in progress: pause invites, raise the verification level, turn on slow mode, remove the raid accounts and check the logs.
In order, and calmly.

What I do

In my moderation and security services I set up anti-raid, captcha verification, auto-ban, logs and permission control, and I leave the response plan explained to your moderation team.

Your checklist

0/4

Tick what you already have. It stays saved in this browser.

Was this guide useful?

Frequently asked questions

Can a raid destroy my server?

It can flood it with spam and force you to clean up, and if permissions are open it can cause bigger damage. With closed permissions, verification and an anti-raid bot, the impact drops a lot.

Is Discord AutoMod enough?

It is a good first layer, but it does not replace entry verification or a bot that detects spikes in joins. The recommended approach is to use several layers.

Does a captcha annoy real members?

It is a step of a few seconds. Members who really want to join complete it, and you lose the bots.

How long does it take to set up?

Basic security is part of the complete server, which is usually ready in 24 to 48 hours. Advanced anti-raid is in the Pro plan, in 2 to 4 days.

Need a hand with this?

Message me on Discord or WhatsApp. I reply in under 24 hours.

Link copied