The filing process in the service provider’s backend follows standard guidance; just follow the prompts. The real challenge is rejection—especially when rejection reasons are vague, leaving you unsure of what to change, forcing you to guess, resubmit, and face rejection again.
Below is a comparison checklist of the most common rejection reasons. Note that filing policies and review standards may vary over time and across接入 providers (接入商). This article outlines long-standing general principles; for specific timeliness and requirements, refer to your current接入 provider’s backend.
Process Overview
① Domain real-name authentication completed (and matches the filing entity)
② Prepare materials (entity ID, responsible person ID, contact info, verification photos)
③ Fill in information and submit via the接入 provider's filing system
④接入 provider preliminary review
⑤ SMS verification (responsible person's mobile number must reply within the specified time)
⑥ MIIT (管局) review
⑦ Obtain filing number → Display filing number and complete public security filingCommon Rejection Reasons Comparison Table
| # | Rejection Reason | How to Fix |
|---|---|---|
| 1 | Domain real-name entity does not match filing entity | Update domain real-name first, then submit filing |
| 2 | Domain real-name not completed | Complete real-name in domain console and wait for it to take effect |
| 3 | ID photo unclear, reflective, cropped, or obstructed | Retake photo: all four corners visible, no glare, original color copy |
| 4 | Website name contains sensitive words or is unrelated to the entity | Change to a name related to the entity/business |
| 5 | Website name contains terms like “China” or “National” | Remove unless you have the corresponding qualifications |
| 6 | Missing pre-approval | Education, healthcare, finance, news, publishing, etc., require prior approval from competent authorities |
| 7 | Responsible person’s mobile/email not verified | Complete SMS or email verification as required |
| 8 | Filing info does not match actual website content | Adjust website content or filing info to ensure consistency |
| 9 | Domain suffix not on the approved list | Switch to a supported suffix |
| 10 | Entity has abnormal filing records | Resolve historical filings (cancel or modify) first |
| 11 | Website name duplicates an existing filing | Change name, add entity-specific identifiers |
| 12 | Verification form signature/seal does not meet requirements | Resign and stamp according to the template |
The top three categories: Domain real-name mismatch (Item 1), non-compliant website names (Items 4, 5), and missing pre-approvals (Item 6). These account for the vast majority of rejections.
Material Checklist
- Entity ID (Enterprise: Business License; Individual: ID Card)
- Responsible person’s ID card (front and back)
- Responsible person’s mobile number and email (must be personally accessible)
- Domain certificate (proof of domain ownership)
- Verification photos (as required by接入 provider; some require backdrop photos or App facial recognition)
- Industries requiring pre-approval: Competent authority approval documents
Decision Tree
Rejected after submission
├─ Reason points to domain → Check if domain real-name matches filing entity
├─ Reason points to website name → Change name: remove sensitive words, link to entity
├─ Reason points to ID → Retake photos: original, clear, no glare, all corners visible
├─ Reason points to industry qualification → Confirm if pre-approval is needed, obtain it
├─ Reason points to responsible person → Confirm mobile/email verification is complete
└─ Reason is vague → Contact接入 provider customer service for specific rejection points, then fix accordinglyA note on the last point: When rejection reasons are vague, directly ask接入 provider customer service for the specific rejection points. This is much faster than guessing repeatedly.
Scenario Simulation: Same Submission Rejected Three Times
Phenomenon: A new domain’s filing submission was rejected three times consecutively. Each time something was changed, but the rejection reason looked the same, and the submitter couldn’t find any errors after repeatedly checking the form.
- Stop guessing based on intuition; view all three rejection comments together → Wording differed, but all pointed to the same direction: inconsistency in entity information.
- Compare character by character with original ID documents → Found that the filled entity name differed by one character from the official document (used an abbreviation), a difference easily missed by visual inspection.
- Continue checking the second layer: Domain real-name → The domain real-name entity did not match the filing application entity, which cannot be changed in the filing form.
- Rectify in the correct order → Go to the domain registrar to complete the real-name change and wait for the status to show “Success”.
- After real-name success, correct the filing form → Modify the name character by character to match the official document, then resubmit.
- Perform a full checklist review before resubmission → Don’t just check the rejected item; re-verify IDs, domain real-name, website name, and responsible person info as a whole to avoid a fourth rejection.
# Self-check list before filing submission (command-line verifiable parts)
# 1. Check where the domain currently resolves and if it points to the expected provider
dig +short example.com A
dig +short example.com NS
# 2. Confirm site accessibility (may vary in some regions before approval)
curl -sS -o /dev/null -w '%{http_code}n' https://example.com/
# 3. Domain real-name status must be confirmed in the domain registrar console; cannot be checked via command lineRoot Cause: Two independent inconsistencies叠加 (stacked)—the form used an abbreviation for the name, and the domain real-name entity differed from the filing entity. Each of the first three attempts only fixed one issue, so another condition remained unmet.
Two key takeaways:
- Treat rejection comments as a checklist, not a single point. If the same type of rejection occurs twice, it’s highly likely there are other unaddressed items. Fixing everything possible at once saves multiple cycles compared to fixing one by one.
- For “domain real-name mismatch,” you must fix the domain real-name, not the filing form. This is the most common mistake leading to repeated rejections due to fixing the wrong thing.
Pre-submission Self-Check List
Checking in order can prevent most rejections:
- Domain real-name authentication is complete, and the entity exactly matches the filing entity (most common rejection reason)
- Domain suffix is on the approved list
- IDs are valid; photos are taken of originals, clear, no glare, all corners visible
- Website name contains no sensitive words, no terms like “China”/”National” requiring qualifications, and is related to the entity’s business
- Website name does not duplicate existing filings
- Responsible person’s mobile and email are personally usable and can receive verification codes normally
- If the industry requires pre-approval (education, healthcare, finance, news, publishing, gaming, etc.), approval documents are obtained
- Filing info matches actual website content
- Entity has no abnormal records or historical filing issues
- Verification form signature/seal meets template requirements
Items 1 and 4 account for the vast majority of rejections. If time is tight, check these two first.
Complete Mapping from Rejection Reasons to Rectification Actions
| Rejection Reason | Specific Manifestation | Rectification Action | Verification Method |
|---|---|---|---|
| Entity Info Inconsistency | Difference between ID name and filled name | Verify character by character against original ID | Compare character by character with ID scan |
| Domain Real-Name Failed | Domain real-name status is not “Success” | Complete real-name at domain registrar first | Check domain real-name status is “Success” |
| Non-compliant Website Name | Contains brand terms, generic industry terms, or personal expressions | Change to neutral name related to the entity | Re-read against naming guidelines |
| Responsible Person Info Error | Incorrect mobile, email, or ID number | Verify each field and resubmit | Receive verification code on-site |
| Verification Form Issues | Unclear seal, missing signature, not original | Download the latest version of the verification form | Confirm it’s the current version and clear |
| Inconsistent Access Info | Actual接入 provider differs from reported | Report based on the actual service provider used | Confirm server ownership |
| Missing Pre-Approval | Content involves areas requiring pre-approval | Obtain corresponding approval first | Confirm approval document is valid |
The key to rectification is not just “changing” but “changing enough to pass”. If the same reason leads to two rejections, it’s usually because only the suspicious item was fixed. Rejection comments often contain multiple issues—fix every item listed before submitting, don’t just fix one at a time.
Final Check Before Submission
- ID Information: Name, number, validity period; verify character by character with the original ID, do not rely on memory.
- Domain Real-Name: Is the real-name entity the same as the filing entity? Is the status “Success”?
- Website Name: No brand terms or generic industry terms unrelated to the entity; no personal expressions.
- Responsible Person Contact: Mobile can receive verification codes normally; email is accessible.
- Verification Form: Use the current version, clear seal, complete signatures.
- Access Info: Consistent with the actual server ownership used.
Completing this check before submission prevents the vast majority of rejections. Only those truly requiring human judgment will enter the normal review cycle.
8 Common Pitfalls
- Rushing to file immediately after buying a domain: If domain real-name is incomplete or doesn’t match the entity, submission will definitely be rejected.
- Arbitrarily choosing a website name: Names like “XX China Net” without qualifications will be rejected; names unrelated to the entity will also be rejected.
- Ignoring industries requiring pre-approval: Education, healthcare, finance, news, publishing, gaming, etc., require prior approval from competent authorities; many are unaware of this rule.
- Entering wrong responsible person contact info or having someone else answer: If SMS verification isn’t received, the process gets stuck.
- Photocopying or reflecting ID photos: Must take photos of the original document.
- Not displaying the filing number after approval: The website footer must display the filing number linked to the MIIT system; this is a compliance requirement.
- Forgetting public security filing: After ICP filing approval, public security filing must be completed within the specified timeframe.
- Not updating entity info changes: After company name changes or responsible person changes, filing modifications must be made; otherwise, it will conflict with business registration.
Real Customer Feedback (From Cloud Market Similar Product Reviews and Consultations)
The following excerpts are from real buyer reviews and consultations for similar operations services on Alibaba Cloud / Tencent Cloud / Huawei Cloud marketplaces (providers include our store and peers, provided for reference only, not fictional tickets from this site):
10***47 2025-11-14 5.0 On-time delivery | Secure & reliable | Comprehensive features (User did not fill in comment content) 10***44 2022-09-16 5.0 Comprehensive features | Affordable price | Skilled technology Filing rectification, easy to use 10***44 2022-09-16 5.0 Skilled technology | Timely response | Affordable price Filing rectification, a useful service 10***67 2022-08-01 5.0 Patient & professional | Affordable price | On-time delivery Easy to use and affordable 10***54 2022-07-15 5.0 Comprehensive features | Affordable price | Secure & reliable Easy to use
10***07 2024-08-16 5.0 Comprehensive features | Affordable price | Skilled technology Essential for filing rectification 10***67 2024-08-15 5.0 Perfect after-sales | Timely response | Patient & professional Expert in handling filing issues 10***02 2023-06-09 5.0 Comprehensive features | Affordable price | Skilled technology Helped me, handled it promptly.
10***18 2024-08-07 5.0 Secure & reliable | Comprehensive features | Affordable price Professional 10***33 2024-07-31 5.0 Affordable price | Perfect after-sales | Timely response Useful 10***72 2024-07-11 5.0 On-time delivery | Affordable price | Skilled technology A merchant specializing in handling filing issues, highly recommended