Skip to content
The audit

The Discord server audit, section by section

Run /audit and EvaluBot reads ten sections of your Discord server, from roles and channels to AutoMod and the last 45 days of risky activity. It scores the setup out of 100, lists every fix in a PDF, HTML or JSON report, and tells you what changed since your last audit. The audit never changes a thing.

Running an audit

One command, two options.

Both are optional. Run it bare for a full PDF audit now, narrow it to some sections, or switch to HTML or JSON. To run one later, use /auditschedule once.

  • The server owner and anyone with Administrator can run it, and the report covers everything. The reply is private to them.
  • When a run would use the server's last audit of the month, it asks first, with Run and Cancel buttons, and warns more strongly when the audit covers only some sections. Only the person who ran it can answer, and Run checks again that they are still the owner or have Administrator.
  • A scheduled or recurring audit is built for whoever booked it, when it runs. If they have lost Administrator by then, channels they cannot see are left out (counted, never named), and so are the ban list without Ban Members, webhooks without Manage Webhooks, the audit log without View Audit Log, and invites, integrations, AutoMod rules and server templates without Manage Server. The report says what was left out, and the score still covers the whole server.
  • A live progress bar shows each step. When many audits are running, you see your place in the queue and an estimated start time, and it starts on its own.
  • One audit runs per server at a time, scheduled and recurring ones included. A second /audit in the same server is asked to wait, and told what is holding it up, such as an audit and who started it, a scheduled or recurring audit, or a fix plan check, with its place in the queue or when it began.
  • If the queue is full, you are asked to try again in a few minutes, and nothing is counted.
  • If Discord will not return a section, the audit carries on without it, names what is missing, and counts as a partial audit.
/auditsectionsroles,channels,automod
format
Optional. PDF, the default, which opens with one click; HTML for the interactive report that opens in any browser; or JSON for the raw data.
sections
A comma-separated list of section keys, or all, the default. It suggests the next section as you type.
The ten sections

What every section of the report shows.

Each section names the bot permission it reads with. Every permission is optional: decline one and only that section is limited.

Server

server
  • Server ID, owner ID, creation date, member count, locale and description
  • Default notification level, vanity URL, verification level, 2FA requirement for moderators, media content filter and NSFW level
  • Community mode, and the system, rules, public updates and safety alerts channels
  • Boosts, the boost progress bar, emoji, sticker and soundboard counts, and the server's Discord feature flags
  • Discord's safety signals: Activity Alerts, when Discord last detected a raid or DM spam, and whether invites or DMs are paused
  • Who can find and join: Server Discovery, the server widget, server templates and Rules Screening
Permission
Manage Server, only for server templates
If it is missing
Templates say they could not be checked

Roles

roles
  • Total roles against Discord's 250 limit, and whether EvaluBot's role is at the top
  • Roles with Administrator, marked as on or off the owner's approved list, and roles that can mention @everyone
  • Risky permissions Discord turns on for @everyone by default
  • 23 sensitive permissions mapped to the roles that hold them, with human and bot member counts and who last changed each privileged role
  • Roles whose members can give themselves a more powerful role because of the role order
  • Roles members get without anyone handing them out (Server Booster, server subscription, Linked Roles, Twitch or YouTube) and whether they carry staff permissions
  • The full role list with colors, roles with fewer than 3 human members, and bot-only roles
Permission
Manage Server to tell bots from people, and View Audit Log for "Last changed by"
If it is missing
Without Manage Server, bots count as humans and bot-only roles are not listed. Without View Audit Log, the "Last changed by" column says so

Channels

channels
  • Every channel grouped by category, with its type, description and last activity
  • Whether each channel is synced with its category, listing the roles and members with overrides, including members who left
  • Channels not synced with their category, and exactly what differs for each role or person
  • The thread vulnerability check
  • Channels where an override for @everyone lets every member manage the channel, create webhooks, ping everyone or act as a moderator
  • Channels everyone can see inside a category @everyone cannot see
  • Who can see each private channel: the roles whose members get in, with member counts, and people with their own access
  • Members whose own override gives them control of a channel
  • Channels with no messages in 90+ days
Permission
View Channels
If it is missing
Channels EvaluBot cannot see are left out, and the report says so

AutoMod

automod
  • Which kinds of abuse a rule covers: suspected spam, mention spam, commonly flagged words, member profile names and custom words
  • Every rule: what it catches (never the word lists themselves), whether it is on, what it does and where its alerts go
  • How many roles and channels each rule exempts
Permission
Manage Server
If it is missing
The section says it could not be read

Onboarding

onboarding
  • Whether onboarding is on, and its default channels
  • Every prompt with its options
  • The roles and channels each option grants
Permission
None
If it is missing
Not applicable

Webhooks

webhooks
  • Every webhook's name and target channel
  • Its type: Incoming, Channel follower or Application
  • Who created it, marking incoming webhooks whose creator is no longer in the server
Permission
Manage Webhooks
If it is missing
The section says it could not be read

Bans

bans
  • Banned users with the recorded reason
  • Up to 400 listed, with how many were read; past 2,500 bans the report says more may exist
Permission
Ban Members, read only and never used to ban
If it is missing
The section says it could not be read

Invites

invites
  • Every active invite's code, channel and creator
  • Uses and max uses, the temporary flag and expiry
  • Never-expiring and high-use links, highlighted
Permission
Manage Server
If it is missing
The section says it could not be read

Integrations

integrations
  • Connected apps and bots, Twitch and YouTube links, and server subscriptions
  • Each one's name, type, account, who added it, and whether it is enabled
  • Every bot: whether Discord has verified it, whether it has Administrator, and the staff permissions it holds through all of its roles
Permission
Manage Server
If it is missing
The section says it could not be read

Recent Activity

activity
  • Administrator, takeover and staff permissions given, bots added and server protections lowered
  • Ownership or the vanity invite changed, risky channel permissions given, webhooks created and AutoMod rules turned off
  • Members banned, kicked or pruned, and channels and roles deleted
  • On Premium, who did each one and when
Permission
View Audit Log
If it is missing
The section says it could not be read

The thread vulnerability check

Part of the Channels section, and one of the checks that costs points. It flags text and announcement channels that @everyone can see but not send messages in, while @everyone can still Create Public Threads, so members get around a read-only channel by posting in a thread.

How to close the loophole

Last activity, without reading messages

A channel's last activity comes from the ID of its latest message, which encodes when it was sent. EvaluBot never reads messages.

"Last changed by" covers about 45 days

It comes from the server's audit log, which Discord keeps for about 45 days, so older changes show as not recorded.

Member counts on servers of any size

Per-role member counts come from Discord's role member counts, on servers of any size. Bots are told apart from people through the server's app list, which Discord caps at 50 apps; past that, the report says some bots count as humans.

Channels hidden from EvaluBot

From 16 November 2026, Discord only shows a bot the channels it can view. The report says how many are hidden and leaves their settings out, without costing points. Giving EvaluBot's role View Channel there brings them back.

Missing permissions never cost points

A section EvaluBot could not read is marked as limited, and the score lists it as not assessed.

The report

PDF to share. HTML to explore. JSON to build on.

A full audit produces one self-contained report: a PDF that opens with one click and keeps every panel open, or an HTML file that opens in any browser, with sections you can collapse and dates in your own time zone. Or ask for JSON and get the raw data behind it.

10-09-2026 03-14-22PM - Starlight Gaming-a1b2c3.html

Starlight Gaming

Discord Server Audit Report

Provided by EvaluBot
Powered by Digital Den
Members
4,812
Created
Mar 14, 2021
Verification
Medium
2FA for mods
On
Media filter
All members
Locale
en-US
Roles
38
Channels
64
Webhooks
6
Bans
112
82/ 100

Security Score

Good

Deductions

  • 2 channels have a thread-permission gap-10
  • @everyone holds 2 elevated permissions-8

Since the last audit

+6 points3 fixed1 to review0 new risks

Recommendations

Critical

  • Default notifications are All Messages on a server with 1,000+ members

General

  • Remove Manage Messages and Mute Members from @everyone
  • Deny Create Public Threads in #announcements and #rules
  • Review risky @everyone defaults: Use External Apps, Create Events

Optional

  • Set up onboarding
  • 4 channels inactive for 90+ days

Recommendations are advisory and do not affect the score.

A full report, in order

  1. 1Header: server name, an overview grid of key settings, and counts of boosts, emoji, stickers, soundboard sounds, roles, channels, webhooks and bans
  2. 2A table of contents
  3. 3Security Score: a ring gauge with the score and grade, and every deduction
  4. 4Since the last audit
  5. 5Recent Activity, the last 45 days of risky actions
  6. 6Server Settings, with Safety Signals and Who Can Find and Join, then AutoMod, Webhooks, Bans, Invites, and Integrations with every bot
  7. 7Recommendations
  8. 8Roles Analysis, Onboarding
  9. 9Channels and Categories, the Thread Vulnerability Check, Channels Where Everyone Has Risky Powers, Public Channels in Private Categories, Channels Not Synced With Their Category, Who Can See Private Channels, Members With Control of a Channel, and Inactive Channels (90+ days)
  10. 10Footer with the Privacy Policy and Terms of Service

Partial audits

A compact report with the header, Security Score, Since the last audit, and the sections you chose.

JSON

Generation time, server ID, sections, the score with its full breakdown, the bot's permissions, every collected section, and on Premium the changes since the last audit with the score history, and who did each recent risky action. Like every report, it holds only what Discord shows its reader.

How it reaches you

  • The Audit complete message gives the score and its grade, the three deductions that cost the most with the step that clears each one, and the next step: turning on alerts if they are off, otherwise fixing what it found and running the audit again.
  • The report arrives in a private reply only you can see, and a copy goes to your DMs, because Discord removes private replies when the app reloads. If your DMs are closed, the reply tells you to download it straight away.
  • A PDF report opens with one click in any PDF viewer. HTML reports come with step-by-step download instructions and a screenshot of where Discord's Download button is, since Discord's preview shows the raw file.
  • If a PDF cannot be made, you get the HTML report instead, with a note saying so.
  • If a queued audit runs past Discord's roughly 15-minute reply window, the DM is the delivery.
  • Reports over 25 MB, Discord's upload limit, are sent as a .zip, roughly ten times smaller. If even the zip is too big, you are told to run fewer sections.
  • An audit counts against the allowance only once the report reaches you. A failed audit, an oversized report, a full queue or a brief database outage never uses one.

The file name

Every report is named for when it ran and the server it covers, ending in .pdf, .html or .json.

MM-DD-YYYY hh-mm-ssAM - Server Name-a1b2c3.pdf

No report carries ads or partner offers. Free reports point to Premium where it would show more.

How to open your report

Milestones

A server earns them from its full audits: First full audit, Scored 90 or more, and 30 days with no critical findings. The Audit complete message says when one is new, and /auditplan and the score card list them. A partial audit earns nothing.

Score card and public score

/auditcard show makes a picture of the score: the grade ring, the server's name and icon, the date of its last full audit and its milestones, and nothing about how the server is set up. It stays private unless you share it. /auditcard badge posts a public message that updates itself after each full audit. Nothing is public unless an admin posts it.

Your own look

Premium

/auditstyle report gives PDF and HTML reports a light or dark theme, your accent color and your icon in the header. /auditstyle bot changes EvaluBot's nickname, picture, banner and bio in your server only, and each change is posted in the alert channel.

Since the last audit

Every audit remembers the last one.

After each delivered audit, EvaluBot keeps a snapshot of the server's security-relevant settings, so the next audit can say exactly what changed. The snapshot holds no member or user IDs.

Every server

  • The score change since the last full audit. Partial audits score only some sections, so their score is not compared.
  • How many settings changed, split into new risks, items to review, fixes and other changes, in the report and the Audit complete message.

Premium

  • Every change, up to 200, labeledNew riskReviewFixedChanged
  • The scores of the last six full audits, leading up to this one.
  • On a server's first audit, a note that the next one will list every change.

What is compared

Server
2FA for moderators on or off; verification level and media filter raised or lowered; default notifications; Community on or off; vanity invite; widget; Server Discovery; server templates; on Community servers, Activity Alerts and Rules Screening
Roles
A role gaining or losing Administrator or a sensitive permission; @everyone gaining or losing takeover, elevated or risky default permissions, or the ability to mention @everyone; deleted roles; role count
Channels
@everyone allowed a risky permission in a channel, or no longer allowed it; thread-permission gaps opened or fixed; deleted channels; channel count
AutoMod
Rules turned on or off, new rules and deleted rules
Webhooks and integrations
New and removed ones
Invites
Never-expiring invite count and active invite count
Bans
Ban count, skipped when a ban list was too long to read in full
Onboarding
Turned on or off, or the number of onboarding questions while it stays on

A section is compared only when both audits read it. A section EvaluBot could not read is skipped, never reported as everything removed, and channels hidden from EvaluBot are never reported as deleted.

Schedule and repeat

Audits on your schedule.

Run an audit later, said the way you would say it, in any time zone, and have Premium post one to your staff every week or month.

One-time scheduled audits

/auditschedule oncewhentomorrow 9amtimezoneEurope/London
  • Say when the way you would: tomorrow 9am, friday 5:30 pm, in 2 hours or 9pm. A day with no time means 9am, and a bare hour such as tomorrow 9 is refused rather than guessed. Dates like 2026-07-25 15:30 or 07/25/2026 3:30 PM work too, and one whose day and month could be read either way, such as 07/10/2026, must be written year first. It must be at least 1 minute and at most 365 days ahead.
  • The time zone autocompletes as you type a city or region, such as Eastern, London or Tokyo, and accepts any IANA zone. EvaluBot remembers the last one you picked; until you pick one, it is UTC.
  • The report arrives by DM. You get a confirmation DM straight away, and scheduling is refused, with instructions, if EvaluBot cannot DM you.
  • A pending audit holds a slot in the month it runs in, so scheduling cannot get around the monthly limit. Each person can have up to 10 pending.
  • /auditschedule list shows every pending audit in the server, and any admin can cancel one with /auditschedule cancel, picked from a list. The person who scheduled it is told by DM.
  • If a scheduled audit fails, you are told by DM and nothing is counted.

Recurring audits

Premium
/auditschedule recurringchannel#staff-reportsfrequencyWeeklywhenmonday 9am
  • Up to 3 per server, with optional format (PDF by default) and sections (all by default).
  • The first report arrives at the time you give, or a week or a month from now, so setting one up does not spend an audit straight away. After that it runs at the same clock time in its time zone, across daylight saving changes. Monthly runs keep the same day, or the last day in shorter months.
  • /auditschedule edit changes any of it in place. A new time sets the next run and, from it, the day and time of every run after.
  • The channel must be staff-only, because reports list roles, bans, invites and webhooks. One that @everyone or a role anyone can get can read is refused, and so is one a role without staff permissions can read, such as a Verified role, unless allow_roles says those roles are meant to read the reports. EvaluBot needs View Channel, Send Messages, Embed Links and Attach Files there, and checks all of this at setup and before every run.
  • Each report shows what the person who set it up can see, and says so when that leaves something out.
  • Each run counts toward the server's monthly allowance. When the month's audits are used up, the run is skipped with a notice in the channel.
  • A failed run is not counted and is tried again an hour later, up to 3 tries. When the server has to fix something, the channel and the owner are told on the first try, and the third pauses it until someone fixes it and runs /auditschedule resume. A run cut off by a restart is tried again a minute after EvaluBot is back.
  • If Premium ends, recurring audits go on hold and resume on their own when it returns. Runs missed while the bot was offline are skipped, not run back to back. Stop one with /auditschedule cancel.

Audit history

/audithistoryscopeThis servercsvTrue

Your recent audits with score, format, sections, the server's name and the time in your own time zone, 1 to 25 at a time. Premium adds every audit run in the server and who ran it, a chart of the server's score over its last 12 full audits, which recurring reports show too, and a CSV of up to 1,000 rows with the columns date_utc, guild_id, run_by, sections, format, score and issues_found.

Every option for every command is on the commands page.

FAQ

Questions about the audit

Can I audit only some sections of my server?

Yes. Pass a comma-separated list to the sections option, using the keys server, roles, channels, automod, onboarding, webhooks, bans, invites, integrations and activity. A partial audit is scored on just its sections.

What happens if EvaluBot is missing a permission?

Only the matching section is limited, and the report says so. AutoMod, Webhooks, Bans, Invites, Integrations and Recent Activity say they could not be read, and channels EvaluBot cannot see are left out. A section it could not read is marked not assessed and never costs points.

Does a failed audit use up my monthly audit?

No. An audit counts only once the report reaches you. A failed audit, an oversized report, a full queue or a brief database outage never uses one.

How does EvaluBot know when a channel was last active?

From the ID of the channel's latest message, which encodes when it was sent. EvaluBot never reads the message itself.

Why does my report look like code in Discord?

That is the HTML format: Discord's file preview shows the raw HTML. Download the file and open it in your browser to see the styled report, or run the audit as a PDF, which opens with one click. EvaluBot sends step-by-step download instructions with every HTML report.

Can I share my server's score?

Yes, on every plan. /auditcard show makes a picture of the score with the grade, the date of the last full audit and the server's milestones, and nothing about how the server is set up. It stays private unless you share it. /auditcard badge posts a public message that updates itself after each full audit.

Does EvaluBot work on very large servers?

Yes. Per-role member counts come from Discord's role member counts on servers of any size, and reports over Discord's 25 MB upload limit are sent as a zip.

Run your first audit today.

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