Discord Profile Viewer

Discord's user endpoint returns a fixed set of public fields: the username, the global display name, the avatar hash, the banner hash, the accent colour, and the public flags that drive badges. That is the whole surface. There is no email, no phone number, no IP, no server list and no message history, because the API simply does not expose them.

The account creation date is not returned as a field at all - it is derived from the ID, because a snowflake encodes its own timestamp. That is why an account age is available even for accounts you share nothing with.

Anything beyond this requires a bot that shares a server with the user, and even then it gets server-scoped information such as nickname, roles and join date rather than anything private. A tool that claims to show someone's email or servers from an ID is either guessing or lying.

The badges on a profile come from a `public_flags` integer where each bit is one badge: Staff, Partner, Hypesquad, Bug Hunter, the three Hypesquad houses, Early Supporter, Verified Developer and Active Developer among others. Reading them is the same bitwise operation as reading permissions.

Nitro and boosting badges are the exception - they are not in public_flags, because subscription state is not exposed on the public user object. A profile viewer can show you that someone is an Early Supporter but not whether they currently pay for Nitro.

Discord requires bot authentication on the user endpoint. An unauthenticated request returns 401 regardless of how public the fields are, which is a deliberate rate-limiting and abuse measure rather than a privacy one.

That is why this tool depends on the site being configured with a token. The bot needs no privileged intents and does not have to be in any server; it only has to exist so Discord has something to attribute the request to.

Badges are stored as a bitfield integer where each bit represents a different badge. The viewer unpacks this for you and shows human-readable names.