The official rules distinguish commercial internet information services, which require a licence, from non-commercial services, which use a filing system (Internet Information Services Administrative Measures). Suitable if your website and its access service are hosted only in Japan: you will typically not need an ICP filing for access through a mainland server that you do not use. That does not remove content, licensing, or other legal duties. Recheck the position if you add mainland hosting or change how users reach the site.
Who should read this: Cross-border e-commerce teams planning a Japan-hosted storefront.
SaaS and content teams serving users in Japan or elsewhere in East Asia.
Site owners comparing a Japan dedicated server with shared hosting or a VPS.
Does a Japan server need ICP filing?
Focus on the website’s actual hosting and access arrangements, not only its domain registrar or the country where the company is registered. A Japan-only origin and application backend, with no mainland server providing access to that website, will typically not require an ICP filing for mainland server access. This is a limited conclusion about that access arrangement, not a blanket legal exemption.
MIIT’s rules and filing guidance describe China’s filing framework and the information collected for it (MIIT filing measure, MIIT filing form instructions). Local communications administration guidance also addresses website filing information and verification (Jiangxi communications administration FAQ, Zhejiang communications administration FAQ). Read those materials alongside the actual architecture. Do not treat the location of the origin server as the only fact that matters.
| Deployment arrangement | How to assess the filing question | What to verify |
|---|---|---|
| Website and application hosted in Japan, with no mainland hosting or mainland access service for the site | Typically no ICP filing for access through a mainland server that is not used | Confirm the origin, application backend, and access services are actually outside mainland China |
| Japan origin with a mainland CDN, proxy, or other mainland access component | Do not conclude that the site is exempt based on the Japan origin alone | Ask the provider which locations and services are used, then check the applicable filing requirements |
| Website or application later moved to mainland hosting | Reassess before making the new arrangement available | Confirm the provider’s requirements and the rules for the service type |
| Domain registered outside mainland China, but website hosted or accessed through mainland infrastructure | Domain registration alone does not settle the filing question | Identify the hosting and access providers and their locations |
The table is a screening tool, not a regulator’s ruling. If a provider’s service arrangement or the relevant rules are unclear, confirm them with the provider and the competent authority before launch.
Does a site on overseas hosting operate without filing?
It may be technically accessible without an ICP filing for mainland server access when the site uses only overseas hosting and does not use a mainland server to provide access to that website. But “accessible” and “legally compliant” are different tests. A site’s content, business model, handling of personal information, and any sector-specific rules can create separate obligations.
The MIIT’s filing guidance explains the filing process and the information requested in an application (MIIT non-commercial internet information service filing guide). It does not turn overseas hosting into permission to publish any material or run any business. If your site offers paid services, handles regulated information, or operates in a regulated sector, assess those issues separately.
Can a Japan-hosted site need filing if it targets mainland users?
The intended audience is not, by itself, enough to establish which filing rules apply. A site can target mainland users while its origin and application backend remain in Japan. The key practical question is whether a mainland server or access service is also used to deliver that website.
Check the whole path, not just the server shown in a hosting account. A mainland CDN point of presence, proxy, hosted API, or other service may change the arrangement. Ask the service provider where the relevant components run and whether its service requires an ICP filing before it serves the site from mainland infrastructure. Do not assume that the provider has completed every filing step on your behalf.
Keep these terms distinct:
| Requirement | What it relates to | What it does not establish |
|---|---|---|
| ICP filing for a non-commercial internet information service | A filing requirement under the applicable internet information service rules | That the site’s content or operations satisfy every other law |
| Commercial internet information service licensing | A licence regime described in the Internet Information Services Administrative Measures | That every paid website automatically falls into the same category |
| Other legal or sector-specific duties | The nature of the service, content, users, and data involved | That overseas hosting removes those duties |
The official measures distinguish non-commercial filing from commercial licensing, but whether a specific business falls into a category depends on its actual service and applicable rules (Internet Information Services Administrative Measures). If classification affects your launch, get advice from the competent authority or a qualified lawyer. Do not infer your licensing position from the hosting location alone.
What changes if you add mainland hosting later?
Treat a move to mainland hosting, or the addition of a mainland access layer, as a fresh compliance review. The earlier conclusion was tied to the earlier architecture. It should not be carried forward automatically after a change.
Before making the change, identify the proposed provider, the locations where its services will run, and which site functions it will deliver. Then ask the provider what filing or other steps apply to your service. MIIT’s government guidance describes non-commercial internet information service filing, but your provider and the competent authority should confirm how the current rules apply to your specific setup (MIIT government filing guidance).
Build that review into the migration plan rather than leaving it until DNS changes or public launch. Keep a record of the old and new architecture, provider responses, and any filing or licensing decisions. If you later remove a mainland component, review the arrangement again instead of assuming the previous decision still applies.
Use this deployment checklist before launch
Use the checklist to document what is deployed today. Repeat it whenever you change hosting, add a CDN or proxy, move an application backend, or introduce a new service provider.
- [ ] Draw the request path from the user to the website. Include the origin server, application backend, proxy, CDN, and any hosted API that serves the site.
- [ ] Record the actual location of each component and the provider responsible for it.
- [ ] Confirm whether any mainland server or mainland access service is used for this website. Do not rely only on the origin server’s location.
- [ ] Write down the site’s intended markets and the services it provides, including whether users pay for a service.
- [ ] Check the applicable MIIT rules and current communications administration guidance. Ask providers about filing requirements for the services they supply.
- [ ] Separate the ICP filing review from content rules, commercial licensing, privacy obligations, and any sector-specific requirements.
- [ ] Add a compliance review to the change plan before introducing mainland hosting or a mainland access component.
- [ ] Keep dated architecture notes and provider confirmations so the basis for the decision can be checked after a future change.
Check that the hosting location matches the deployment plan
For a Japan-only setup, confirm that the website origin and application services are actually placed in Japan, and document any third-party components that affect how users reach them. A location listed for one server does not confirm the location of every service in the request path.
XFP Cloud lists its server location as Japan, Tokyo. That is a hosting-location fact to verify against your deployment plan, not a promise about filing outcomes, legal compliance, or mainland access performance. You can review the XFP Cloud server information and confirm available operating-system choices on the server configuration page. Product information can help you check deployment conditions; it is not legal advice.
Separate filing from the rest of your compliance review
ICP filing is not a general-purpose approval for a website. It does not decide whether a site’s material is lawful, whether a commercial service needs a licence, or whether personal information and industry-specific requirements are being handled correctly. Likewise, a Japan server does not automatically make a business compliant simply because it may not need a filing for mainland server access.
If you store or process information about users in Japan, assess the rules that apply to that data and business activity separately. If you serve customers in mainland China, assess the content and service obligations that apply to that audience as well. The right answer depends on the service, the data, the infrastructure, and current rules—not just the server’s location.
For a site that remains entirely on Japan hosting, a dedicated server may be appropriate when shared hosting or a VPS no longer gives the team the control it needs over the operating system, application stack, or resource allocation. Those shared options can still make sense for a small site, a short-lived test, or a workload with little demand. A dedicated server does not solve a filing question, and it does not remove the need to review third-party access services.
When a shared plan or VPS makes it difficult to control the full deployment or understand which components serve the site, first map those components and verify their locations. If the requirement is sustained, dedicated capacity with a clearly documented Japan hosting location may fit better. Review XFP Cloud’s Japan server details against the architecture you have confirmed, then complete the filing and legal review separately; the product information describes hosting conditions, not a compliance determination. For legal questions, follow the latest requirements from the competent authority and consult a qualified lawyer where needed.
Build Your Tokyo Dedicated Server with XFP Cloud
Run your workloads on an entire AMD EPYC 7543P physical server in Tokyo, not a shared cloud slice.
From $455 / month