Get an X verification code on a temporary number

X asks for a phone number in three separate spots of its verification flow, and each one wants a live number for a different reason. During sign-up, the service shows a phone-or-email field before you pick a username — feed it a number and Twitter's SMS system texts a six-digit code to a code-entry screen with six boxes. Later, X's automated abuse checks can flag an account for a burst of follows, an odd login location, or posting patterns that look scripted; the account locks and the unlock screen demands SMS verification, a phone number and a fresh code, before you can use Twitter again. Third, if you turn on SMS-based two-factor login, the service texts a new code on every single sign-in from a new device, so that number has to be reachable each time, not just once.

The numbers above cover the first two verification cases well: get an active number, type it into the field, and read the SMS code that lands on this page a moment later. Every number here is shared, so the code you need is the only thing you take from the service — treat the rest of that number's inbox as background noise from other people's sign-ups.

A US number and a Canadian number both carry the +1 dial code, so the verification field on the service accepts either without asking a follow-up question about the country. Pick the country that matches the account you are opening, or use whichever number shows active if the account itself has no country tied to it.

Twitter runs every number a user submits through a spam and abuse filter before it sends anything. That filter checks two things: whether the number's range looks like VoIP rather than a mobile carrier, and whether the number is already tied to another account in Twitter's own database. A shared number fails the second check more often simply because more people have typed it into the field before you — the service sees a number with account history attached and blocks the new sign-up with "this phone number can't be used to verify this account."

Spend time or spend a dollar

Two honest paths from there on Twitter. If you have a few minutes, get another active number from the list above; new numbers rotate in through the day and a number with no account history usually clears the Twitter check on the first try. If you need the account working now, rent a private number instead: it runs about $1 for 20 minutes and refunds automatically if the code never arrives, and because nobody else can request a code on it, Twitter sees a number with a clean history and no prior sign-up. Rent one at SV Number whenever the shared numbers keep bouncing.

Twitter's own help pages explain what its verification step checks and how to appeal a locked account at x.com — worth a look if a number that should be clean still gets rejected by the service.

On Twitter, a number here is receive-only, built to catch one SMS verification code and nothing more. You cannot use it to send a direct message, you cannot answer a call Twitter places to it, and the service never sees it as anything but a verification step. Once the code clears and the account opens, Twitter moves on to the device and session you are using; this page keeps showing the number's messages, but no part of the Twitter account lives here afterward.

A shared phone number also cannot back a Twitter account long-term. If you leave Twitter's SMS two-factor turned on, every future login sends a new code to the same phone number field, and anyone else who picks up that shared number later can read it just as easily as you did today — a login code, a password-reset link, an unlock request. That is fine for the one verification code you needed to open the Twitter account; it is the wrong choice for a number you plan to keep tied to it.

None of that makes the free numbers a bad tool — they exist for exactly this job, catching a verification code once at no cost. Where they run out of road is anything Twitter checks a second time, and a private phone number is what closes that gap.