Common Usernames to Reserve

Essential usernames every app should reserve. Learn which usernames you should always block and why. No need to maintain manual lists.

Essential Usernames to Reserve

Every app should reserve usernames from these categories to prevent security conflicts, maintain support channels, and ensure platform integrity. These categories are universal across platforms.

Instead of hardcoding lists, use the username.dev API to check these categories programmatically.

Common Reserved Categories

System & Infrastructure

System usernames are the most commonly exploited handles in phishing attacks. When someone messages you from @admin, you assume authority. Platforms block these to prevent impersonation of staff, conflicts with subdomain routing (like api.example.com), and bugs caused by programming keywords like null and undefined. Every platform from Twitter to Discord reserves these from day one.

Rules →
adminadministratorrootsystemapiwww

Government & Official Entities

Impersonating government entities is criminal in most jurisdictions. Fake @fbi or @police accounts enable dangerous scams. Platforms reserve these terms not just for user safety but for legal protection. Government agencies often have formal verification processes to claim these handles, similar to the verified badge program.

Rules →
fbicianasapoliceofficialgovernment

Security & Authentication

Security terms are weapons for phishing. A message from @verify saying "click here to confirm your account" looks legitimate. Handles like @login, @password, @secure, and @authenticate appear in thousands of social engineering attacks. Blocking these prevents attackers from gaining credibility through username selection.

Rules →
securitysecureauthloginpasswordverify

Support & Customer Service

Support impersonation is the #1 social engineering attack vector. Attackers register @support on a new platform, wait for users to have problems, then reach out offering "help" that involves sharing passwords or sending money. Reserving support terms ensures your official support team owns these handles before scammers do.

Rules →
supporthelphelpdeskcontactfeedbackbilling

Why These Usernames Matter

Reserving common usernames prevents:

  • Security conflicts with system infrastructure
  • Confusion with official support channels
  • Impersonation of administrative accounts
  • Legal issues with government terms

Test This with Your Own Username

Powered by username.dev

Programmatic Checks

Check common reserved usernames programmatically:

CURL

Frequently Asked Questions

Every app should reserve system terms (admin, root, api), support terms (support, help, contact), security terms (auth, login, password), and government terms (official, government). These categories are universal across platforms and prevent critical conflicts.