---
title: "Test sign-up for people in mainland China · Proxy Mail QA"
description: "Phone-first sign-up, real-name rules, 姓名 and province fields, and why a test account never uses a real 身份证 number, for apps used in mainland China."
url: https://proxymail.qa/solve/china-sign-up-testing
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# Test sign-up for people in mainland China

Sign-up in mainland China starts with a phone number, often has to check who the person really is, and runs on a network where Google's services don't load. Test each of those without a real person's number or ID, and from a mainland network.

Updated 13 November 2026

## What’s different about sign-up in China

- **Phone first.** Most apps sign people up with an 11-digit mobile number and an SMS code. An email address, if asked for at all, often comes later, to bind to the account.
- **Real-name rules.** Services that publish information or offer messaging must check a new user’s real identity (Cybersecurity Law, article 24). The 2022 account rules name the ways to do it: by mobile number, by ID number, or by unified social credit code for an organisation ([互联网用户账号信息管理规定](https://www.cac.gov.cn/2022-06/26/c%5F1657868775042841.htm), article 9). Most apps rely on the phone number, since a SIM card is registered to its holder’s ID. Some, such as games, payments and lending, also check a name and 身份证 number with a verification service.
- **What doesn’t load.** Google sign-in, reCAPTCHA, Google Fonts and Firebase don’t work from mainland networks. A sign-up page that waits for any of them looks stuck or broken. Test from a mainland network with any VPN turned off, as your users will be.
- **Social sign-in** is WeChat, Alipay or QQ, not Google or Apple. Proxy Mail QA doesn’t sign in with them: test those with accounts your team controls.

## Real-name checks without a real person

**Never put a real 身份证 number in a test account.** Not yours, not a colleague’s, not one found online. It’s someone’s identity: China’s personal information standard lists ID numbers as sensitive personal information (GB/T 35273-2020, appendix B), and the Personal Information Protection Law sets stricter rules for handling it. A test database is copied to laptops, logged and pasted into bug reports, and every copy would hold that person’s number.

A made-up number isn’t safe just because it’s made up. A 身份证 number has 18 characters: a 6-digit region code, the date of birth (8 digits), a 3-digit sequence (odd for men, even for women) and a check character, 0 to 9 or X. The check character is a simple sum anyone can work out, so random digits with a real region code and date can belong to a real person.

Two kinds of number can’t be anyone’s:

- **The standard’s own example**, 11010519491231002X, from GB 11643-1999.
- **Region code 99**, which no province has, with the persona’s date of birth and a correct check character.

When a lead adds the ready-made National ID number field in Project settings → Custom fields, Proxy Mail QA puts one of these in a 身份证 field: it follows the format and never matches a real person. A form that only checks the pattern and the check character takes it. A form that also checks the region code refuses the second kind, so test that path with the standard’s example. The full list of formats is on [field formats](https://proxymail.qa/docs/field-formats).

For the verification itself, where the app sends a name and number to a verification service:

1. **Don’t call the real service from test.** Put the check behind a setting, and in development and staging answer it from a stub that passes or fails as the test asks.
2. **Test both answers.** A number the service accepts lets the person in; one it refuses shows a clear message and lets them try again.
3. **Test the limits.** A person under 18 gets the experience the rules ask for (games limit playing time for minors), and the same number can’t make a second account if the app allows only one.

## Phone-first sign-up

Mainland China has no phone numbers set aside for fiction, so Proxy Mail QA leaves phone fields empty rather than make up digits that could reach someone. Use your provider’s test numbers, added to the project’s Phone number for China, or a test-mode code (万能验证码) that works only for listed numbers and never in a release build. The [phone-first guide](https://proxymail.qa/solve/phone-first-sign-up-testing) covers both.

A project lead adds the number once, as China’s test number on the project’s [Phone number](https://proxymail.qa/docs/custom-fields#ready-made-fields): in **Project settings → Custom fields**, or through an agent with `save_custom_field` and the Phone number’s `phones`. `form_values` then puts the same number in every phone field for a test account from China.

## Names, addresses and dates

- **One 姓名 field.** A Chinese name is a family name then a given name, two to four characters with no space: 王伟, 欧阳子涵. Make the test account with China as its country (in the app’s **New address** or `country: "CN"` for agents and tests) and the persona gets a name from Chinese lists. Check that the app keeps all four characters of a compound family name such as 欧阳 and doesn’t split the name on a space that isn’t there.
- **Province, city and district.** Chinese forms ask for 省, 市 and 区, usually as menus, then 详细地址. The persona’s answers agree with each other and with the 邮编: 广东省, 深圳市, 福田区 and 518000, for example, with a made-up street, 测试路1号, so nothing is ever sent to a real door.
- **Dates.** 出生日期 and 生日 are read as a date of birth, and an example such as 1990年1月22日 gets the same format.

## Email in Chinese

Verification and reset emails in Chinese are read like any others: the code after 验证码, the link, and how long it lasts (10分钟内有效). Make sure the email’s subject and sender name read well in Chinese mail apps, and that the code isn’t only in an image, which some clients block.

## Automating this?

Make it a test: createAddress with country CN gives a Chinese name (王伟) and an address whose province, city, district and postcode agree, and formValues fills a Chinese form in its own script. When a lead has added the ready-made National ID number field, a 身份证 field gets a number that follows the format and can't be anyone's.

[Node.js client](https://proxymail.qa/docs/node) [Python](https://proxymail.qa/docs/python) [Set up your coding agent](https://proxymail.qa/docs/api#agent-setup)

## 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 account](https://app.proxymail.qa/?mode=signup&from=site-solve-china-sign-up-testing)

## Questions

### Can a test account use my own 身份证 number, just once?

No. Test data is copied, logged and shared far more than real data, and every copy would hold your number. An ID number is sensitive personal information in China, with stricter rules than a name or an email address. Use a number that follows the format and can't be anyone's.

### If I make up 18 digits with the right check character, is that safe?

Not on its own. The check character is easy to work out, so a made-up number with a real region code and a plausible date of birth can belong to someone. Use region code 99, which no province has, or the worked example in the standard.

### Can Proxy Mail QA receive the SMS code?

No. Proxy Mail QA receives email only. Use your provider's test numbers or a test-mode code, as the phone-first guide describes, and Proxy Mail QA for any email step.

### Are the Chinese names real people's names?

They're combined from lists of common family and given names, never taken from anyone's record. A common name such as 王伟 is shared by many people, as any common name is.

### Can I use Proxy Mail QA from mainland China?

Yes. The app, the site and the tools work without a VPN, if more slowly than elsewhere. Sign in with an email code: Google sign-in doesn't work from the mainland.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Email limits in auth providers while you test](https://proxymail.qa/solve/auth-email-limits): Supabase's 2 an hour, Firebase's 5 email links a day, Auth0's 10 a minute and Clerk's 100 a month, and how to send your own.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [CAPTCHA, Google and Apple sign-in in tests](https://proxymail.qa/solve/captcha-and-social-sign-in-tests): Published test keys for reCAPTCHA, hCaptcha and Turnstile, and what to test instead of automating Google and Apple sign-in.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Check that one user can't see another's data](https://proxymail.qa/solve/vibe-coded-app-data-leaks): A curl with the anon key for tables anyone can read, and two signed-up accounts for policies that let every user read every row.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-ups over several screens](https://proxymail.qa/solve/multi-step-sign-up-testing): One test account across every screen of the sign-up, with your form's own questions filled the same way each time.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)
