Last updated: November 9, 2026.
When a verification code does not arrive, check the destination on the screen before pressing Resend. The service may have sent it to an email address, another app session or a different phone number. If it says the number is unsupported, the request needs attention before there is a message to look for.
Keep the current request open, read any error or countdown and check the receiving phone, mailbox or inbox. Delivery times and retry rules vary between services, so follow the instructions for the request you are making.
Start with the message on your screen
| What you see | Your next step |
|---|---|
| Number not supported | Check the country, format and permitted number type |
| Code sent, but no message | Check the stated destination and whether it can receive that message |
| Code received, but rejected | Match it to the current request and check its expiry and characters |
| Too many attempts or a countdown | Stop requesting codes and follow the waiting period |
| Online inbox will not open | Check the inbox site's access requirements or loading problem |
Check the destination and the number
Read which delivery method the service selected. For example, Telegram can send a login code to a connected Telegram session. Its authorization documentation describes several possible routes. Open the destination named on your screen, even if you were expecting an SMS.
For an existing account, compare the masked phone number or email with your own details. If it points to an old number, use that service's account-recovery options. Waiting in another inbox will not redirect the code.
If you are entering a phone number, look for a missing digit, the wrong country selection or a repeated country code. Some forms add the prefix; others expect the full international number. The US phone-number format guide shows how +1 fits with the ten national digits. After correcting an error, check the final destination once before submitting.
If the code should reach your phone
On a dual-SIM phone, check that the line receiving the code is active. Look in spam and unknown-sender folders, and check whether you have blocked the sender. A trusted contact can send an ordinary text to the same number to help narrow the problem.
If messages from several unrelated senders fail, ask your carrier to check incoming SMS. Mention a recent activation, number transfer or plan change if the problem began after it. If ordinary messages arrive but one app's codes do not, tell the app's support about that difference. Ordinary and automated texts may take different routes, so one successful text does not establish that every type will arrive.
A sender may also reject a line that otherwise receives SMS. Microsoft's verification guidance, for example, excludes VoIP numbers and warns about blocks after repeated requests. Check the requirements of the service you are using, and choose another verification method only if it offers one for your account.
If you are using a browser SMS inbox
Match the full number on the request with the one at the top of the inbox. Then look at the sender and arrival time. The newest message could belong to another visitor or come from a different service. An app-specific last-message time is more relevant to that app, although past activity cannot guarantee another delivery.
The app directory groups listings by the sending service. The inbox activity page shows recent texts on listed numbers. Use both to inspect activity, then check the exact destination of your request; neither guarantees a new delivery.
The Refresh button retrieves messages the website has received. To request a new code, you need to use the sending service's controls and follow its timer. Switching numbers or sending requests from several devices will not reliably clear a restriction.
For a loading or access problem on Receive SMS Live, use the inbox help center. Check the access labels in the temporary number directory if sign-in is required: members-only access does not give you an exclusive inbox.
Check the inbox update and receipt history
On Receive SMS Live, the time of the last successful inbox update helps you check whether the page has retrieved fresh data. If the tool shows Update failed, choose Retry update. The last successful timestamp stays unchanged until a request succeeds. A successful refresh can return the same messages when no new text has arrived.
For a wider view, open the SMS activity report by country. It shows available public numbers, how many recorded an SMS and the number of receipts in its dated window. Complete UTC daily totals appear separately. A busy country or inbox does not establish that your particular sender accepted the number.
To receive SMS online, choose the country you need and open the exact number before making a permitted request. Compare its number and arrival times with your own request. Use the sender’s resend controls only when its instructions allow another attempt.
If a code arrives but does not work
Use the code for the request still open on your screen. A late message may belong to an earlier attempt, a different account or another browser session. Check the sender's expiry instructions and enter the characters exactly.
Avoid guessing missing digits. WhatsApp's registration help warns that repeated incorrect guesses can trigger a waiting period. If the screen shows a restriction, wait as instructed before trying again.
Give support the details they can act on
Contact the sending service about rejected numbers, account restrictions or verification errors. Contact the carrier or number provider when several senders cannot reach the line. For an inaccessible webpage or messages that fail to display, contact the inbox website.
Include the approximate request time and time zone, your device and browser, and the exact error. For this site, add the affected page URL to your support request. You can describe a display problem without sharing a password or verification code.
