We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
If this tool helped you, you can buy us a coffee ☕
Check whether a mainland China mobile number matches the provider’s complaint-risk or high-frequency criteria.
Only submit a number you are authorized to process. The middle four digits are masked in results.
Screens for complaint behavior in the provider model and is the recommended default.
Each query costs 10 coins
Enter a mobile number and choose a screening scope to view the result.
A mainland China mobile number returns forbid=1 before an outbound call. The precise meaning is that it matched the third-party provider’s complaint-risk criteria at the selected screening level. That is a useful signal to pause automated dialing and review the contact. It is not proof that the subscriber committed fraud, broke a law, or made a malicious complaint, and it does not replace your own consent records.
The page screens one 11-digit number at a time using two inputs: Mobile Number and Screening Level. The provider can return Not Matched, Complaint Risk, or High-Frequency Risk. This is not an official carrier blacklist, subscriber-identity search, phone-ownership verification, credit report, criminal-record search, or legal determination. No subscriber name, address, or identity-document data is displayed.
Appropriate uses include pre-screening an authorized call list, checking a number before a customer-service callback, reviewing old contact records, and investigating repeated-contact complaints. The response only describes this request, this level, and the provider’s data at that time. It cannot answer whether a person is trustworthy or whether a particular call is lawful.
+86, spaces, hyphens, a URL, or a note.The format rule ^1[3-9]\d{9}$ only confirms the shape of a mainland mobile number. It does not prove that the number is active, belongs to the person who supplied it, or may be contacted. The full number is sent to the ToolKK backend and the bound third-party provider to perform the lookup; masking the result is not the same as never processing the full number.
| Page option | Request value | Provider-model scope | Typical use |
|---|---|---|---|
| General | 1 | Narrow scope for numbers the provider calls extremely sensitive | A conservative flow that blocks only the strongest modeled signal |
| Sensitive | 2 | Includes numbers associated with complaint behavior in the model | Routine screening for service callbacks and notices |
| High Risk | 3 | Broader scope that may include complaint intent and frequency signals | Workflows that require a larger manual-review pool |
“High Risk” describes a broader screening scope; it does not promise greater accuracy or prove that a match is more severe than a General match. A number can produce different results when the level changes because the matching criteria change. Define the business purpose and acceptable false-positive rate first instead of switching levels until a desired result appears.
If your team has no established rule, begin with the default Sensitive level. Compare matches with verified complaints, explicit refusals, contact frequency, and human review over a defined period. Use that evidence to decide whether to narrow or broaden screening. Do not convert the three labels into low, medium, and high personal credit scores.
| Value | Displayed meaning | Reasonable next action | What it does not establish |
|---|---|---|---|
forbid=0 | Not matched | Still verify consent, permitted hours, and your internal suppression list | It does not prove safety or grant marketing permission |
forbid=1 | Complaint risk | Pause automated contact and review the source and context | It does not prove fraud, illegality, or bad intent |
forbid=2 | High-frequency risk | Review recent attempts, cross-team duplication, and frequency caps | It does not prove that a complaint was filed |
Keep the provider message with the numeric state. A timeout, provider error, or empty result is not a Not Matched response and should not automatically release the number for contact. If the response conflicts with a documented current request from the customer, stop bulk automation and let an authorized reviewer check the timestamp, number source, level, and contact history.
The final contact decision should also consider purpose, date and scope of consent, current relationship, explicit refusals, contact frequency, internal do-not-contact lists, and applicable rules. This lookup is one external signal inside that process, not an independent approval or prohibition engine.
Example 1: a requested support callback. A customer creates a ticket today, supplies 138****8000, and asks for a telephone reply. The agent enters the full number, leaves Sensitive selected, and receives forbid=1. The match is not a reason to label the customer as malicious. A proportionate response is to verify the ticket’s immediate consent, make one human callback during the agreed window, and keep the number out of unrelated marketing automation.
Example 2: an old event list. A number collected at an event two years ago returns forbid=0 under High Risk. The result does not renew old consent or create a new legal basis. The operator still needs to inspect what the person agreed to, how long the record should be retained, and whether the person later refused. Without adequate support, remove it from the current campaign rather than treating Not Matched as permission.
Comparison: a frequency match. Sales, logistics, and support systems all contact the same customer and the response is forbid=2. Investigating shared frequency caps, duplicate jobs, and the customer’s suppression preference is more useful than trying different caller IDs. Document the system behavior without assigning a character or credit label to the subscriber.
Coverage gaps, delayed records, recycled numbers, missing complaint context, and false matches can all occur. A fairer workflow uses the result inside a sequence of consent verification, frequency review, human assessment, documented action, and scheduled deletion rather than turning it into a permanent personal label.
A mobile number is information that can identify or relate to a person. State a specific purpose and lawful basis before processing it, submit only numbers necessary for that purpose, and restrict who can see full numbers and results. Masking the middle digits reduces exposure on the result screen, but it does not replace access controls, transport security, retention limits, or deletion procedures.
Chinese telecommunications guidance for call-center operations sets boundaries around outbound services. Official reminders about telephone marketing emphasize consent, process records, and stopping calls after an explicit refusal. Rules for commercial short messages similarly reflect prior consent, accessible opt-out, and disturbance reduction; those message rules are useful adjacent context, not a claim that every provision directly governs every voice call. Your compliance team should assess the current rules for the organization, location, and communication channel involved.
China’s Personal Information Protection Law calls for a clear and reasonable purpose, direct relevance, minimum impact, security measures, and respect for individual rights. A defensible internal record should include the requester, time, purpose, consent source, selected level, disposition, and deletion date. Do not sell, publish, or reuse a number or match for unrelated profiling.
This guide follows the actual page fields and the Aliyun Market product used by the importer. The official materials below provide privacy and communications-governance context; they do not supply, certify, or endorse the API’s risk data.
You can now return to the form, enter one mainland China mobile number you are authorized to process, start with Sensitive, and review the result together with your consent and contact records.