Discord Gatekeeping and Perimeter Security Bots
Compare RestoreCord, Double Counter, AltDentifier, PeakBot, and Wick for VPN filtering, alt detection, verification, and perimeter security.
On this page
Most moderation bots wait for someone to cause trouble. A perimeter bot checks people at the door, before they can see the server or post anything.
The check happens in a different place. Dyno and Discord AutoMod work inside Discord, where they inspect messages and react to spam. RestoreCord and Double Counter send new members to a web page instead. Since the member connects to that page directly, it can see network and browser details that Discord keeps hidden from bots.
That gives web verification more information to work with. It is also more intrusive. Members must leave Discord and trust another service before they can enter, and some gates ask for OAuth permissions too.
The main options
| Service | Best for | How it checks users | Main drawback |
|---|---|---|---|
| RestoreCord | Custom entry rules and member recovery | Web verification with network rules, device checks, and OAuth authorization | More setup, more data collection, and extra friction for every member |
| Double Counter | Fast alt and VPN blocking | Web-based device and connection checks across its verification network | Limited custom policy controls and recurring privacy concerns |
| AltDentifier | Identity checks through established accounts | Reviews a Discord profile and can ask users to connect outside accounts | Many users will not link Steam, Reddit, or another personal account just to enter |
| PeakBot | Verification mixed with daily moderation | Configurable entry checks alongside tickets, logs, and AutoMod | Broader feature set can make the setup harder to follow |
| Wick | In-server raid and admin protection | Uses Discord account details, join patterns, and server activity | Cannot inspect IP addresses or browser data |
What a web firewall can see
Discord does not give bots a member's IP address, browser details, or internet provider. A verification website sees more because the member connects to it directly.
RestoreCord turns that information into entry rules. An owner can block VPNs or proxies, restrict a country or network provider, and check browser details for signs that several accounts came from the same device. Rules can also use Discord account information collected during authorization.
This works best when you know what you are trying to stop. If a raid comes from disposable accounts on one hosting provider, blocking that provider makes more sense than rejecting every new Discord account. Innocent users can still get caught, particularly on mobile or workplace networks.
Device fingerprinting is useful, but messy. A match may connect several Discord accounts to one browser or computer. It can also catch siblings sharing a laptop or someone whose browser settings changed. A match deserves a look. It is not proof that someone is malicious.
RestoreCord
RestoreCord gives you the most control of the services here. Instead of one broad risk switch, it lets you write rules for IP ranges, ASNs, countries, connection types, and user agents. Account details can go into those rules too, and events can be sent to logs or webhooks.
Its bypass password is handy on a tightly locked server. If a VPN or location rule catches a moderator, the password can let them through without weakening the rule for everyone else. A private community can use it as a final lock on the gate. Keep it out of ordinary staff channels and change it when someone leaves the team.
RestoreCord also handles backups and member recovery, which the dedicated gatekeeping services do not. Using one verification flow for entry and recovery is convenient. It also means trusting one service with more data. Read its retention policy and OAuth scopes before asking the whole server to sign up.
Double Counter
Double Counter is simpler if alternate accounts are the main problem. A member opens its verification page, and the service checks connection and device signals for links to other accounts. Because it operates across many participating servers, it may recognize a device seen elsewhere.
The setup is closer to an on-or-off layer than RestoreCord's detailed firewall. You can get it running quickly, but there is less room for custom network rules, exceptions, or a private password route. The free verification page may show ads as well.
Cross-server detection deserves scrutiny. Check what Double Counter collects, how long it keeps identifiers, and whether a user can appeal a false match. Nobody should be stuck with an unexplained block based on activity in another server.
AltDentifier
AltDentifier looks at identity rather than leaning mainly on IP and device matches. It can assess the Discord account and ask a member to connect an established account from another platform. A Steam or Reddit account with real history is harder for a disposable raid account to fake quickly.
Of course, that means asking members to tie more of their online identity to Discord. Some will be fine with it. Others will leave, especially in communities where people prefer to stay pseudonymous. Offer manual review, and do not treat a missing social profile as proof of bad intent.
PeakBot, Wick, and native checks
PeakBot sits somewhere between a verification service and a general moderation bot. It handles entry checks, then sticks around for tickets, logs, and chat moderation. That is convenient for a small staff team. It also gives moderators more settings to untangle when two rules overlap.
Wick stays inside Discord. It watches account age, join patterns, role changes, and destructive administrator activity without sending every member to a browser. It cannot see a VPN or browser fingerprint. It can still react when a raid starts or a stolen admin account begins deleting channels.
Discord's own verification levels and AutoMod are enough for many servers. They barely affect onboarding and do not put another company between you and your members. For a small private group that has never been targeted, I would start there.
Web verification versus native defense
| Security question | Web gate such as RestoreCord | Native bot such as Wick |
|---|---|---|
| Can it inspect IP or network data? | Yes | No |
| Can it look for browser or device matches? | Yes | No |
| Can it stop a user before server access? | Yes | Limited to Discord's available gates and roles |
| Can it watch messages and admin actions? | Only if it also has in-server features | Yes |
| Does the member leave Discord to verify? | Yes | Usually no |
| Main concern | Privacy, false matches, and onboarding drop-off | Less information about alts and network origin |
Which approach should you use?
RestoreCord makes sense for a high-risk public project that needs precise entry rules and member recovery in the same system. Someone on staff must be willing to maintain those rules and review blocks. Otherwise all that control just turns into a pile of settings nobody understands.
Double Counter is the quicker choice when alt detection is the main problem. AltDentifier fits communities where an established outside account is a reasonable trust signal. PeakBot is for a small team that would rather manage entry checks and daily moderation in one place.
Wick and Discord's native tools ask less of new members. That matters. A server that has never faced a targeted raid probably does not need to inspect every visitor's connection.
Test the full join process on a phone and a desktop. Give blocked users somewhere to appeal, review false positives, and tell members what the service collects. If legitimate people cannot get through the gate, the settings are too strict.