English
Notify me

Reporting a Domain to Its Registrar: the Last Escalation Step

Short answer: find the domain's registrar and its abuse contact with an RDAP lookup at lookup.icann.org. Send one clear report: the infringing links, copies of your earlier notices to the site and the host with their dates, and proof you own the work. Under ICANN's rules the registrar must investigate and respond appropriately — but it is not required to suspend a domain over copyright, so treat this as a final escalation rather than a sure shutdown.

At a glance

When After the site and the hosting provider ignored or refused your notices
Where The registrar's abuse email or form, from an RDAP lookup
Account Not needed
Cost Free
Time to file 20–30 minutes, mostly gathering the earlier notices (our estimate)
Response time "Reasonable and prompt" under ICANN's rules; no fixed deadline for copyright
Likely outcome Report forwarded to the domain owner; sometimes a warning; suspension only in clear, documented cases and not guaranteed

Where the registrar sits in the chain

Step Who you contact What they can remove
1 Search engines The page from search results
2 The site itself The content
3 The hosting provider (through Cloudflare if needed) The content, or the server
4 The registrar The whole domain — rarely, and only as a last resort

The registrar controls the domain name, not the content. Acting on it is the heaviest and least likely step, which is why it comes last.

What a registrar is actually required to do

ICANN-accredited registrars sign an agreement that requires them to publish an abuse contact and to take reasonable and prompt steps to investigate and respond appropriately to abuse reports. In practice:

  • At a minimum, a registrar usually forwards the report to the domain owner.
  • Copyright infringement is not one of the defined "DNS abuse" categories (malware, botnets, phishing, pharming, and spam used to deliver those) where a registrar is expected to take mitigation action.
  • Whether to suspend a domain is the registrar's own decision. A well-documented pattern of ignored notices makes action more likely, but nothing obliges it.

So a registrar notice is worth sending when the lower steps have failed, with realistic expectations.

What to prepare

  • The infringing URLs, still live.
  • Copies of your earlier notices to the site and the hosting provider, with the dates you sent them and any replies (or the absence of replies).
  • Proof you own the work: a link to the original and its publication date.
  • The domain's registrar and abuse contact, from the lookup below.
  • Your contact details and the authorization if you act for someone else.

How to find the registrar

  1. Open lookup.icann.org and enter the domain.
  2. Read the Registrar section: the registrar's name and its abuse contact email.
  3. If the lookup hides the owner's personal data, that's normal — the abuse contact stays public. See abuse contact.
  4. For a country-code domain, check the national registry's website instead, as its rules may differ.

What to send

Use the registrar escalation template. Keep it factual: the URLs, the history of notices with dates, your proof of ownership, and a plain request that the registrar investigate and respond. Attach your earlier notices. Avoid threats and legal posturing; a clear record does more.

What happens next

  • The registrar acknowledges the report (not all do) and usually forwards it to the domain owner.
  • The owner may remove the content, ignore it, or move the domain to another registrar.
  • In clear, repeated cases some registrars place the domain on hold; most do not act on copyright alone.
  • Keep the search-result delistings in place meanwhile — that keeps traffic down regardless of what the registrar does.

If the registrar does nothing

  • No reply at all: for an ICANN-accredited registrar, file a complaint with ICANN Contractual Compliance. You must show you first contacted the registrar's abuse address. ICANN checks whether the registrar met its duty to investigate and respond — it does not itself remove content or domains.
  • The domain moves or changes: the content and its host usually stay the same. Keep working the host and the search engines.

Common mistakes

  • Writing to the registrar first, before the site and the host have had a notice.
  • Expecting the registrar to delete the content — it controls the domain, not the files.
  • Sending no evidence of the earlier, ignored notices.
  • Treating a country-code domain as if ICANN's rules applied.
  • Reporting content you don't own: a knowingly false notice can lead to liability under 17 U.S.C. §512(f).

If this keeps happening

Reaching the registrar step means a site has ignored every earlier notice — and the worst sites do this across many domains that change often. Tracking which notices were sent, when, and with what result, for each domain, is the slow part. PiracyGone keeps that history for every link and escalates in order — search engines, host, then registrar — automatically. Start with a free scan.

Frequently asked questions

Will the registrar take the domain offline?

Often not. ICANN-accredited registrars must investigate abuse reports and respond appropriately, but copyright is not in the narrow set of 'DNS abuse' categories where they must act. Many simply forward your report to the domain owner.

When is it worth contacting the registrar?

After the site and its hosting provider have ignored or refused your notices. It is an escalation step, not a first contact.

The domain ends in a country code like .ru or .to. Does this apply?

Not always. Country-code domains follow the rules of their own national registry, which may differ from ICANN's. Check that registry's website for its complaint policy.

What if the registrar never replies?

For ICANN-accredited registrars you can file a complaint with ICANN Contractual Compliance, showing that you first sent your report to the registrar's published abuse contact.

General information, not legal advice. Send notices only about content you own or are authorized to act for.