How to secure a Discord server: a 10-point checklist
To secure a Discord server, require 2FA for moderators, keep Administrator to two roles or fewer, strip powerful permissions from @everyone, close the thread loophole in read-only channels, and clean up webhooks, invites and connected apps. These 10 checks cover the settings that matter most, each with the exact setting to change.
Check 1 of 10
Require 2FA for moderator actions
If a moderator's password leaks, two-factor authentication is the only thing standing between an attacker and your ban, kick, and delete buttons. With the requirement on, Discord blocks moderation actions from any account that has not enabled 2FA.
How to fix it
Server Settings, then Safety Setup, then turn on Require 2FA for moderator actions. Only the server owner can change it, and the owner needs 2FA enabled first.
In an EvaluBot audit: One of the heaviest deductions in an EvaluBot audit: 20 points.
Check 2 of 10
Keep Administrator to two roles or fewer
Administrator bypasses every channel override and grants every other permission. Each extra role holding it is one more path to a full takeover, and members often end up in those roles long after they needed them.
How to fix it
Server Settings, then Roles. Open each role, check whether Administrator is on, and replace it with only the specific permissions that role actually uses.
In an EvaluBot audit: Each Administrator role beyond two costs 4 points, up to 16.
What Administrator and the other dangerous permissions can do
Check 3 of 10
Strip powerful permissions from @everyone and roles that do not need them
Permissions such as Manage Roles, Manage Webhooks, and Ban Members are routinely handed to roles "just in case", and a few end up on @everyone, which hands them to every member. EvaluBot maps 23 sensitive permissions to every role that holds them: Manage Channels, Manage Roles, Manage Expressions, Create Expressions, View Audit Log, Manage Webhooks, View Server Insights, Manage Server, Manage Nicknames, Kick Members, Ban Members, Timeout Members, Mention @everyone, @here and All Roles, Manage Messages, Manage Threads and Posts, Mute Members, Deafen Members, Move Members, Priority Speaker, Use External Apps, Create Events, Manage Events, Pin Messages. Staff roles hold some of these legitimately, so treat the list as a prompt to review.
How to fix it
In Server Settings, then Roles, open @everyone first and turn off anything beyond basic member permissions. Then use View Server as Role to see what each other role can really do, and remove anything it does not need.
In an EvaluBot audit: A takeover permission such as Administrator or Manage Roles on @everyone costs 20 points, and elevated ones such as Manage Messages cost 4 each, up to 12. Roles other than admin and bot roles holding Manage Server, Manage Roles, Manage Channels or Manage Webhooks cost 5 points each, up to 15.
Check 4 of 10
Close the thread loophole in read-only channels
Announcement and rules channels are usually locked by denying @everyone the Send Messages permission. Threads use separate permissions, so if @everyone can still Create Public Threads, anyone can open a thread and post inside the channel you locked.
How to fix it
Edit the channel, open Permissions, select @everyone, and deny Create Public Threads, Create Private Threads, and Send Messages in Threads. Or turn off Create Public Threads on the @everyone role to close it in every channel at once.
In an EvaluBot audit: A thread-permission gap in any channel costs 10 points.
Check 5 of 10
Limit who can mention @everyone and @here
Mention Everyone turns one compromised account into a ping to every member, which is exactly what scam-link raids rely on.
How to fix it
Turn off Mention @everyone, @here, and All Roles on @everyone and on every role except your staff roles. EvaluBot lists every role that has it.
In an EvaluBot audit: @everyone being able to mention @everyone costs 15 points.
Check 6 of 10
Audit your webhooks
Anyone who has a webhook's URL can post as it, without being in your server. Old webhooks from abandoned tools and leaked URLs are a common spam route.
How to fix it
Server Settings, then Integrations, then Webhooks. Delete any webhook you cannot tie to a tool you still use, and regenerate the URL of any webhook that may have been shared. EvaluBot lists every webhook with its creator, and its permission alerts flag each new incoming webhook.
In an EvaluBot audit: More than 15 webhooks costs 5 points.
Check 7 of 10
Expire your invites
A never-expiring invite posted years ago can still be sitting on a public list, feeding raids and unwanted joins.
How to fix it
Server Settings, then Invites, lists every active invite with its uses. Revoke stale ones, and when you create an invite, set Expire After and a maximum number of uses. EvaluBot flags never-expiring and high-use invites.
Check 8 of 10
Review connected apps and bots
Every bot you add brings its own permissions, and a bot that is abandoned or compromised keeps them.
How to fix it
Server Settings, then Integrations. Remove apps you no longer use, and check the role of each remaining bot for Administrator or other powerful permissions. EvaluBot reports who added each one.
Check 9 of 10
Check what onboarding hands out
Onboarding prompts assign roles automatically. If a prompt option grants a role with moderation permissions, every new member who picks it gets them.
How to fix it
Server Settings, then Onboarding. Open each prompt and confirm every role it grants is a cosmetic or access role with no moderation permissions.
Check 10 of 10
Set a verification level that fits your server
Verification gates who can talk the moment they join. A public server on None or Low is an easy target for throwaway accounts.
How to fix it
Server Settings, then Safety Setup, then Verification Level. Medium or higher suits most public communities.
In an EvaluBot audit: A verification level of None costs 6 points.
Run every check in one command
Working through this list by hand takes a while on a large server, and it is easy to miss one channel override among hundreds. EvaluBot runs all of these checks for you and more:
- It inspects ten sections of your server and scores it out of 100, listing every deduction with how to fix it.
- Its audits are read-only, so they never change anything they find.
- Recommendations are grouped into critical, general, and optional, in a report you can get as a PDF, HTML or JSON.
- Its live permission alerts tell you when someone grants Administrator or another risky permission, and who did it.
- It is free to start, with one audit per server each month and the critical alerts. Premium raises that to 15 audits and every alert.
See how the score is calculated, try the score calculator, or read everything an audit checks. For the worst case, see how to protect a Discord server from nukes.
FAQ
How do I make my Discord server more secure?
Require 2FA for moderator actions, keep Administrator to two roles or fewer, remove powerful permissions from @everyone, close the thread loophole in read-only channels, delete webhooks you no longer use, expire old invites, remove unused bots, check what onboarding hands out, and set a verification level that fits your server.
What is the most important Discord security setting?
Requiring 2FA for moderator actions. It stops a moderator account with a leaked password from banning, kicking or deleting. Close behind is keeping Administrator and other takeover permissions off @everyone and off roles that do not need them.
How do I check my Discord server's permissions?
Open Server Settings, then Roles, and review each role, starting with @everyone. View Server As Role shows a channel exactly as a role's members see it. EvaluBot maps 23 sensitive permissions to every role in one read-only audit.
Can a bot secure my Discord server for me?
A bot can find the problems. EvaluBot audits your settings and alerts you to risky permission changes, but its audits are read-only, so you make every fix yourself, or with Premium apply channel permission templates to many channels at once.
See how your server really scores.
Add EvaluBot, run one command, and get a scored report with every fix explained. Read-only from start to finish.
Join the Discord servers already running EvaluBot.
Running a busy server? Premium gives it 15 audits a month, every risky change as an alert, fix plans and more. See Premium