How to Renew an ICP Filing (and What Happens If It Lapses)

Quick answer
An ICP filing has no single renewal date. It remains valid as long as the domain, the filing entity, and the mainland hosting account stay consistent.
Hosting providers re-verify filings periodically and will suspend the domain if the information no longer matches.
Any change of domain owner, company name, legal representative, or hosting provider requires an update to the filing.
Losing the filing takes the site offline for mainland users: the provider blocks the domain until a new filing is approved.
Re-filing from scratch is slower than keeping the existing one in good order, which is why the information matters more than the deadline.

How does ICP filing renewal work?

It is maintenance rather than renewal. The filing was approved for a specific entity, domain, and hosting provider, and it stays effective while those remain true. What the provider does on a schedule is re-verify: they check that the domain is still registered to the filing entity, that the entity still exists and is in good standing, and that the site still matches the declared nature. If everything matches, the filing continues and nothing is issued or paid.

In practice each hosting provider runs its own verification cycle, and the filing system records the relationship between domain and provider. That means two things you must keep current: the domain registration details and the entity’s corporate records. A company that renames itself, changes its legal representative, or lets a related registration lapse will eventually fail verification without any obvious trigger.

What has to be updated, and when

Update the filing when any of these change: the domain owner or registrar, the company name or legal representative, the hosting provider or the server’s province, or the nature of the site. Transfers of hosting between providers are the most common case, and they are where filings are most often lost — the new provider has to re-submit under its own account, and the old relationship ends.

If the domain is transferred between registrars the filing can survive, provided the registrant entity is unchanged, but confirm that with the provider rather than assuming. Treat every structural change as something that triggers a filing update and put it on the migration checklist next to the DNS changes.

Trigger a filing update when ANY of these change:
  [ ] Domain registrant entity
  [ ] Registrar or the domain's registration record
  [ ] Company name / legal representative
  [ ] Hosting provider
  [ ] Server province
  [ ] Site name or the nature of the service

Each hosting provider runs its own re-verification; keep contact details current
so the notice reaches a human who can act on it.

What happens if a filing lapses

The short version is access is withdrawn. The mainland hosting provider blocks the domain from being served, usually without warning beyond a notification to the account contact, and restores it only after a valid filing is in place again. Monitoring that runs from outside the mainland will show DNS resolving but requests failing, which is a confusing signal if nobody has connected it to the filing.

Recovering is slower than maintaining. A new filing goes through the same review as the first one, so the site can be down for weeks. If the lapse also involved a failed entity — a deregistered subsidiary, for instance — the recovery path may run through corporate restoration first. This is the argument for treating the filing as part of the production runbook, not as a one-off launch task.

Keeping a filing healthy

Assign one owner in the company for the filing and record which domain, entity, and provider it is attached to. Keep the registered contact details working — a filing whose verification email goes to a departed employee is a filing that will lapse. Put the filing number and its renewal relationship into the same inventory that holds your domain expiry dates, because they fail in the same way and are noticed at the same inconvenient time.

When you change hosting or corporate details, do the filing update in the same change window as the technical migration. Doing it separately guarantees that one of the two is forgotten. A short checklist in the runbook turns a rare but sharp outage into a routine step.

Where this bites vibecoders
This is exactly the class of operational work an AI assistant never generates, because there is no code artifact to produce. A migration plan from an assistant will cover DNS cuts, database moves, and rollback; it will not mention that moving the hosting provider invalidates a compliance registration attached to the old one. If the project has a mainland filing, add it to the deploy checklist by hand — the assistant cannot see that dependency in the repository.

Where AI coding assistants get this wrong

Describing the filing as something with a renewal date rather than as ongoing verification.
Omitting the filing from migration runbooks when hosting providers change.
Assuming a domain transfer is fine without confirming the registrant entity is unchanged.
Leaving the account contact as a personal email that nobody monitors.
Treating a lapsed filing as a quick re-submission rather than a multi-week outage.
Not recording which domain, entity, and province the filing is attached to.

Checklist

Name one owner for the filing and record their contact details in the account.
Inventory the filing with its domain, entity, provider, and province.
Add a filing update step to every hosting migration runbook.
Notify the provider before changing the registrant or the company name.
Watch for provider verification notices and act in the window given.
Test that the site still serves from inside mainland China after any change.

FAQ

Does an ICP filing need to be renewed every year?

There is no annual renewal in the way a certificate or a licence has one. The filing is re-verified by the hosting provider, and it remains valid while the entity, domain, and hosting relationship stay consistent. You act when something changes, not on a fixed anniversary, though keeping the account details current is what makes verification pass.

What happens if my ICP filing expires?

The mainland provider blocks the domain from being served, so the site becomes unavailable to users inside China while continuing to resolve in DNS. Restoring it means submitting a valid filing again and waiting through review, which can take weeks. Keeping the filing details accurate is far cheaper than recovering one.

Do I need to re-file if I change hosting providers?

Yes, in practice. The filing is linked to the provider and province, so a new provider submits a fresh filing under its own account. Plan it as part of the migration, not after it, and expect a window where the site is not served from inside the mainland. Changing registrars without changing the registrant entity is usually safer, but confirm with the provider.

Can I keep a filing if the company is sold or renamed?

The filing follows the legal entity and its recorded details, so a change of company name or legal representative requires an update. A sale that moves the domain to a different entity means a new filing for that entity. Leaving stale corporate details in place is the most common way filings fail verification months later.