What to do when the .top registry puts your domain on ServerHold

Four days after javranking.top went live, it suddenly began returning NXDOMAIN. WHOIS showed serverHold, and my registrar later confirmed that the .top registry had stopped the domain from resolving.

Between 8 and 11 September, I sent three emails to [email protected]. The registry eventually removed the ServerHold. I have kept the full correspondence out of the article so the main story remains readable; a complete redacted record is linked at the end.

First, make the registry state its case

My first email had one purpose: require the registry to explain the reason for the suspension, the supporting evidence, any case reference, the policy basis, and the appeal process.

The registry replied with two words: Pornography locking.

That was not a meaningful explanation, but it did establish that the action concerned website content rather than malware, phishing, botnets, or another form of DNS Abuse.

My second email focused on that distinction. I asked the registry to identify the exact policy, applicable law, source of the report, affected content, and appeal procedure. I also asked why a ServerHold affecting resolution worldwide was considered necessary. I pointed out that adult content is not part of ICANN’s definition of DNS Abuse and said I would send the correspondence to ICANN Contractual Compliance if the registry still refused to provide a reasoned response.

The registry then acknowledged that adult content is not DNS Abuse under ICANN’s definition. It argued, however, that because it provides domain services from within mainland China, it must comply with mainland Chinese content restrictions.

That response mattered. The dispute was no longer about an undefined allegation of “abuse”. The question had become whether a registry could enforce a domestic content restriction by disabling a domain across the global DNS.

Do not argue about the content; challenge the measure

My third email did not continue debating whether adult content should be legal. I said clearly that I did not object to competent Chinese authorities preventing users inside mainland China from accessing the site.

But restricting access inside mainland China is not the same as applying a global ServerHold. A ServerHold removes the domain’s delegation from the global .top DNS zone, so users outside mainland China lose access as well.

I had registered the domain through an overseas registrar. The site was hosted and operated outside mainland China and intended for an international audience. At the time of purchase, I had not seen any clear notice that violating mainland Chinese content rules could cause the domain to be removed from the DNS worldwide. The registry also gave me no warning, notice, or opportunity to respond before applying the hold.

I therefore did not ask the registry to change its policy inside mainland China. I asked it to remove the ServerHold and restore normal global DNS delegation.

If it refused, I asked for a written decision confirming four points: whether .top applies mainland Chinese content restrictions to domains worldwide; whether it considers itself entitled to disable services operated overseas; whether that worldwide restriction was clearly disclosed before purchase; and whether no geographically limited measure or formal appeal process was available. I also stated that I would use the final decision as evidence in an ICANN complaint.

The registry did not answer those four questions. Its next email simply said that the domain had been unlocked.

What actually helped

Do not start by arguing with the label the registry gives you. First require it to classify the issue: is it DNS Abuse, a content-policy violation, or something else? Then ask for the exact basis.

Do not let the discussion collapse into a debate about whether a particular country should prohibit particular content. You can accept the registry’s position on access inside that country while still asking why the measure must disable DNS resolution worldwide.

Do not send a general complaint. Every email should ask for a concrete outcome: remove ServerHold and restore global DNS delegation.

If the registry refuses, ask for a formal written decision and list the specific points it must confirm. An ambiguous reply is easy to hide behind. A written position that can be reviewed by a registrar or ICANN is harder to avoid.

What to consider before registering a .top domain

The main lesson was not how to write a forceful appeal. It was that choosing a domain requires looking beyond the registrar. A registrar sells and manages the registration, but the registry controls the TLD zone.

If your site may trigger mainland Chinese content restrictions, you should think carefully before using a TLD operated by an organisation based there. Living overseas, hosting overseas, and buying through an overseas registrar do not change the fact that the registry controls whether the domain remains delegated globally. Domestic regulatory pressure can reach the registry, while the registrant carries the operational risk.

In my case, the sequence was: no prior notice; a global hold first; an explanation only after I discovered the failure and asked; and removal of the hold after repeated objections and a stated intention to escalate to ICANN.

I cannot prove that this sequence reflects a formal internal .top policy. From a registrant’s perspective, however, the practical result was “suspend first, review only when challenged”.

For adult, political, or otherwise sensitive content, I would not choose .top again, nor another TLD operated by an organisation subject to the same content controls. Recovering a domain should not depend on whether its owner has the time, patience, and confidence to keep escalating by email.

Source material and caveat

• Complete redacted email correspondence
• Period covered: 8–11 September 2026
• Outcome: the registry removed ServerHold and restored DNS resolution

This is a record of one case, not legal advice. The same approach may not produce the same result for another domain or registry.