CN domain — registrar and real-name, not ICP
A cn domain is a TLD and real-name gate, not an ICP shortcut. You can file ICP on .com. GoDaddy may sell a cn domain name; CNNIC real-name and an MIIT-approved registrar still bind.
A cn domain is a CNNIC country-code TLD — a registrar and real-name gate, not a substitute for ICP filing. You can file ICP on an approved gTLD such as .com. Buying .cn does not skip Mainland China hosting. GoDaddy and other global registrars may sell a cn domain name; CNNIC real-name plus an MIIT-approved registrar still bind before you register cn domain for China-facing publish.
What a cn domain actually is
Hard names this Decision Map uses — sibling to ICP filing — domain DNS and host in Mainland China:
- CN domain / .cn — China’s country-code TLD. CNNIC operates the national ccTLD family including .cn. The suffix is a registry name, not a Mainland China host SKU and not an ICP number.
- Anyone can often buy the string — Global registrars, including GoDaddy’s .cn help, state that applicants can register .cn. That cart does not finish China-facing publish.
- CNNIC real-name — Registration needs authentic identity of the holder (Internet Domain Name Regulations, Arts. 25 and 30; CNNIC national ccTLD rules). Until real-name passes, the name typically stays pending (GoDaddy real-name validation).
- MIIT-approved registrar — Confirm the current licensed list on the MIIT domain industry platform. An overseas brand on the invoice is not proof the name can enter an ICP submit.
- ICP is a different gate — Filing follows DNS that ends on Mainland China IPs, on .com or .cn. Buying .cn does not skip host in Mainland China or the ICP and PSB sequence.
- Common myth — “We must have a cn domain to launch in China.” You do not. A cn domain Godaddy checkout is not China-ready. Real-name, approved registrar, and ICP/host still sit downstream.
Vocabulary first. Next: what must be true before a .cn purchase is real work.
What must be true before you register a cn domain
Missing a clear suffix job stops your product team before a registrar cart is useful.
| Precondition | Why your process stalls |
|---|---|
| Job locked — brand needs the CNNIC ccTLD versus any MIIT-approved gTLD (for example .com) | A .cn sprint is staffed while .com plus ICP was the publish path — or the reverse |
| Honest trigger — China-facing publish versus “buy the string in case” | The name sits unused while hosting and filing never start |
| CNNIC real-name owner named — individual or organization documents that match the registrant | Checkout completes; the registry leaves the name pending |
| MIIT-approved registrar path — confirm on the current MIIT list, including after a global-registrar purchase | ICP console rejects the name; transfer starts in week twelve |
| Registrant = later filing entity | Passport real-name on .cn, company filing subject on ICP — reject or later false-information risk |
| Host / DNS plan independent of suffix | Teams treat .cn as in-country hosting and skip Mainland China termination |
Product teams usually cannot treat “register cn domain this sprint” as China launch. Suffix, registrar, and real-name are the floor. Filing still lives on the DNS path.
CN domain path — suffix, registrar, real-name
Stages are product decisions — not a registrar click-path.
| Stage | Decision / outcome |
|---|---|
| 1. Name the suffix job | Is .cn required for this launch, or will an approved gTLD (for example .com) carry the China-facing hostname? |
| 2. If no — keep the approved gTLD | Do not buy .cn as an ICP or hosting shortcut. Move to host + ICP when DNS will end in Mainland China |
| 3. If yes — register cn domain on rails that bind | CNNIC real-name with authentic documents; hold the name at an MIIT-approved registrar |
| 4. Align identity | Domain real-name subject = the entity that will hold ICP if you terminate in Mainland China |
| 5. Treat host as a separate chain | Buying .cn does not place origin in Mainland China. Hong Kong ≠ Mainland China |
| 6. File ICP when DNS ends in-country | Same duty on .com or .cn — see ICP filing — domain DNS |
| 7. After filing | PSB filing on the launch clock; keep registrar and IP change control owned |
Hard gate — is .cn required?
Necessity: confusing “we want a China-looking URL” with “we must use .cn to file or host” wastes the quarter.
| Job | .cn role | What must already be true |
|---|---|---|
| China-facing site on an approved gTLD | Not required | MIIT-approved suffix (commonly .com); registrar and real-name ready for ICP; host/DNS plan |
| Brand / ccTLD is the job | Plan A after gates | CNNIC real-name; MIIT-approved registrar; still ICP if DNS ends in Mainland China |
| “Buy .cn so we skip ICP” | Myth | Filing follows Mainland China DNS endpoints, not the ccTLD |
| “Point .cn at the overseas builder / PaaS” | Myth as launch | Suffix does not remap website builders, Heroku, or an enterprise CMS origin |
Why a cn domain does not skip ICP filing
Mixing suffix, registrar, and DNS is how teams miss the launch date with a paid name.
| Constraint | What breaks | What to do |
|---|---|---|
| Suffix ≠ filing trigger | Product reports “we bought .cn, China is unblocked.” ICP still follows DNS to Mainland China IPs. | Keep ICP filing — domain DNS as the obtain path. File on .com when that is the hostname. |
| Global registrar cart ≠ MIIT-approved registrar | A cn domain Godaddy (or other overseas) invoice exists; the filing console will not accept the name. | Confirm the registrar on domain.miit.gov.cn. Transfer before you promise a submit week. |
| CNNIC real-name ≠ ICP entity match | Passport-class real-name creates the name; the filing subject is a Chinese business-license holder. | Align registrant with the organizing entity before you submit ICP. |
| .cn ≠ Mainland China origin | Marketing treats the ccTLD as in-country hosting. Users still wait on an overseas origin. | Decide termination on host in Mainland China. Then file if DNS ends there. |
| Overseas-only .cn | The name exists; ordinary Mainland China users still fail the journey. | Name it as a capped architecture — not “China launched.” Reach design: website accessible in China. |
| Builder / PaaS left overseas | .cn CNAME to a stalled SaaS or PaaS host. | TLD choice does not move origin. Remap the host; do not restaff a suffix purchase. |
Approved gTLD + honest DNS → ICP can proceed without .cn. Filing does not demand the CNNIC ccTLD.
CNNIC real-name passed → the string can exist. It still does not place IPs, bind an access provider, or display an ICP number.
HQ laptop WHOIS → false confidence. A registrar dashboard that says “active” is not Mainland China vantage on the site those users must complete.
Where suffix and registrar work stalls
- Must-have-.cn thinking — Product treats the ccTLD as a geo toggle before registrar, real-name, and DNS are named.
- GoDaddy cart as Plan A — A cn domain Godaddy checkout is confused with an MIIT-approved registrar plus CNNIC real-name complete.
- ICP treated as a .cn tax — Filing is skipped on a real in-country .com, or demanded because someone bought .cn for an overseas-only site.
- Passport real-name, company filing — Identity rails were never the same subject.
- Hong Kong conflated with Mainland China — Regional hosting is reported as China launch behind a .cn badge.
- Builder or PaaS left in place — Website builders and overseas CMS/PaaS origins still stall after the suffix change.
- No owner for registrar transfer — The name sits at a registrar that cannot enter filing; nobody owns the move.
- No Mandarin / entity owner — Real-name packs, approved-registrar consoles, and ICP host bind sit on rails most global teams lack.
What “fixed” means: the suffix job is named (.cn required vs approved gTLD); CNNIC real-name is complete when .cn is the job; the registrar is MIIT-approved for any later ICP submit; registrant matches the filing entity; Mainland China DNS still has a complete filing when termination is in-country; residual overseas-only use of the name is named and capped. A paid cn domain name with a China marketing claim is not fixed.
China landing partner when CNNIC real-name stalls
Most product teams exploring Mainland China entry need a China landing partner once they stop treating a registrar cart as Plan A — to complete CNNIC real-name, place the name at an MIIT-approved registrar, match the registrant to the filing entity, and bind host plus ICP when DNS will end in Mainland China. Your team still owns whether .cn is required, which hostname ships, and which residual overseas line to keep; the partner path makes that suffix-and-registrar stack executable when those rails are not already in-house. Keeping a capped overseas site on .cn for outside-Mainland China viewers does not remove the need for that China landing partner on the primary China path.
What we can offer?
A cn domain for Mainland China is a suffix + registrar + real-name decision before any “buy .cn and we are live” sprint. Chinaready helps your product team keep an approved gTLD when that is the job — or complete CNNIC rails when the ccTLD is actually required:
- China Readiness Assessment — Decide whether .cn is required, whether a global-registrar cart can enter ICP submit, and whether filing is a go-live stall on the real DNS plan.
- China Access Acceleration — Keep China-facing pages reachable from Mainland China vantage after the hostname is honest — a suffix change does not repair an overseas origin.
- China Product Hosting — Place the origin where ICP adjacency and entity consistency stay coherent; buying .cn does not create in-country hosting.
- Mobile App Distribution — Align any China app domains and backends with the same registrar, real-name, and filing identity — not mistake a global .cn badge for a China store plan.
Contact us when you need the cn domain versus ICP fork decided before you staff another registrar checkout.
Frequently asked questions
Do we need a cn domain to launch in China?
No. A cn domain is not required to publish for Mainland China users. You can file ICP on an approved gTLD such as .com when DNS ends on Mainland China IPs. Buy .cn when the brand job is the CNNIC ccTLD — not as a substitute for hosting or filing.
Does a cn domain Godaddy purchase finish China publish?
No. GoDaddy and other global registrars may sell a cn domain name, but CNNIC real-name validation still has to pass, and China-facing ICP submit still needs an MIIT-approved registrar plus real-name match to the filing entity. A checkout is not go-live.
Does buying a cn domain name skip ICP filing?
No. ICP filing follows domain DNS that finally resolves to Mainland China IPs — the suffix is not the trigger. A .com on Mainland China termination still files. A .cn that never answers in Mainland China does not become an in-country launch. Depth lives in the ICP filing — domain DNS Guide.
What does it take to register cn domain for China-facing use?
Complete CNNIC real-name with authentic identity documents, hold the name at an MIIT-approved registrar (confirm the current list), and align the registrant with the later filing entity. Then treat hosting and ICP as a separate chain if public DNS will end in Mainland China.
Can product teams finish CNNIC real-name without Mainland China ops?
Usually no once the job is China-facing publish. Passport-class real-name can create the name; Mandarin registrar consoles, MIIT-approved transfer, entity match, and ICP host bind sit on rails most global teams lack. That is when a China landing partner becomes the realistic path.
