Counts destructive actions
Channel and role deletes, bans, kicks, dangerous permission grants, new webhooks and bots, and mass channel or role creation are each watched with their own limit.
SERVER PROTECTION
Anti-nuke and anti-raid protection for your Discord server
Server protection: a feature of Rezaletbot, the free Discord bot.
If a staff member or a bot starts deleting channels, wiping roles or banning members in a short time, Rezaletbot sees it in Discord's audit log right away, strips the attacker's dangerous permissions and tells you. When a raid hits it pauses invites and can lock the server with panic mode; it stops suspicious accounts at the door, slows spammers with a heat system and verifies new members with a captcha. Everything starts off, and you set the limits.
🛡️ Anti-Nuke🚨 Anti-Raid🔒 Panic mode🚪 Join gate🔥 Heat system✅ Verification
mod-logAnti-Nuke
Audit logNightAdmin · channel deletions · 30 s0 / 3
- NightAdmin deleted #announcements
- NightAdmin deleted #rules
- NightAdmin deleted #general
Rezaletbot BOT
HIGHLIGHTS
What server protection can do
Strips dangerous permissions
Whoever crosses a limit loses their roles with Administrator, Manage Server, Manage Roles and similar permissions, or gets kicked or banned if you prefer. A bot that attacks is kicked.
Cleans up behind them
Bots the attacker added are kicked and webhooks they created are deleted, so the attack can't carry on through something they left behind.
Catches raids
Lots of joins in a short time (10 in 10 seconds by default) count as a raid. Welcome messages pause and an alert goes to your moderation channel.
Pauses invites by itself
During a raid, Discord's own invite pause is switched on for the time you choose (30 minutes by default), and Discord lifts it when time runs out.
Holds back brand-new accounts
Accounts younger than the age you set are timed out until they reach it (28 days at most) or kicked right away. It works independently of raid protection.
Panic mode with a one-click undo
During an attack, sending is turned off, invites pause and the verification level goes up; when it ends everything goes back exactly as it was, even if the bot restarts.
A heat system slows spammers
Speed, repeats, mentions and links build up heat that cools over time. At the limit, a timeout, and the member is told why. Hot channels get temporary slowmode.
Observe first, enforce later
In observe mode the join gate and heat system touch nobody and only report who would be caught. Start in one click with Light / Balanced / Strict presets.
ANTI-NUKE
A compromised staff account is stopped in seconds
Rezaletbot watches the server's audit log live and counts each destructive action per person. If a staff member or bot crosses a limit within your window (30 seconds by default), say by deleting 3 channels, the bot steps in at once: it removes their roles with dangerous permissions, kicks bots they added and deletes their webhooks. What happened is posted to your moderation log channel and sent to the server owner by DM.
- Default limits: channel / role deletes 3, bans 3, kicks 5, permission grants 2
- Each limit is 0–50; 0 stops watching that action
- Response: remove roles, kick or ban
ANTI-RAID
When a wave of joins hits, the door closes
If the number of members you set joins within your window (10 in 10 seconds by default), the bot calls it a raid. With Lock selected it switches on Discord's invite pause so nobody can join through an invite; with Alert only it just lets you know; with Start panic mode the server goes into panic mode. Members who join during the raid can get a 6-hour timeout, a kick or a ban if you want. Once things calm down, the raid ends and a summary of how many joined and what was done is posted.
- 3–100 joins within 5–120 seconds
- Invites stay paused for 5 minutes up to 24 hours
- No welcome messages during a raid
EXEMPTIONS & NEW ACCOUNTS
Trusted people pass, brand-new accounts wait
The server owner is never counted, and you add the roles and users you trust to a list. The new account filter is separate from raid protection: anyone whose account is younger than your setting is timed out as soon as they join, and the timeout lifts by itself once the account is old enough (Discord allows 28 days at most), or they're kicked straight away. Every action is written to the Action log.
- Trusted roles and users list
- Account age 0–365 days; 0 turns the filter off
- Every action in the Action log
PANIC MODE
Lock the server during an attack, then put it back
Panic mode turns on by hand (/protection panic or one button in the panel) or by itself when a raid or Anti-Nuke fires. Invites (and DMs if you want) pause, sending is turned off or slowed in public channels and the verification level goes to High; people joining meanwhile are timed out, kicked or banned. When time runs out or you end it, the bot puts every channel's old permission back without touching other changes you made meanwhile. The old settings are kept in the database, so a bot restart can't leave the undo half done.
- 5 minutes – 24 hours, 30 minutes by default
- Automatic start on a raid or Anti-Nuke
- Every channel is restored exactly when it ends
JOIN GATE
Suspicious accounts stay at the door
Every joining account is checked: names with an invite or link, names matching your blocked patterns (like *nitro* or steam*, look-alike letters and digit tricks included), optionally accounts without a profile picture, and groups of accounts joining within 90 seconds that were created in the same half hour or have similar names. Caught accounts are timed out for a day, kicked or banned, and alerts are batched. Observe mode shows who would be caught without touching anyone. You can also set a trust score limit: accounts that had protection actions, bans, kicks or violations in this server before stay out when they come back, while an ordinary new account with no records gets in easily. Other servers' records aren't used.
- Up to 50 blocked name patterns
- Catches groups of similar accounts (bot armies)
- Risk-free trial with observe mode
- Trust score limit: accounts with a bad history stay out
HEAT SYSTEM
Spammers heat up, normal chat doesn't
Each message adds heat to its author: fast typing, repeating the same message, mentions, links, files and emoji floods add more, and new accounts count 1.5x. Heat cools every 10 seconds, so normal chat never reaches the limit. At 60% the member gets a "slow down" warning; at the limit they're warned, timed out (twice as long if it happens again within an hour), kicked or banned, their recent messages are deleted and they're told why. If many people speed up in one channel at once, it gets 5 minutes of slowmode and then goes back. With the adaptive limit on, not everyone is measured the same way: the limit stretches for long-time members with a clean record and tightens for newcomers or recently warned members, and someone suddenly writing 5x faster than usual (a sign of a hijacked account) gets extra heat.
- Limit 50–300, cooldown 1–50 heat per 10 s
- Moderators and Manage Messages holders are exempt
- Channel heat: temporary slowmode
- Adaptive limit: ×0.6–×1.5 per member
VERIFICATION
New members confirm with a button, a captcha or on the website
The bot posts a message in your verification channel. When a new member presses the button (or types the 5-character code from the picture in captcha mode, or passes Cloudflare's human check on rezaletbot.com in web mode) they get the role you picked, and welcome auto-roles are given then too. The code is valid for 5 minutes and three wrong tries need a new one. Optionally, members who don't verify in time get a short DM and are kicked. You set channel permissions so @everyone sees only the verification channel and the verification role sees the rest.
- Button, picture captcha or web with Cloudflare
- Role + auto-roles after verifying
- Kick the unverified: 0–10080 minutes
SETUP
Ready in three steps
- 01
Move the bot's role up and grant permissions
Anti-Nuke needs the View Audit Log permission to work at all. The bot also needs Manage Roles, Kick Members, Ban Members, Timeout Members, Manage Webhooks and Manage Server to pause invites. Its role must sit above the roles of the staff you want it to be able to stop.
- 02
Turn protections on and pick limits
Sign in with Discord, pick your server and switch Anti-Nuke and Anti-Raid on separately. Set the limits, responses, how long invites stay paused, the new account age and trusted roles on the same screen, then save.
Web panel → Server settings → Moderation → Protection - 03
Check it with /protection status
Type /protection status in Discord: it shows which protections are on, any permissions the bot is missing and an ongoing raid, if there is one. Use /protection lock to pause invites by hand during an attack and /protection unlock to open them again.
COMMANDS
Use it from Discord
/protection statusShows protection settings, missing bot permissions and an ongoing raid./protection lockPauses invites right away for 5–1440 minutes, 60 by default./protection unlockOpens paused invites again./protection panicStarts panic mode right away with the panel settings, for 5–1440 minutes./protection panic-endEnds panic mode and restores channels, invites and the verification level./protection trustShows a member's trust score, the reasons and their heat system limit multiplier.FAQ
Questions about server protection
Why didn't Anti-Nuke stop anyone?
There are two common reasons. Without View Audit Log the bot can't see who did what, so Anti-Nuke doesn't run at all. If the bot's role is below the attacker's, Discord won't let it remove their roles or kick them; the bot still sends a "could not stop them" alert. /protection status lists any missing permissions.
Will my own staff get punished while reorganizing the server?
The server owner is never counted. Add the role of staff who'll do a big rework to the trusted roles list. That's also why channel and role creation limits start high (10 in 30 seconds); set a limit to 0 and that action isn't watched at all.
Are deleted channels and roles restored?
Not yet. Protection stops the attack and records what happened; it doesn't recreate deleted channels and roles. You'll see who deleted what in the alert in your moderation log channel, in the Action log and in server logs if they're on.
When do invites open again after a raid?
When the time you chose in the panel runs out (30 minutes by default, 24 hours at most), Discord opens invites itself, even if the bot is offline. To open them earlier, use /protection unlock or resume invites from the server menu in Discord.
Does the new account filter affect real members too?
It can: a genuinely new account gets caught too. That's why the filter starts off (0 days), and with the timeout option the member isn't kicked; the timeout lifts by itself once the account is old enough. A moderator can remove it by hand at any time. 1–7 days is enough for most servers.
Will panic mode mess up my channel permissions?
No. Before starting, the bot saves every channel's @everyone permission to the database, and when it ends it only reverts the sending permissions it changed; other changes you made meanwhile are kept. Even if the bot restarts in between, it finishes the job on startup. It also restores the verification level only if it's still the one the bot set.
Will the heat system time out people just chatting?
Not with the default settings: someone writing a message every 3 seconds never reaches the limit, because heat cools every 10 seconds. It usually catches accounts sending the same message over and over, mass-mentioning or writing several messages a second. To be sure, turn on observe mode first and see who would be caught in the alert channel without touching anyone.
Does the trust score block new users too?
No, being new alone isn't enough: even an account under a day old with no picture and no records stays around 72. What really lowers the score is the account's negative records in this server (earlier protection actions, bans, kicks, violations); other servers' records aren't used. The limit is off by default; before turning it on you can see who would be caught in observe mode. If you specifically want to hold back new accounts, the new account filter fits better.
How do I set up channel permissions for verification?
Create a verification role (keep the bot's role above it). In your other channels turn off View Channel for @everyone and allow it for the verification role; in the verification channel @everyone can see but not write. Pick the role, channel and method in the panel, save, then press "Send message".
MORE
You might also like
ModerationProfanity is stopped by Discord's own AutoMod before the message ever lands, and repeat offenders get a warning, then a timeout, then a bot block.Auto moderationInvite links, sites you haven't allowed, mass mentions and spam are stopped by Discord's own AutoMod before they're sent.Server logsTurn logging on and Rezaletbot keeps track of what happens in your server: deleted and edited messages, members joining and leaving, roles given and taken, bans, channels created and deleted.All featuresMusic, karaoke, moderation, integrations and more.
Give your server a rhythm.
Behind every great moment, there’s a great song.
Add to Discord✳