Real-Name Registration vs. an ICP License: Which One Actually Applies to Your China-Facing Service?
Ask three people whether Chinese internet regulation applies to your foreign-hosted service and you’ll get three answers, usually because they’re each thinking of a different rule. Real-name registration and ICP licensing come up in the same conversations, often in the same sentence, as though they were one requirement with two names.
They aren’t. They govern different things, attach to different parties, and are triggered by different decisions. One is about verifying who your users are. The other is about whether you’re allowed to serve a site from inside mainland China at all.
Getting the distinction right matters because it changes the answer to the only question most businesses actually care about: does any of this reach a server in Tokyo or Singapore that happens to have Chinese visitors.
The short version
| Real-name registration | ICP filing (备案) | Commercial ICP license (ICP证) | |
|---|---|---|---|
| What it governs | Verifying the real identity of users | Permission to serve a site from mainland infrastructure | Permission to run a revenue-generating online service |
| Who carries the obligation | The platform or operator signing up users | The site operator, gatekept by the hosting provider | The site operator |
| Entity required | Not applicable, it’s an operator duty | A mainland-registered entity; a wholly foreign-owned one qualifies | Generally a Chinese company, or a joint venture with no more than 50% foreign ownership |
| What triggers it | Operating a domestic service that has users | Hosting on mainland Chinese infrastructure | Charging users for online services |
| Reaches a foreign-hosted server? | Not directly | No, and you can’t obtain one | No |
What real-name registration actually is
Real-name registration is China’s requirement that users of domestic internet services be identified with verified real-world identity, typically a national ID number or a mobile number already tied to one. It covers mobile SIM cards, accounts on domestic platforms like WeChat and Weibo, apps distributed through Chinese app stores, and domestic hosting accounts.
It’s rooted in China’s Cybersecurity Law, whose Article 24 requires network operators to obtain real identity information when signing service agreements with users, and to refuse service where that information isn’t provided. Enforcement runs through the platforms and telecom carriers themselves, which are the parties held responsible.
The key structural point is that it’s an obligation on the operator of a domestic service, not a rule that attaches to users wherever they happen to browse. It has tightened steadily rather than loosened, so if you’re planning multi-year, assume more verification rather than less.
What ICP filing and an ICP license actually are
ICP is where most of the confusion lives, partly because there are two distinct things sharing the abbreviation.
An ICP filing, usually called by its Chinese name beian, is the registration required for any site served from mainland Chinese infrastructure. It’s free, and it requires a mainland-registered entity, though a wholly foreign-owned enterprise generally qualifies. Enforcement is delegated to the hosting providers: a mainland host is required to verify your filing before serving your site, and to suspend sites that lack one.
A commercial ICP license, the ICP证, sits on top of that and is required when the service generates revenue online rather than simply publishing information. It involves substantive review rather than a registration formality, takes considerably longer, and carries an ownership constraint covered below that catches a lot of foreign businesses off guard.
The trigger for both is infrastructure, not audience. Filing is tied to hosting on mainland servers, which is why a site hosted in Tokyo, Singapore, or Hong Kong doesn’t need one. It’s worth being precise here: such a site isn’t merely exempt, it generally can’t obtain a filing at all, because the filing presupposes mainland hosting.
How the two connect
Here’s the relationship that makes the comparison useful rather than academic: the ICP path is what converts real-name obligations from something you inherit to something you carry.
A foreign-hosted business encounters real-name verification indirectly, through the platforms it builds on. Offer WeChat login and you’re consuming an identity system that already performed verification, bound by WeChat’s terms about what you do with the result. Use a China-based SMS gateway, accept Alipay or WeChat Pay, or distribute through a Chinese app store, and each of those relationships brings its own filing and identity expectations. Your compliance surface tracks your integrations, not your server location.
Take an ICP filing and a mainland entity, and the position changes in kind rather than degree. You’re now a domestic operator inside the regulatory perimeter, where the identity framework applies to you directly, alongside content responsibilities and ongoing filing duties that an offshore service never touches. That’s the real reason ICP is a strategic decision rather than a procedural step.
The ownership constraint that decides it for many businesses
The commercial ICP license carries a restriction that reframes the whole question for foreign companies: it’s generally limited to wholly Chinese companies or joint ventures with no more than 50% foreign ownership.
For a foreign-majority business, that means the commercial license usually isn’t a matter of budget or patience. It requires restructuring, typically a joint venture with a Chinese partner holding at least half the equity, which is a corporate decision rather than a compliance task.
This is why the practical comparison for most foreign businesses isn’t “real-name registration or ICP license.” It’s “operate offshore and reach China over optimized routing, or restructure the company to operate inside it.” Framed that way, the latency conversation that usually dominates these discussions turns out to be the smaller half of the decision.
Which question you’re actually answering
If your infrastructure sits outside mainland China, neither ICP requirement applies to you, and real-name registration reaches you only through the domestic platforms you’ve chosen to integrate with. The hosting and routing layer is a network decision. A VPS in Tokyo or Singapore reaching mainland users over CTGNet, CUP, or CMIN2 doesn’t make you a domestic operator, and choosing a premium carrier path doesn’t move you one step closer to the licensing regime.
One caveat worth raising with a partner rather than assuming: if you add mainland CDN or cloud capacity to an offshore deployment, you’ve introduced mainland infrastructure into the picture, and the filing question deserves a direct answer from that provider rather than an inference from your own setup.
Beyond that, the useful exercise is listing the domestic Chinese services you actually depend on, payment processors, login providers, SMS gateways, app store distribution, CDN partners, and getting advice on that list. “Does Chinese internet law apply to us” has no useful answer. “What do we take on by using this payment processor and this SMS gateway, with no Chinese entity” has a real one, and a China-focused advisor can usually give it quickly.
Wrapping up
Real-name registration governs identity verification by operators of domestic services. ICP filing governs whether you may serve a site from mainland infrastructure at all, and the commercial license governs whether you may charge for it. They’re separate rules, and only the ICP path pulls a business into the perimeter where the identity rules apply to it directly.
For a foreign-hosted service, the honest summary is that neither applies to your server, and the exposure you do have arrives through the domestic platforms you’ve integrated with. If the ICP route is ever genuinely on the table, the ownership constraint on the commercial license is the detail to check first, because it decides the question more often than latency does.
Thanks for reading! Whether you’re weighing a mainland presence or planning to serve China from outside it, knowing which of these two rules actually applies to you is what keeps the decision straightforward. If you’re looking for China routing you can verify yourself rather than take on faith, Riven Cloud runs KVM VPS in Tokyo and Singapore with all three named premium paths on every plan: CTGNet on China Telecom, CUP on China Unicom, and CMIN2 on China Mobile, each testable through a public Looking Glass before you buy.
Ready to see the numbers for your own traffic? Deploy a server or contact our team with questions.
Frequently asked questions about real-name registration and ICP licensing
What’s the core difference between real-name registration and an ICP license?
Real-name registration governs verifying the identity of users on a domestic service. ICP filing and licensing govern whether you’re permitted to serve a site from mainland infrastructure, and whether you may charge for it. Different obligations, different triggering conditions.
Does my foreign-hosted server need an ICP filing to reach Chinese users?
No. The filing is tied to hosting on mainland Chinese infrastructure rather than to your audience, so a site hosted in Tokyo or Singapore doesn’t need one and generally can’t obtain one either.
Does real-name registration apply to my foreign-hosted service directly?
No. It attaches to operators of domestic services under Chinese jurisdiction. Where it reaches a foreign business, it’s through the terms of domestic platforms you’ve integrated with, such as WeChat login or a China-based SMS gateway.
What’s the difference between an ICP filing and a commercial ICP license?
The filing is a free registration required for any mainland-hosted site, and a wholly foreign-owned entity can generally obtain it. The commercial license is an additional approval for revenue-generating online services, involving substantive review and a much longer timeline.
Can a foreign-owned company get a commercial ICP license?
Usually not on its own. The commercial license is generally limited to Chinese companies or joint ventures where foreign ownership doesn’t exceed 50%, so it typically requires restructuring rather than just an application.
Does adding a mainland CDN to an offshore setup change anything?
Potentially, because you’ve introduced mainland infrastructure into the delivery path. It’s worth putting that question directly to the CDN provider rather than assuming your offshore hosting settles it.
Should I get advice on my specific integrations?
Yes, and it’s far more productive than the general question. List the domestic services you depend on, payment, login, SMS, app store, CDN, and ask about that list, since obligations vary by platform rather than applying uniformly.
Share