ApplyDeskEvery Discord user ID is a snowflake: a big integer that encodes the moment the account was created. You do not need an API token to decode it. That is why “paste the ID” checkers exist, and why a staff form that only asks “how old is your account?” is leaving a gate on the table.
What the number actually means
Discord’s epoch is 1 January 2015. The high bits of the snowflake are milliseconds since then. Shift the ID right by 22 bits, add the epoch, and you have a creation timestamp. Alts, recovered accounts, and bought accounts still have a birthday. A two-day-old account applying for Ban Members is not a mystery.
Gates that match the role
- Public whitelist or member apps: 7–14 days. Stops the cheapest raid bots. Will not stop a determined person.
- Helpers and event staff: 14–30 days. They do not need a long history, but they should not be brand new.
- Moderators: 30–60 days is a reasonable floor if they must already be in the server.
- Admins and people with audit-log access: 90 days is common. You are trusting them with other people’s reports.
Account age is a filter, not a personality test. A four-year-old account can still leak tickets. Combine it with “must be a server member” and a real scenario section.
Do not make applicants type the date
People round, guess, or lie. If they sign in with Discord, you already have the ID. Decode it yourself, or put a minimum age on the form so applications that fail never hit the queue. Manual checkers are for IDs you were sent in staff chat, not for replacing login.
Use the free account age checker on this site for a one-off ID. For every applicant, turn the gate on in the form so you are not doing arithmetic in the review channel.