Guide
How to verify that a Discord invite goes where it claims
An invite code is opaque by design. Resolving it tells you which server it opens - which is a different, smaller, and more answerable question than whether that server is safe.
Step 1: reduce the link to a code
Discord serves invites from discord.gg/<code> and discord.com/invite/<code>. Anything else - a redirect service, a shortener, a lookalike domain - is not an invite link, it is a link that may eventually reach one.
Take the final path segment. That is the code, and it is the only part that needs checking.
Open the Invite CheckerStep 2: resolve it against Discord
Discord answers GET /invites/{code} without authentication, and with with_counts=true it returns the destination server and two approximate counts. That is the request this checker makes, and the only one it makes.
A 404 means Discord does not know the code: it never existed, it expired, or it was revoked. A 429 means the check was rate limited and says nothing about the invite. The checker distinguishes those rather than collapsing them into "invalid".
Step 3: compare the destination against an official source
Resolving a code tells you a server ID and name. Names are not unique and are trivially copied, so the ID is the part that identifies anything.
Discord publishes the support server on an application's own record. Where a code resolves to one of those, the checker reports it as corroborated by an official source and links the app - that is a genuine identity check rather than a vibe. Where it does not, the checker says so instead of inventing confidence.
Step 4: read the counts for what they are
The two numbers Discord returns are named approximate_member_count and approximate_presence_count. They are approximations for an invite preview: a total and an online figure at that moment.
They are not daily active users, not a measure of how much anyone talks, and not comparable across servers of different sizes and timezones. The checker shows them with that caveat attached rather than as a metric.
Step 5: check consistency over time, not safety
A code that resolved to one server last week and a different one today has changed destination. That is a concrete, checkable signal, and it is the one this tool is actually for.
What no invite check can tell you is whether the destination is trustworthy. Validity is not safety. The checker deliberately reports valid, destination consistent, official-source corroborated and last checked, and leaves risk unknown, because those are the claims the data supports.
How this catalog decides what it will claim