Raid Protection
Raid protection watches how fast members join your server and raises the alarm the moment a raid starts, including which invite the raid came through. Detection and alerts are free for every server; automatic responses and cleanup tools are part of Premium.
Raid protection is disabled by default: turn on Enabled on the dashboard's Raid Protection page and pick an Alert channel to get started. An alert channel is required while raid protection is enabled.
Raid Detection
The alarm trips when members join faster than your Joins per minute setting and enough of those joins come from young accounts (your Young account ratio). Requiring both keeps false alarms away: a partnered event or a viral video brings in lots of established accounts, while a bot raid brings in a wave of brand new ones.
It also trips right away when 5 young accounts join within 10 seconds, whatever your Joins per minute: that burst is the usual signature of a bot raid.
Once tripped, the raid response stays active for your Response duration and extends itself while the join surge continues.
The Raid detection section has these settings:
- Enabled: detect join surges and send raid alerts.
- Alert channel: where raid alerts and incident summaries are sent, with one-click response buttons.
- Joins per minute: trip the alarm when this many members join within one minute (3 to 100, 10 by default).
- Young account age (days): accounts younger than this many days count as suspicious (1 to 90, 7 by default).
- Young account ratio (%): only trip when at least this share of the joins comes from young accounts (0 to 100, 60 by default).
- Response duration (minutes): how long the raid response stays active once tripped (5 to 120, 10 by default).

INFO
Free servers use the default detection settings: 10 joins per minute, at least 60% of them from accounts younger than 7 days, and a 10-minute response. Changing them requires Invite Tracker Premium.
Raid Alerts
When a raid trips, Invite Tracker sends an alert to your Alert channel with the full picture: how many members joined within the last minute, how many of them are young accounts, and the suspicious invites they used, with the invite code, its creator and the join count per invite.
Every alert comes with one-click response buttons:
- Pause invites: pauses all server invites through Discord's own safety tools (free for everyone). The pause lifts on its own after your Invite pause duration, 1 hour by default.
- Raise verification: new joiners must pass verification while the response is active (needs your verification panel set up).
- Kick young joiners: kicks the young accounts that joined during the raid, and keeps kicking young accounts that join while the response is active.
- Ban raid cohort: bans every member who joined during the incident, young or not. The confirmation shows exactly how many young and older accounts are included; press the button again within 60 seconds to confirm.
- False alarm: lifts the response, restores paused invites and records the incident as a false alarm.
When the response ends, a summary is posted with the final numbers and a last chance to ban the captured members, or to use /massban with one of the flagged invite codes for a more targeted cleanup.
WARNING
The response buttons require the Manage Server permission. Kick young joiners also requires Kick Members and Ban raid cohort also requires Ban Members, just like doing it by hand. All buttons except Pause invites and False alarm require Invite Tracker Premium.
Invite Tracker itself needs the Kick Members, Ban Members and Manage Server permissions (with a role above the raiders) for the kick, ban and invite pause actions to work.
Members out of Invite Tracker's reach (the server owner and anyone whose top role is at or above the bot's) are skipped, and the reply tells you how many. Pressing Kick young joiners or Ban raid cohort again only acts on members who haven't been removed yet. If Discord refuses a kick or ban, that button rests for a minute before it can be used again.
Automatic Response
Premium feature
The automatic raid response requires Invite Tracker Premium.
With Respond automatically enabled, the actions you pick are applied within seconds of a raid tripping, no admin needed. Alerts with the manual response buttons are always sent either way.
- Pause invites: pauses all server invites through Discord's own safety tools. They restore themselves after the Invite pause duration (minutes) (10 to 1440, so up to 24 hours).
- Force verification: new joiners must pass verification (captcha at minimum) while the response is active. Your saved verification settings are untouched and apply again as soon as the response ends.
- Kick young accounts: accounts younger than your Young account age are kicked while the response is active. They can rejoin once it ends.
- Pause invite crediting: joins during a raid don't count towards invite counts or leaderboards, so raiders can't inflate them.

TIP
Force verification needs a working verification setup: configure it on the Verification page and send a verification panel first. Until then, the dashboard shows a notice under the setting, and during a raid this action is skipped and the alert tells you so.
Manual Lockdown
Premium feature
Manual lockdowns (/lockdown start and /lockdown end) require Invite Tracker Premium.
The /lockdown start command activates the raid response on demand, which is useful before an announced event or the moment you spot trouble yourself. It pauses invites and invite crediting for the chosen duration (5 to 120 minutes, defaulting to your Response duration) and also applies Force verification and Kick young accounts if you turned them on. /lockdown end lifts it early and restores paused invites.
Both commands require the Administrator permission. Starting a lockdown enables raid protection for your server if it wasn't enabled yet.
While a response is active (raid or lockdown), a live banner shows up at the top of the dashboard's Raid Protection page with when it started and when it lifts automatically. Press End response to end it from there.

Incident History
Every raid and lockdown is listed in the Incident history section with its status (Active, Resolved or False alarm), when it started and how long it lasted, its join counts, the top invites used and the response actions taken. An active incident shows up with live counters.

INFO
Free servers keep 3 days of incident history. Premium servers keep it forever. The page shows the 20 most recent incidents.
