What’s happened? X has issued a warning to users that it’s moving logins to x.com and, as part of that, plans to phase out the twitter.com domain. Anyone using a hardware security key or a passkey needs to re-enroll by November 10 so the key is tied to x.com instead. X says this is not a security incident, and authenticator apps are unaffected.
- The company’s Safety account said that accounts using security keys for 2FA must re-enroll to keep access, via posts on X.
- Miss the deadline and your account will be locked until you re-enroll, switch to a different 2FA method, or turn off 2FA.
- X clarified the change targets YubiKeys and passkeys only, not authenticator apps.
- The stated reason: existing keys are bound to twitter.com, re-registering binds them to x.com so the old domain can be retired.
This is important because: The change can affect access if you miss the date, and it ties into a wider migration from twitter.com to x.com. That sort of switch touches logins, links, and lots of small tools people forget they rely on.
- If you miss November 10, account access is paused until you update 2FA or change methods.
- Hardware keys were registered to twitter.com. Updating your key registration ties them to x.com so they continue to work when you log in.
- Phasing out twitter.com risks breakage for embeds, older links, and automations that still reference the old domain.
Why should I care? If you use a YubiKey or a passkey on X, this is your to-do item. The bigger story is the domain shift, which could ripple into how links and embeds behave across the web.
- If you use a YubiKey or passkey, update your security key registration by November 10.
- If you’re not using passkeys, check why you might need one today.
- Users point out that phasing out twitter.com is likely to break lots of things, from old links to automations that still point to the legacy domain.
Okay, so what’s next? Treat it like a small migration. Update your key now, test your log in on desktop and phone, then clean up any shortcuts that still lean on twitter.com.
- Re-register your hardware key or passkey today, confirm you can log in on multiple devices, and stash backup codes. A temporary authenticator app can cover you if needed.
- Audit touchpoints that reference twitter.com, like bookmarks, link tools, and simple automations. Watch X’s developer notes for any embed or API changes.
