Proxy Mail QA

Test phone-first sign-up without receiving real SMS

In China, India, Pakistan and much of South-East Asia, people sign up with a phone number and a code by SMS. Testing that with real messages is slow and costly, and in some countries hard to set up at all. Test numbers with fixed codes do the same job without a message being sent.

Updated

Phone-first sign-up is common across Asia: an 11-digit number and an SMS code in China, a mobile number and a one-time code in India and Pakistan, and in Indonesia often a code by WhatsApp. To test it you need codes that arrive every time, quickly, for numbers you control. Real SMS gives you none of that reliably.

Why real SMS is hard to test with

  • Registration before sending. India requires businesses to register their sender ID and message templates (DLT) before SMS are delivered. In mainland China, SMS signatures and templates are approved by the provider before use.
  • Real-name SIMs. In China and Pakistan a SIM card is registered to a person’s ID, so a team can’t simply buy a stack of test numbers.
  • Cost and delays. Every test run pays for messages, and delivery can take seconds or minutes.
  • Virtual numbers refused. Lookup services can tell a virtual (VoIP) number from a mobile one, and many apps refuse virtual numbers before sending a code, as bots use them. Online SMS services hand out exactly those.

Option 1: your auth provider’s test numbers

Most auth providers let you register test numbers that take a fixed code and never send a message:

  • Firebase Authentication: add up to 10 fictional numbers, each with a 6-digit code, under Phone numbers for testing in the Phone provider’s settings. No SMS is sent.
  • Supabase Auth: add test numbers and their codes under Authentication → Sign In / Providers → Phone, in Test Phone Numbers and OTPs, with a date they stop working. An SMS provider must still be set up, but no SMS is sent.
  • Clerk: in development, numbers from +1 (XXX) 555-0100 to 555-0199 take the code 424242.

Keep these in development and staging projects. A production project should have none.

Option 2: a test-mode code in your own backend

If you send SMS yourself, a test mode with a fixed code is the usual answer. In China it’s often called a universal code (万能验证码). Done carelessly, it is a way into every account. Done carefully:

  1. Limit it to listed numbers. The fixed code works only for numbers on a short test list, never for any number.
  2. Turn it on by setting, off by default. Read it from an environment variable that only development and staging set.
  3. Leave it out of release builds. In a mobile app, keep the code path behind a build flag the release build doesn’t include. Check the release build refuses the code before it ships.
  4. Check production refuses it. Add a test to your release checks that signs in to production with a test number and the fixed code, and expects it to fail.

What to test in the flow

  • A wrong code is refused, and the number of tries is limited.
  • An expired code is refused, and asking again sends a new one.
  • After a resend, an older code works or doesn’t, as you decided, and the app says which.
  • The number is stored in one format (with the country code) whatever the person typed: spaces, a leading 0 or +86.
  • Someone who signs up with the same number again is sent to sign-in, not given a second account.
  • If the app also asks for an email address, the confirmation email arrives and works. Proxy Mail QA covers that step: create an address, sign up with it, and wait for the code or link.

Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

Create a free accountOpen the app

Questions

Can Proxy Mail QA receive SMS codes?

No. Proxy Mail QA receives email only. Real-name rules for SIM cards in China and Pakistan, and India's registration rules for business SMS, make shared test numbers impractical, so we don't offer them. Use your provider's test numbers, and Proxy Mail QA for the email steps.

Can I use a free online number to receive the code?

Don't. Anyone can read the messages on those sites, so anyone can take over an account made with one. Many apps also refuse virtual numbers.

Is a fixed test code safe?

Only when it's limited to a short list of test numbers and can't work in a release build. A fixed code that works for any number in production is a way into every account.

My form needs a phone number but never sends an SMS. What should I type?

A number from a range set aside for fiction: 07700 900000 to 07700 900999 in the UK, ACMA's list of 0491 57x xxx numbers in Australia, or 555-0100 to 555-0199 after any area code in North America. They look real and reach no one. Elsewhere, add one of your app's own test numbers per country to the project's ready-made Phone number: in Project settings → Custom fields, or with save_custom_field for agents.

Built your app with an AI tool? Pick yours