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 Uu Jia Su Qi and, where Uu Jia Su Qi accepts public or virtual numbers, to sign up for a Uu Jia Su Qi 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 1 public message records from the available MyTempSMS snapshot. Public messages are visible to everyone; number availability, Uu Jia Su Qi acceptance, verification, and delivery are not guaranteed. MyTempSMS is independent from Uu Jia Su Qi.
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 |
The current NetEase UU page lets you monitor a text on one of MyTempSMS's free public number inboxes without reserving that number. NetEase UU's help search describes entering the correct mobile number, requesting an SMS verification code, and submitting that code in the client login flow. Select the inbox before the official request and return to it afterward. If nothing arrives, use the platform's approved fallback instead of assuming delivery.
The page works best when you keep the selected number and its inbox together. Copy a listed number into the genuine NetEase UU verification field, request the text through the sender, and then review this public inbox for a new message. If nothing arrives, do not assume another public number is an approved workaround; consult the sender's own help or alternate sign-in process.
The NetEase UU workflow controls whether SMS is offered, while this page only exposes messages that reach its listed numbers. UU documents normal mobile SMS login but also says phone verification is not forced in every newer-client scenario. This means a missing code should be diagnosed in the exact login mode rather than assuming every UU session requires SMS.
NetEase UU's help content describes mobile-number login with a verification code and offers concrete delivery checks, including message interception by antivirus or security software. It also documents a different first-time WeChat route that may ask the user to register a mobile number before that linked login can be completed.
A UU-specific nuance is that newer clients do not necessarily force mobile verification for all basic use, while verified phones are recommended for points, support, and certain activities. The help center also has platform-specific troubleshooting, such as refreshing the macOS client when the send-code control does not respond.
For unresolved code delivery, use UU's feedback or online-service path after checking local SMS interception. If the account supports another legitimate login route, use that documented option rather than repeatedly requesting texts. Keep a private number bound if you depend on points, support, or account recovery.
Check the phone's spam, interception, antivirus, or security-message settings, which UU lists as common causes. If the message is still missing, submit feedback through the official UU help route.
Use the refresh step described in UU's macOS troubleshooting entry, then retry the normal login flow once. If the client still cannot send the request, use UU support instead of repeated clicking.
That can be consistent with current UU guidance, which says newer clients do not force mobile verification in every case. Use the login method presented by the client and verify a phone only when the feature requires it.
Use a number shown on this page only for the particular NetEase UU SMS step in front of you. Open its inbox first, request the message through NetEase UU, and check that same inbox for any delivered text.
The number is shared and the inbox is public. If you need continuing access to NetEase UU, keep its security and recovery methods tied to a private contact channel rather than to a temporary listing here.
NetEase UU's help search describes entering the correct mobile number, requesting an SMS verification code, and submitting that code in the client login flow.
UU advises checking whether antivirus, security, or message-blocking features intercepted the text and provides a feedback route when the code still cannot be received.
The help content says the newer UU client no longer forces mobile verification in every case, although verification is recommended for points, support, and some activities.
UU's help search includes a macOS troubleshooting item that suggests refreshing the client interface when the verification-code control cannot be clicked or sent.
UU's login guidance says first-time users following the WeChat login path may still need to register a mobile number before completing that account flow.
NetEase UU's reviewed help material explains ordinary mobile verification without publishing approval for shared inbox numbers, disposable destinations, virtual lines, or VoIP contacts.
Content review date: