DEFENSIVE SERVER PROTECTION

Keep your community
one step ahead.

A practical Discord moderation and security-monitoring bot. Catch suspicious patterns, give moderators useful context, and keep server owners in control.

No web dashboard or account login. Configure the bot from Discord slash commands.

WEBSITE STATUS Checking... Checking website service
Review alerts before action
MONITORING SERVER OWNERS IN CONTROL
50standalone slash commands
8configurable protection modules
0automatic anti-nuke punishments
Youchoose which protections to enable
WHAT IT DOES

Useful signals.
Human decisions.

Layered monitoring and everyday moderation tools, designed to give your team context instead of pretending detection is perfect.

Watch join patterns

Join-rate alerts and new-account age signals help moderators spot unusual bursts. They are indicators for review, not proof of malicious intent.

Review admin activity

Audit-log monitoring records potentially risky server actions and notes trusted actors when known. The bot does not automatically punish administrators.

Configure message filters

Optional spam, unapproved-link, caps, and mention filters can remove matching messages. Scam matches are alerts only and are never auto-deleted.

Moderate with guardrails

Warnings, timeouts, kicks, bans, and quarantine roles use Discord permissions and role-hierarchy checks. Discord must confirm an action before it is reported complete.

Keep a server audit trail

SQLite stores supported bot settings, moderator warnings, and timestamped security events. Set a private log channel and keep backups somewhere safe.

Make decisions in Discord

Every setting and moderation action is handled through permission-gated slash commands. There is no separate web dashboard, OAuth login, or hidden owner account.

GETTING STARTED

Up and running
in a few steps.

The bot starts conservatively. Choose what to enable and test filters in a private channel before relying on them.

  1. 01

    Invite the bot

    Add it to your server with only the permissions you plan to use. Enable Server Members and Message Content intents in the Discord Developer Portal for join and message monitoring.

  2. 02

    Choose a private log channel

    Use /setup to select a channel the bot can view and send alerts in. Start with /security-scan to review its permissions.

  3. 03

    Enable and tune protections

    Run /protect-enable, review /protect-status, then configure thresholds, link allowlists, and the modules that fit your community.

  4. 04

    Review, test, and back up

    Test in a private channel. Check the security logs, keep SQLite backups, and have moderators verify uncertain signals before acting.

COMMAND DIRECTORY

Find the right
slash command.

Search all 50 commands. Administration and moderation actions require the corresponding Discord permissions.

Loading commands...

BUILT WITH BOUNDARIES

Protection should
stay accountable.

Anti-nuke is monitoring, not retaliation. Audit events can arrive late or lack context. The bot logs risky actions for human review; it does not strip roles, ban administrators, or reverse server changes automatically.

Heuristics can be wrong. Join-age, raid, scam, and spam signals can have false positives. Configure thresholds for your server and review alerts in context.

Moderation stays permissioned. Discord permissions and role hierarchy apply. The bot does not grant itself permissions, collect credentials, or offer a hidden control panel.

No bot can guarantee perfect detection or uninterrupted uptime. Keep Discord permissions, hosting, and backups under administrator control.

PROTECT. DETECT. DEFEND. RECOVER.

Build a calmer,
safer server.

Give your moderators clear signals and a practical toolkit, without handing automated systems unchecked power.