Verification gate
New members land in one verify channel and sign in with Discord before they get a role. Raid accounts never see your other channels, so there is nothing for them to spam.
Chat moderation deals with people who are already inside. VaultCord moderates the door: raid accounts, alts, VPN ban evaders and known scammers are blocked at verification, and if the worst happens, /denuke unnukes your server from the audit log, even without a backup.
The first job is keeping chat healthy: warnings, timeouts and filters. Discord's built-in AutoMod and classic moderation bots are good at that.
The second job is keeping the wrong people out and recovering when something breaks. A raid of 50 new accounts, a ban evader on a VPN or a compromised admin deleting every channel are not chat problems. They need a bot that checks members before they join and keeps a copy of your server.
That second job is what VaultCord does. It runs alongside whatever you already use for chat, so you do not have to replace anything.
| Job | Typical chat moderation bot | VaultCord |
|---|---|---|
| Warn, mute and timeout commands | ✓ | – |
| Chat filters and auto-mod rules | ✓ | – |
| Stops raid accounts before they reach your channels | ◐ | ✓ |
| Captcha, VPN and alt detection | – | ✓ |
| Blacklist by IP, fingerprint, country or ISP | – | ✓ |
| Blocks known scammers | – | ✓ |
| Denukes a server from the audit log, no backup needed | – | ✓ |
| Rebuilds channels and roles from a backup after a nuke | – | ✓ |
| Adds members back after a ban or deletion | – | ✓ |
Each check is one toggle in the dashboard. Members who fail see why, and your staff see the reason in the log channel. The full details are on the Discord verification bot page.
New members land in one verify channel and sign in with Discord before they get a role. Raid accounts never see your other channels, so there is nothing for them to spam.
Cloudflare Turnstile or hCaptcha on the verify page. Even with captcha off, requests that look automated are given one, which is what stops scripted raids.
Banned members usually come back through a VPN. VaultCord can refuse VPNs, proxies and cellular networks, so an IP ban actually sticks.
Accounts that verify from the same network as an existing member are flagged as likely alts. You choose whether to log them, withhold the role or ban them automatically.
Every member is checked against more than 13,400 confirmed scammers reported to ScammerAlert. Matches cannot verify, which matters most in trading and marketplace servers.
Raid accounts are days old. Set a minimum account age in days and anything newer is turned away, with the exact age written to your logs.
VaultCordAPPToday at 3:12 PMStaff do not need the dashboard for everyday work. These are VaultCord's commands and what each one does. Replies are private, so other members never see moderation happening.
| Command | What it does |
|---|---|
/blacklist | Blacklist a member and their metadata (IP address and browser fingerprint), so a new account on the same device is stopped too. |
/unblacklist | Remove a member from the blacklist. |
/whitelist | Allow a member and their metadata, useful when a trusted member is caught by a VPN or alt rule. |
/info | Get the details VaultCord has on a verified member. |
/deluser | Delete a member from your backups, for example an old alt account. |
/delunauthed | Delete every member who unlinked VaultCord, so your counts stay accurate. |
/usercount | Check how many verified members you can pull. |
/pull | Start pulling verified members back into the server. |
/denuke | Unnuke the server: reverse deleted channels, deleted roles, removed roles and unbans from the last 45 days of the audit log. No backup needed. |
/backup | Back up the server: channels, roles and settings. |
/restore | Restore a backup to the server. This deletes the current channels first, so use it on a nuked or new server. |
A Discord ban only covers one account. VaultCord's firewall checks every verification against your blocklist and allowlist, so a banned member cannot come back on a new account, a new network or a friend's invite.
| Rule type | Use it to |
|---|---|
| Discord user ID | Block one account, or allow it past your other rules |
| Discord server ID | Block anyone who is a member of a server you name, such as a known raid server |
| IP address | Block a connection, even after the member makes a new account |
| Browser fingerprint | Block a device across accounts and networks |
| Country or region | Limit a server to the places your community is from |
| Internet provider (ASN) | Block a hosting provider or network that raids come from |
| Email domain (allowlist) | Only accept members whose verified Discord email ends in your domain |
The firewall is included with Premium and Plus. Known scammer blocking is free.
A nuke is when someone with too many permissions deletes channels, roles or bans members in bulk. No bot can fully stop an account that already has Administrator, so the real protection is being able to undo it.
VaultCordAPPToday at 9:41 PMMost anti-nuke bots can only help if they were in your server and had a backup before the attack. VaultCord's /denuke works after the fact. Discord records every deleted channel, deleted role, role change and unban in the audit log for 45 days, and /denuke reads that log and reverses each change.
That means you can add VaultCord to a server that was nuked an hour ago, run one command and get your channels, roles and bans back. Nothing the nuke did not touch is deleted, so it is safe to run on a server you are still using.
| What the nuke did | What /denuke does |
|---|---|
| Deleted text and voice channels | Recreated with the same name. Channels that still exist are skipped. |
| Deleted roles | Recreated with the same name. Set their permissions and colour again afterwards. |
| Roles taken off members | Given back to each member who is still in the server. |
| Members who were unbanned | Banned again, so the people you removed cannot rejoin. |
| Server name changes | Changed back to the old name. |
| Messages | Not restored. Discord does not keep deleted messages in the audit log. |
| Deleted events | Listed, but you need to recreate them with the right time. |
Take Administrator off the account or bot that nuked the server, kick it, and have staff reset their password and 2FA if an account was hacked.
Sign up at dash.vaultcord.com and invite the bot. It does not need to have been in the server before the nuke. Move its role to the top so it can manage channels, roles and bans.
Run /denuke as an administrator (add code: if your VaultCord account has 2FA) and click Continue De-nuke. Channels and roles come back, removed roles are given back and unbanned members are banned again.
Set role permissions and channel categories again, then run /pull to add back verified members who were kicked or banned.
Use /denuke when there is no backup, or when only part of the server was hit and you want to keep everything else. Use /restore when you have a backup and want channels, categories, permissions and messages back exactly as they were. On a badly nuked server you can run /denuke first and /restore afterwards.
| Question | /denuke | /restore |
|---|---|---|
| Needs a backup made before the nuke | No | Yes |
| VaultCord in the server before the nuke | No, add it afterwards | Yes, to take the backup |
| What it reads | Last 45 days of the audit log | Your latest backup |
| Channels and roles | Names come back | Names, categories, permissions and colours |
| Channels that were not deleted | Kept | Deleted, then rebuilt |
| Messages | No | On paid plans |
| Bans | Reverses unbans | On paid plans |
/denuke is free, limited to administrators, asks for your VaultCord 2FA code if you use 2FA, and can run once every 20 minutes per server.
Create a Member role. Let @everyone see only #rules and #verify, and give the Member role access to everything else.
Sign up at dash.vaultcord.com, invite the bot, pick the Member role and drag the bot role above it so it can give the role.
In the Security tab, switch on captcha, scammer blocking and a minimum account age. On Premium, add VPN blocking and alt detection.
Run /verify-embed in #verify, set a log channel for staff, and run /backup so you have a restore point from day one.
Most servers use two kinds. A chat moderation bot (or Discord's built-in AutoMod) handles warnings, mutes and message filters for people already inside. VaultCord handles who gets in and how you recover: verification, captcha, VPN and alt detection, blacklists, backups and member restores. They work side by side.
No. VaultCord focuses on keeping bad actors out and restoring your server, not on punishing chat behavior. Use Discord's built-in timeout and AutoMod, or your existing moderation bot, for that. VaultCord's /blacklist stops someone from verifying again, even on a new account from the same device.
Put your channels behind a verified role, then require new members to verify with captcha, a minimum account age and, on Premium, VPN blocking. Raid accounts fail those checks and never reach your channels. A role that pings staff on blocked events tells you a raid is happening.
Yes, two ways. /denuke unnukes the server from the audit log, even if you never made a backup. If you do have a backup, /restore rebuilds channels, roles and permissions exactly (messages, emojis and bans on paid plans). Either way, a member pull adds your verified members back.
Both mean undoing a nuke: bringing back the channels and roles someone deleted and reversing the bans, unbans and role changes they made. VaultCord's /denuke command does this automatically by reading the last 45 days of your server's audit log.
Remove the account that nuked the server, add VaultCord, run /denuke and click Continue De-nuke. Deleted channels and roles are recreated by name, removed roles are given back and unbanned members are banned again. Then set role permissions again and run /pull to bring members back.
Yes. /denuke does not use a backup, so it works even if VaultCord was added after the nuke. It can only reverse what is still in the audit log, which Discord keeps for 45 days, and it brings back names rather than every permission, so a backup is still the most complete restore.
No. Discord does not keep deleted messages in the audit log, so no denuke bot can bring them back. Message backups are part of VaultCord's paid plans and are restored with /restore.
Yes, /denuke is included on the free plan. It is limited to server administrators, asks for your VaultCord 2FA code if you use 2FA, and can run once every 20 minutes per server.
No bot can fully stop someone who already has Administrator permission. VaultCord makes a nuke reversible instead: /denuke, backups, Server Deletion Alerts by email, and Automatic Pull to bring members back if the server is deleted or raided. Limiting admin permissions is the best prevention.
A blacklist entry can be a Discord user ID, a server ID, an IP address, a browser fingerprint, a country, a region or an internet provider. /blacklist adds a member together with their IP and fingerprint, so a new account on the same device is stopped as well. The firewall is part of Premium and Plus.
The free plan includes verification, captcha, scammer blocking, minimum account age and server backups with a cooldown. VPN and alt detection, the firewall, the log channel, scheduled backups and backups of messages, emojis and bans are paid features.
Yes. Slash commands cover the day-to-day work: /blacklist, /whitelist, /info, /deluser, /pull, /denuke, /backup and /restore. Settings such as which checks are on live in the dashboard.
Start free with verification, captcha, backups and /denuke, then add VPN, alt detection and the firewall when you need them.
Written by the VaultCord team. Last updated .