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 Battle and, where Battle accepts public or virtual numbers, to sign up for a Battle 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, Battle acceptance, verification, and delivery are not guaranteed. MyTempSMS is independent from Battle.
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 |
Open a listed number, trigger the intended account action, and verify both sender and message purpose when the public inbox updates. For Battle, observed “battle” sender messages identify themselves as battle.net verification codes is the cited Battle sender mapping condition. The inbox view for observed “battle” sender messages identify themselves as battle.net verification codes is public.
Open a listed number, trigger the intended account action, and verify both sender and message purpose when the public inbox updates. Open Battle sender mapping with a free number here. Confirm observed “battle” sender messages identify themselves as battle.net verification codes before using the message. On refusal, follow Battle sender mapping through the documented route.
Blizzard says Battle.net Phone Notifications require a supported text-enabled cell phone to get started. That requirement means a number merely capable of appearing in a public SMS list is not necessarily an eligible Battle.net phone. Recheck supported cell phone on the service screen.
Blizzard says Phone Notifications can support account actions such as unlocking a Blizzard account, removing a lost Authenticator, recovering an account name, and resetting a password. The phone can therefore become important to long-term recovery. Use phone recovery actions as the practical checkpoint.
Blizzard’s security guidance promotes the Battle.net Authenticator in the Battle.net mobile app as an additional account-protection method. Users should follow the Authenticator or Phone Notifications flow actually attached to their account. Confirm Battle.net Authenticator against the cited guidance. Follow Battle.net Authenticator rather than a generic SMS assumption.
Blizzard says Battle.net Phone Notifications can be configured to provide account-activity notifications in addition to assisting with selected account actions. That makes a personal controlled phone more appropriate than a shared public inbox. Compare account activity alerts with the live prompt first. Keep account activity alerts inside the supported account flow.
Read the message body before treating the sender label as Battle.net, because public inboxes can contain unrelated marketing text with the word battle. Use only messages that clearly identify Battle.net and match an action you initiated. For account security or recovery, continue through Blizzard’s official Battle.net flow.
Check whether the number is a supported text-enabled cell phone as required for Phone Notifications. Use a personal eligible mobile number rather than repeatedly cycling public or unsupported numbers. If the account has another configured security method, follow the Battle.net Authenticator or official support path.
Do not use the code or ignore the security meaning of the message. Go directly to the official Battle.net site, review account security, and use the Authenticator or Phone Notifications recovery functions that are already attached to the account. Contact Blizzard support if control of the account is uncertain.
For Battle sender mapping, use a free listed number after checking observed “battle” sender messages identify themselves as battle.net verification codes. Open a listed number, trigger the intended account action, and verify both sender and message purpose when the public inbox updates.
For password change alert, a public inbox can expose password change alert messages to other visitors. The cited password change alert guidance identifies observed battle messages also include password-change security notices. Keep password change alert on a private recovery method you control.
Current MyTempSMS samples under the sender label Battle include messages that explicitly say “Battle.net verification code,” linking this project label to Battle.net verification traffic.
Blizzard says Battle.net Phone Notifications require a supported text-enabled cell phone to get started. Check supported cell phone in the cited guidance. Keep supported cell phone matched to the live prompt.
Blizzard says Phone Notifications can support account actions such as unlocking a Blizzard account, removing a lost Authenticator, recovering an account name, and resetting a password.
Blizzard’s security guidance promotes the Battle.net Authenticator in the Battle.net mobile app as an additional account-protection method. Users should follow the Authenticator or Phone Notifications flow actually attached to their account.
Blizzard says Battle.net Phone Notifications can be configured to provide account-activity notifications in addition to assisting with selected account actions. That makes a personal controlled phone more appropriate than a shared public inbox.
MyTempSMS samples under Battle include a Battle.net password-change notice telling the recipient to visit the website if the change was not performed by them.
Content review date: