Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 2 min read

We counted which apps send OTP codes to shared virtual numbers (900 tries, Nov 2026)

If you test sign-up flows, run QA across countries, or just wonder why a free online number never got your code, here is some real data. We run a receive-SMS service, and between 27 October and 16 November 2026 about 900

If you test sign-up flows, run QA across countries, or just wonder why a free online number never got your code, here is some real data. We run a receive-SMS service, and between 27 October and 16 November 2026 about 900 free shared numbers on one pool either received an OTP or timed out. We counted the results per app and country.

How we counted

A try is a free number that either received the code or waited the full time without it. Numbers the visitor gave back early are left out, because that says more about patience than about the app. Only app and country pairs with at least 8 tries are shown below.

Apps that usually deliver

App (country) Codes / tries Success
Marktplaats (FR) 45 / 46 98%
YouTube (PK) 13 / 16 81%
OpenAI (IN) 19 / 27 70%
Airtel (IN) 14 / 21 67%
Opay (NG) 14 / 21 67%
Fiverr (DE) 16 / 26 62%
Discord (DE) 8 / 13 62%

Apps that rarely deliver

App (country) Codes / tries Success
Telegram (IN) 2 / 39 5%
Telegram (NG) 1 / 13 8%
Telegram (PK) 0 / 11 0%
YouTube (PH) 4 / 31 13%
Foodpanda (PK) 0 / 8 0%

Three things that surprised us

1. Country matters as much as the app. YouTube delivered 81% of codes in Pakistan and 13% in the Philippines. By country overall, France delivered on almost 9 of 10 tries, Germany and Nigeria on more than 4 in 10, India on about a third, and Mexico and the Philippines rarely worked.

2. Some big apps simply refuse shared numbers. Telegram delivered 8 codes out of 127 tries across all countries. Amazon delivered 2 out of 50 in our wider logs. Waiting longer does not help; the SMS is never sent. We have since removed apps like these from our free list so people stop wasting time.

3. People give up too early. A large share of numbers were cancelled about a minute and a half after they were issued. International SMS can take several minutes. Give it the full 10 to 15 minutes before you conclude it failed.

What this means for your tests

  • For automated end-to-end tests, a free shared number is only reliable for apps and countries in the first table. Do not build CI on it.
  • For anything that must work every time, or for apps like Telegram, use a private number (one-time or rented) that only your test account receives SMS on.
  • If you send OTPs yourself and see users from shared-number ranges, expect them. Blocking them is a product choice, but it explains some of your "never received" tickets.

The data

The full table (132 app and country pairs, counts only, no phone numbers or user data) is on Kaggle under CC BY 4.0: SMS code delivery to free virtual numbers by app. There is also an interactive chart on Observable.

Disclosure: I'm part of the team behind receive-smss.net, which offers free numbers, private one-time numbers and rentals. The figures come from our own logs and change over time.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.