Free public number
$0- Public messages are visible
- Used by multiple visitors
- No registration required
- Best for low-priority testing
Use a free virtual number or temp number to receive SMS online from Firebase and, where Firebase accepts public or virtual numbers, to sign up for a Firebase account without paying for the number. You can also compare paid one-time and private options when you need more control. This page currently displays 10 public message records from the available MyTempSMS snapshot. Public messages are visible to everyone; number availability, Firebase acceptance, verification, and delivery are not guaranteed. MyTempSMS is independent from Firebase.
Choose a country
Check priceChoose a country
Check price| Feature | Free public number | One-time verification | Private rental |
|---|---|---|---|
| Best for | Testing or low priority | Quick verification | Frequent or long-term use |
| Cost | $0 | Varies by country | Varies by country |
| Number type | Shared | Single use | Private |
| Message visibility | Public | Order-specific | Private |
| Reusability | Multiple visitors | Single use | During rental |
| Active duration | While available | Until verified or expired | Selected rental period |
| Delivery guarantee | Not guaranteed | Not guaranteed | Not guaranteed |
| Setup time | Instant | At checkout | At checkout |
For a one-off check, use a free public number from the live list. Copy it to Firebase only when the current flow explicitly requests a telephone number. Keep this page open so you can revisit the corresponding inbox when the text is sent. Do not read successful SMS delivery as proof that the account step has been approved. Firebase Authentication is a developer service, not one consumer account system.
Pick a free public number that is active in the present list, copy it exactly, and use it only if the current Firebase workflow contains a phone field. After requesting the code, inspect the corresponding inbox rather than testing several numbers at once. A received text confirms delivery to the inbox, not acceptance by Firebase.
New-account verification may use more than one channel. To Register Firebase, follow the method assigned by the live flow. Firebase Authentication is a developer service, not one consumer account system. An app developer can enable phone-number authentication so an end user signs in with a one-time SMS code, but Firebase also supports email/password, federated providers, anonymous authentication, and other methods.
Public-number availability and platform acceptance should be evaluated separately. If the number is rejected, the cause can be invalid formatting, disabled phone sign-in, region policy, quota, reCAPTCHA/app-verification failure, or anti-abuse throttling. Developers should inspect Firebase Auth errors and configuration. End users should not rotate public numbers to bypass the app’s restrictions or Firebase abuse controls.
Firebase phone authentication is controlled by the app’s Firebase project. The developer must enable phone sign-in and configure allowed SMS regions; Firebase also uses app verification such as Play Integrity or reCAPTCHA and applies SMS quotas and anti-abuse limits. Therefore a number may receive normal texts but still be ineligible for a particular app’s Firebase flow.
If you lose a phone number used as a Firebase credential, use whatever recovery or linked provider the app developer has implemented, such as email or federated sign-in. If no alternative exists, contact that app’s support. Keep at least one durable, private account factor available.
Confirm that the app actually uses Firebase phone authentication and that the phone sign-in provider is enabled for the project. Check the E.164 number format, allowed SMS region, app-verification step, and whether requests are being throttled.
If the number is rejected, the cause can be invalid formatting, disabled phone sign-in, region policy, quota, reCAPTCHA/app-verification failure, or anti-abuse throttling. Developers should inspect Firebase Auth errors and configuration. End users should not rotate public numbers to bypass the app’s restrictions or Firebase abuse controls.
If you lose a phone number used as a Firebase credential, use whatever recovery or linked provider the app developer has implemented, such as email or federated sign-in. If no alternative exists, contact that app’s support.
For a one-off check, use a free public number from the live list. Copy it to Firebase only when the current flow explicitly requests a telephone number. Keep this page open so you can revisit the corresponding inbox when the text is sent. Do not read successful SMS delivery as proof that the account step has been approved.
Do not assume a listed number is approved by Firebase. MyTempSMS only shows an inbox; the platform can reject a number based on its own rules even when SMS delivery itself works.
To Register Firebase, rely on the verification route displayed by the service at that moment. Firebase Authentication is a developer service, not one consumer account system. An app developer can enable phone-number authentication so an end user signs in with a one-time SMS code, but Firebase also supports email/password, federated providers, anonymous authentication, and other methods.
Confirm that the app actually uses Firebase phone authentication and that the phone sign-in provider is enabled for the project. Check the E.164 number format, allowed SMS region, app-verification step, and whether requests are being throttled.
If the number is rejected, the cause can be invalid formatting, disabled phone sign-in, region policy, quota, reCAPTCHA/app-verification failure, or anti-abuse throttling. Developers should inspect Firebase Auth errors and configuration.
If you lose a phone number used as a Firebase credential, use whatever recovery or linked provider the app developer has implemented, such as email or federated sign-in. If no alternative exists, contact that app’s support.
Firebase phone auth can apply project region policies, reCAPTCHA or app verification, per-number abuse throttling, project quotas, and developer configuration. A receivable phone number alone does not guarantee the authentication request will be accepted.
A MyTempSMS inbox is publicly readable, not a private mailbox. Use it only with that limitation in mind, and keep important Firebase accounts tied to a private number or other controlled recovery method.
Content review date: