What the primary sources say
| Fact | Primary source |
|---|---|
| The MIIT ICP filing itself carries no government fee. Cost comes from everything around it, not from the filing. | MIIT — ICP/IP address/domain name information filing management system |
| A filing that genuinely exists is queryable in the MIIT public record. Expired filings still return a record; a filing that returns nothing was never made. | MIIT public record query |
| The filing is triggered by server location, requires a mainland legal entity, and is bound to the access provider — not only to the domain. | State Council Decree No. 292, Administrative Measures on Internet Information Services |
Sources verified by the 21YunBox China engineering team on 2026-08-27.
TL;DR — An ICP filing is a legal permission, not a performance feature. Filing a site does not make it load faster, and anyone who tells you otherwise is selling the wrong thing. But the reverse is not symmetrical: in mainland China, the only delivery path that removes the cross-border round trip is delivery from inside the mainland, and delivery from inside the mainland is precisely the event that triggers the filing requirement. So compliance does not buy speed — and the fastest available path cannot be bought without it.
The concession first, because it is true
If your site is slow in mainland China and someone tells you an ICP filing will fix it, that advice is wrong. Getting filed does not change your DNS, does not move your servers, does not replace a font host that never answers, and does not shorten a single network path. A filed site with an offshore origin is exactly as slow as an unfiled site with an offshore origin.
It is worth being blunt about this because the confusion runs in both directions and both directions cost money. Teams buy filings expecting a speed improvement and get none. Other teams postpone the filing conversation because they have been told it is “just paperwork,” and then discover at launch that the arrangement they have built has no legal basis.
Compliance is about permission. Performance is about paths. They are different questions with different answers.
But they meet at exactly one point
Here is the part that gets left out when the two are separated too cleanly.
There are three ways to deliver a site into mainland China. Only three:
| Path | Where the request ends | Cross-border round trip | ICP filing |
|---|---|---|---|
| Offshore origin | Outside China | Full — every request crosses a congested, filtered border | Not required |
| Nearshore edge (Hong Kong, Singapore) | Outside the mainland | Shortened, not removed | Not required |
| In-China delivery | Inside the mainland | Removed | Required |
Now read the middle row and the bottom row together, because that is where the whole decision lives.
The nearshore option is exempt from filing for exactly the reason it cannot close the performance gap: it never enters China. A node in Hong Kong or Singapore moves the endpoint of the cross-border trip closer to your users. It does not remove the trip, because the traffic still has to cross into the mainland to reach them. The exemption and the ceiling are not two facts about nearshore delivery. They are one fact, described twice.
And the bottom row inverts it. Removing the round trip means the response originates inside mainland China. Originating inside mainland China is the event that triggers the filing requirement. There is no version of “served from inside China” that is also “outside the scope of the filing rules.”
So the interlock is this: any arrangement that avoids the filing has, by construction, kept the latency. Not as a matter of policy or vendor preference — as a matter of where the packets go.
What this means when you are choosing
The practical consequence is that “how fast can we be in China” and “what are we allowed to do in China” are not two procurement tracks that can run independently and meet at the end. They are one decision with three options, and each option prices both axes at once.
- If you choose the offshore origin, you have chosen no filing and full latency.
- If you choose nearshore, you have chosen no filing and reduced-but-permanent latency.
- If you choose in-China delivery, you have chosen the filing and no cross-border round trip.
You can pick any of the three. What you cannot do is pick the third row’s performance with the second row’s paperwork.
The other half of a bad China score
While we are separating things that get conflated: a poor result from inside China usually has two independent causes, and only one of them is about distance.
| Cause | What it looks like | Does moving delivery closer help? |
|---|---|---|
| Distance and congestion | Everything loads, slowly. High time-to-first-byte, long tail on every request. | Yes. This is what shorter paths are for. |
| Unreachable dependencies | Page shell arrives, then stalls. Individual third-party hosts never respond at all. | No. |
The second row deserves emphasis because it is the one people try to solve with the wrong tool. A CDN makes a reachable host closer. It cannot make an unreachable host answer. If your page requests a font, a tag manager, an analytics endpoint, a video player or a map API on a domain that is filtered at the border, caching that request elsewhere changes nothing — the browser still asks the original host, and the original host still does not reply. Blocked dependencies have to be replaced, or rewritten to a same-origin path that is served from inside China — which is what the 21YunBox Optimizer does. They cannot be accelerated.
You can see which of your own dependencies fall into that category with our China firewall test, and what a Lighthouse audit reports from inside the mainland with our China speed test — Google PageSpeed Insights audits from infrastructure that cannot reach China at all, so its score describes a path no Chinese visitor takes.
Three properties of ICP filing that catch teams late
Most teams meet these after they have already committed to an architecture, which is the expensive order to meet them in.
-
It is triggered by server location, not by company nationality. The question is not where your business is registered. It is where the response comes from. A foreign company serving from inside mainland China needs a filing; a Chinese company serving from Singapore does not.
-
It requires a mainland legal entity. The filing is made in the name of a domestic entity, which is why “we have no Chinese subsidiary and are not planning one” is a real architectural constraint rather than a paperwork inconvenience.
-
It is bound to the access provider, not only to the domain. Change hosting or delivery provider without updating the record and the filing goes stale. Records left stale get classified as dormant and can be cancelled — at which point the site is not slow, it is off.
The Ministry of Industry and Information Technology publishes the record itself, and it is worth checking rather than assuming: any filing that genuinely exists is queryable at beian.miit.gov.cn. Expired filings still return a record. A filing that returns nothing was never made. The MIIT filing itself carries no government fee — what varies is everything around it, which we break down in what it actually costs to host a website in China.
What compliance does not buy you
To close the loop honestly, the filing is not a performance product and should not be sold as one. It does not:
- make an offshore origin faster,
- unblock a third-party dependency,
- improve your Core Web Vitals,
- or guarantee that your site works well once it is legal.
What it buys is the right to serve from inside mainland China — and serving from inside mainland China is the only thing that removes the border from the request path. That is the entire relationship, and it runs in one direction only.
If you want the full comparison of delivery options against both axes, it is laid out in CDN or 21YunBox: which one do you need for China. If you want the filing explained on its own terms, start with the China ICP license guide.
