Discord alt accounts: how to detect and stop them

An alt account (short for “alternate account”) is an additional Discord account created by someone who already has one. The first account is usually called the main.

Having more than one account is not against Discord's rules. Discord even ships an account switcher so you can move between several accounts in the same app. People keep alts for ordinary reasons: separating work from gaming, testing a bot or a server's permissions, or keeping a private account for friends.

What is against the rules is what some alts are used for. Discord's Community Guidelines explicitly prohibit ban and block evasion, and coordinating server joins to harass a community. The account is fine; the behaviour is the problem.

Every moderation action on Discord targets an account: a timeout, a kick, a ban, a role removed. If creating a new account costs nothing, none of those actions lasts. These are the cases server staff report to us most often:

• Ban evasion. A banned member comes back on a fresh account, often within minutes. See how Discord bans work and why they are easy to evade.
• Giveaway and reward abuse. One person enters ten times with ten accounts, or farms invite rewards by inviting their own alts.
• Vote and poll manipulation. Community decisions, staff elections and contests can be swung by a handful of people.
• Harassment and sock puppets. Several accounts pile on one member, or pretend to be independent voices agreeing with each other.
• Dodging mutes and timeouts. The main is muted, so the conversation simply continues from the alt.
• Raid preparation. Accounts are parked in a server days ahead and activated together. Our raid protection guide covers that pattern.

Notice that only the first case involves a ban. A member who quietly runs three accounts has never been punished, so no ban list will ever help you find them.

Moderators develop a nose for alts. The usual hints are real, and worth teaching to a new staff member:

• Account age. The account was created hours or days ago. Discord shows the creation date on the profile, and the Members page in Server Settings lets you sort by join date and account age.
• Timing. It joined shortly after a ban, a mute or a heated argument.
• Empty profile. Default avatar, no bio, no connected accounts, no mutual servers.
• Familiar behaviour. The same writing style, the same typos, the same targets, the same hours of activity as a member you removed.
• Too much knowledge. A “new” member who already knows your channels, your inside jokes and your staff by name.

The limit of this method is that every hint is circumstantial. Plenty of real people create an account the day they are invited to their first server, and anyone evading on purpose will age an account, set an avatar and wait a week. Manual checks also do not scale: a server that gains two hundred members a day cannot interview each one.

Discord gives you three native defences. Each one helps, and each has a gap.

None of these answers the question that matters: is this new account run by someone I already know? Discord does not tell server owners or bots which accounts belong to the same person, and its API never exposes a member's IP address or device. A regular moderation bot sees a username, an avatar and a creation date, the same things you see.

Because Discord shares no identifying signal, an alt checker (also called an alt detector or alt finder) has to collect its own, and the only honest way to do that is a verification step. New members open a link before they get access, and that visit provides what the Discord API does not:

• Network signals: the IP address and whether it belongs to a VPN, a proxy, Tor or a datacenter.
• Device and browser signals: characteristics that stay stable when someone only changes account.
• Behaviour signals: how and when verifications happen, across the server and across the network.

Those signals are compared with the accounts that verified before. If the new account matches an existing one, it is flagged as an alt, on your server or on any server sharing the same detection network. Double Counter combines more than 20 risk factors this way and catches about 98 % of alt accounts on arrival, in roughly 3 seconds and without a Discord login or a captcha.

1. Put a gate in front of your channels. New members should see one verification channel and nothing else until they hold a “verified” role. Our verification setup guide walks through the permissions.
2. Add an alt checker to that gate. With Double Counter you choose the verification channel, the verified role and a staff-only log channel in the dashboard, and every join is screened from then on.
3. Decide what happens to a detected alt. Auto-ban is the strictest option. A quarantine role or a staff alert is gentler and lets a moderator look first. Start with alerts if you are unsure, then tighten.
4. Set a minimum account age. Holding accounts that are a few days old removes most throwaways, including the ones nobody has seen before.
5. Block VPNs at verification. Hiding the network is the first thing an evader tries. See whether your server should block VPNs.
6. Write the rule down. State in your rules whether alts are allowed and how to declare one. People who read “one account per person, ask staff for exceptions” rarely argue when an undeclared alt is removed.

One caveat applies to every tool of this kind: members who joined before you added verification were never screened. Protection starts with the next join, which is a good reason to set it up before you need it.

Not every match is an evader. Two siblings on the same computer, housemates behind the same connection, or a moderator testing permissions with a second account will look related, because they are.

Good practice is to treat a detection as evidence, not as a verdict. Every Double Counter flag is logged with its reasoning, and staff can approve a known second account with /manverify, which only applies to your server. The docs explain how alt detections are decided.

One habit prevents most accidental links: tell your members that a verification link is personal. Opening a link meant for someone else ties the two accounts together.