Last updated: October 12, 2026 · Category: Guide · Editorial review · About the authors
Key Takeaways
- Verification and anti-fake detection solve different problems. Verification decides who gets in. Anti-fake decides who counts once they are already in.
- A server running invite competitions or reward leaderboards should start with anti-fake. It is free and only needs to be switched on and given a threshold.
- A server that has been raided, or runs public invite links at scale, should start with verification. Anti-fake alone does not stop entry, only reward eligibility.
- Most servers running both invite tracking and public growth campaigns eventually want both layers, not one instead of the other.
Server owners researching Discord security tend to run into two different terms in the same search session: verification and anti-fake (or alt-account) detection. Both sound like they solve the same problem. They do not, and picking the wrong one first leaves a real gap open.
This site already covers each mechanism in depth: how verification actually works and how alt-account detection actually works. This post skips the mechanism deep-dive and answers the question those two guides do not: which layer should you set up first, given what your server actually does.
Neither of those guides frames the choice as a decision based on what the reader is actually running. Both explain a mechanism well; neither tells a reader which one to reach for first. That decision, not a third mechanism explainer, is the gap this post closes.
The Core Difference: Timing
Verification is an entry-time gate. A new member cannot see restricted channels until they complete a required step, such as an OAuth sign-in through Discord's own authorization code grant flow (Discord OAuth2 documentation, retrieved 2026-09-03). Anti-fake detection is an attribution-time classification. The member is already in the server; anti-fake decides whether their join counts toward a leaderboard, auto-role milestone, or invite-gated giveaway.
That timing difference is the whole answer to "do I need this instead of that." Verification never asks whether a join should count for rewards. Anti-fake never asks whether a member should be let in at all. Neither one does the other's job, which is why both existing guides on this site describe them as complementary rather than competing.
If You Run Invite Competitions or Reward Leaderboards, Start With Anti-Fake
Account-age anti-fake detection is available on every InviteForge plan. It is off by default: turn it on under Dashboard → Settings → Anti-Fake and set a minimum account age. The InviteForge docs suggest 7 days to start and 7 to 30 days for most servers, and the threshold guide covers the choice. Each join is classified when the member arrives, so turn it on before rewards go live. Once set, it protects the exact thing at risk in a reward system: whether a join represents a real member or a disposable alt farmed for a prize.
This is the lower-effort, higher-immediate-value starting point for any server where invites already unlock something, a role, a rank, a giveaway entry, because the exposure exists the moment rewards go live, not after a raid.
If You've Been Raided or Run Public Invite Links at Scale, Start With Verification
Anti-fake detection does not stop entry. A raid, a bot wave, or a bulk-join attack still gets into the server; anti-fake only prevents those joins from counting toward rewards afterward. If the actual concern is who gets in at all, not just who counts, verification is the layer that addresses it.
OAuth verification's core tier is also free, with no member limit: sign-in through Discord's own login, automatic verified and unverified role assignment, and verification stats. For the tradeoffs between OAuth and CAPTCHA-style verification, see the full verification guide; for setup, see the verification landing page.
Running Both
Verification and anti-fake do not conflict, and most servers running public invite campaigns end up wanting both. The practical order is verification first, since it determines who is in the server's population at all, then anti-fake, which classifies joins within that population for reward purposes. A server that only sets up anti-fake still gets raided at the front door. A server that only sets up verification can still have its leaderboard farmed by alts that pass the sign-in step.
For alts that are old enough to pass an age threshold, both existing guides point to the same next layer: device fingerprinting. It catches aged alts reused across raids that account age alone misses, and it is covered in the alt-account detection guide.
Frequently Asked Questions
Do I need both verification and anti-fake detection?
It depends on what you are protecting. Servers running reward competitions or invite-gated giveaways need anti-fake to keep those rewards honest. Servers worried about raids or bulk-join abuse need verification to control entry. Many growth-focused servers running both invite campaigns and public entry points eventually want both layers, not one instead of the other.
Which one is free?
Both have free tiers. Core OAuth verification, with automatic role assignment and no member limit, is free. Account-age anti-fake detection is included on every InviteForge plan at no cost.
Does verification stop fake invites from counting toward rewards?
No. Verification controls who gets into the server. It does not classify whether a join should count toward a leaderboard or auto-role milestone. That classification is anti-fake detection's specific job.
Which should I set up first?
If rewards are already live, set up anti-fake first, since it is a single threshold setting with immediate protection. If you are worried about raids or high-volume bulk joins, set up verification first, since anti-fake does not stop entry at all.