An alt is an additional Discord account. People use them to separate communities or test a bot, as well as to evade bans or repeat abuse. Your moderation policy should distinguish having a second account from breaking server rules. RestoreCord's Discord alt checker helps server owners review possible linked accounts during verification.
Start with evidence you can review
Record the behavior that prompted the check: repeated spam, the same targeted harassment, or an account returning immediately after a ban. Review messages and moderation history available to your team. A recent creation date, similar name, or shared avatar is a clue, not an identity check.
- Keep the reason for the investigation and relevant message links in a private moderation channel.
- Check whether the account actually broke a rule before acting on resemblance alone.
- Ask for context when a match could come from a shared household, school, or device.
- Do not ask members for passwords, login tokens, or access to unrelated accounts.
Understand what verification checks can tell you
IP address matches
RestoreCord compares a verifying member's IP address with previous verifications in the same server. A different account using the same address can trigger a match. Roommates, school networks, public Wi-Fi, and mobile carriers can put different people behind one public IP, so automatic bans can catch legitimate members.
Browser fingerprint matches
Browser characteristics produce a visitor identifier that can match another verified account in that server. This adds a signal when the network address changes. It is not a permanent hardware ID: different browsers, devices, or privacy protections can change the result, and shared devices can produce matches between different people.
VPN status and account age
VPN and proxy checks and a minimum account-age setting are separate access controls. A VPN user is not necessarily an alt, and an old account is not necessarily safe. Choose restrictions based on abuse your server has experienced and check their availability on your plan.
Set up alt checks in RestoreCord
- Connect your bot and server. Follow the server setup guide. Alt detection is included on Premium, Business, and Enterprise; core verification is available on Free.
- Publish verification. Use the verify-message guide and check channel visibility with the permissions guide. Publishing a message alone does not configure protected channel permissions.
- Start with warnings. Configure webhook logs and leave alt blocking and automatic bans disabled while you review matches.
- Test the member experience. Verify with a spare account from a previously used connection. Check the alert and the matched accounts, then test how a legitimate member can contact moderators if blocked.
- Choose your response. Keep warnings for manual review, enable blocking to deny verification, or enable auto-ban if your policy requires it. Review existing firewall rules, because another access rule can reject a member before the warning stage.
Work through a match before banning
Suppose a member verifies and the alert lists an existing account from the same IP. The two could be siblings on home Wi-Fi. Compare the moderation history and ask about the shared connection privately. If there is no abuse, a permanent ban based only on the match may be the wrong outcome. If the accounts repeat documented harassment, record that evidence with the action you take.
Explain your verification process and provide an appeal route. Account records and technical identifiers can be personal data; a hashed fingerprint does not make linked member records anonymous. Read the privacy policy and direct members to Manage My Data for their data controls.
Choose a checker that fits your moderation workflow
Check when the tool runs, which records it compares, what happens on a match, and how a moderator handles mistakes. For RestoreCord's current scope and plans, see alt detection during Discord verification. For product differences, read RestoreCord vs Double Counter. A comparison of published features cannot establish which tool detects more alts without a shared test dataset.