Many digital projects treat filing as a "last-mile formality" and get blocked at campaign or launch time. In reality, domain planning and ICP filing should start with project kickoff. This guide gives executable compliance paths for IT and marketing leaders.
1. How to Plan the Domain System
Separate at minimum: main brand domain, campaign/short domains, API or static asset domains, test domains. Main domain for site and trust; short domains for campaigns with abuse controls; static assets on CDN; test domains must not point to production data. Avoid obscure names—easy for verbal and print use.
1.1 Real-Name and Ownership
Domain real-name entity should align with business license and filing entity to reduce transfer and filing changes. Enable registry lock and DNSSEC where supported; avoid shared super-admin accounts on registrar panels.
2. ICP Filing Key Steps
- Confirm provider and server in a filable region.
- Prepare entity documents, site owner ID, authorization, domain certificate.
- Submit initial review at provider; complete curtain or online verification.
- After telecom approval, display filing number and keep site accessible.
Provincial review varies—photo clarity, site completeness, owner phone reachability affect timing. Buffer 2–4 weeks; urgent projects should parallel-track from day one.
3. Frequent Rejections and Fixes
| Issue | Typical Sign | Fix |
|---|---|---|
| Entity mismatch | Domain owner ≠ license | Transfer or change entity first |
| Incomplete content | Site down or placeholder only | Launch basic compliant pages |
| Wrong category | Business ≠ declared service | Select true service category |
| Owner unreachable | Verification call missed | Dedicated contact, phone on |
Unfiled domains cannot serve websites in mainland China. Overseas hosting to avoid filing often hits compliance lines in ads, payment, and enterprise acceptance—legal should assess.
4. Ongoing Compliance After Filing
Filing is not one-time. Site name, owner, provider changes may need filing updates; shutdown should cancel filing to avoid legacy risk. Sync public security filing per local rules. Multi-site groups need a domain/filing ledger: expiry, entity, DNS, certs, owners—prevent loss when staff turnover.
5. Coordinating with Business Launch
Campaigns, ads, mini program H5 jumps depend on accessible compliant domains. Project plans should gate on "domain ready / filing passed / HTTPS valid." XYN Technology embeds filing milestones in delivery to avoid "dev done but cannot publish."
6. Filing Sync and Campaign Timing
Filing cycles clash with campaigns. Day-1 tasks: domain real-name, entity docs, owner verification parallel with UI design. One cross-border e-commerce site missed Black Friday two weeks—overseas domain holder caused rejection; fixed via entity change and authorization.
Group multi-brand ledger: registrar, expiry, DNS, cert policy, filing number, owner. Subdirectory/subdomain campaigns: confirm new filing vs extend existing service description.
6.1 Certificates, DNS, Security
Auto-renew HTTPS with expiry alerts; dual review on DNS changes. Registry 2FA; CDN/WAF filing entity must match provider. Public forms/login: captcha, rate limit, geo anomaly—not filing alone.
7. Cross-Border Team Template
HQ IT and China entity share one filing milestone sheet: transfer, authorization, owner real-name, provider review, regulator feedback. Weekly three items: blockers, owner, deadline. One consumer group cut average filing from 38 to 22 days.
Overseas CDN/mail: filing entity vs DNS consistency; legal reviews privacy vs actual fields.
Pre-event drill: DNS switch, certs, origin load, filing display; rollback to static compliant page within hours if needed.
8. Linking to Business Systems
After filing, DNS cutover must check mail, payment, OAuth callbacks—main site up but OAuth on old domain is a hidden failure. Change in low-traffic windows; notify support and ops.
Multi-legal-entity groups: each ICP number correct in footer—mobile and desktop spot checks.
Auto-renew domains with multi-level alerts—expiry can take filing display offline.
Provider change, entity migration, category adjustment: semi-annual filing self-audit; footer, in-app about, and regulator records aligned. CDN sites: verify filing IP and origin after changes.