X Retires Twitter Domain Name: Users Must Migrate Security Keys and Passkeys Before Deadline

X has announced a significant domain migration that will affect users relying on hardware-based authentication methods. According to reports from October 2025, the platform is officially retiring the twitter.com domain name and requires account holders using security keys or Passkeys to complete a re-registration process. This marks an important technical shift as the company consolidates its operations under the new x.com branding.

What’s Changing for Security Key and Passkey Users

Users who have bound their accounts with hardware security keys or Passkeys to the old twitter.com domain must re-register these credentials to x.com within a two-week window. Security keys—physical devices that authenticate user identity—and Passkeys, the modern passwordless alternative, will become non-functional if not migrated to the new domain. X clarified that this action is purely a technical requirement for the domain transition and is not related to any security breach or vulnerability. The company emphasized that existing 2FA methods, including Authenticator apps, will continue to function normally and do not require any changes.

Timeline and Account Access Impact

The critical deadline for users to complete this migration was set for November 10th, 2025. Those who fail to re-bind their security credentials by this date will face account lockouts. Once locked, users have limited options: they can re-register through alternative verification methods, switch to a different 2FA approach such as Authenticator apps, or temporarily disable 2FA to regain access. X stressed the importance of completing this migration promptly to avoid disruption to account access.

Why This Matters

The retirement of the twitter.com domain name represents a full organizational transition to the x.com identity. By requiring users to update their hardware authentication methods, X ensures that all security infrastructure aligns with the new platform branding. This change primarily impacts the subset of users who have invested in hardware security solutions, while the majority of users relying on software-based 2FA methods remain unaffected by this policy shift.