How to Report Domain Abuse to a Registrar
Under their ICANN accreditation agreement, domain registrars must act on domains used for DNS Abuse such as phishing and malware, and suspension is one of the actions open to them. The report goes to the sponsoring registrar named in the domain’s RDAP record, and it is actionable when it states verifiable facts: the complete URL where the abuse is located and a screenshot of what it served.
Updated
- Where to report
- Sponsoring registrar
- Response time
- Varies by registrar
- Primary remedy
- clientHold / suspension
The sequence is short: find the sponsoring registrar in the domain’s RDAP record, report to its published abuse contact with only what can be verified, and ask for the domain to be placed on clientHold. Under Section 3.18.2 of the ICANN Registrar Accreditation Agreement, a registrar with actionable evidence of DNS Abuse must promptly take appropriate mitigation action, and a registrar that ignores a well-founded report can itself be reported to ICANN Contractual Compliance.
Understanding the role of the sponsoring registrar
Each generic top-level domain (gTLD) is operated by a registry under contract with ICANN, while individual domain registrations are sponsored by ICANN-accredited registrars. The registrar offers the registration service; the registry maintains the authoritative database of registered names and publishes the zone. When a domain is used for DNS Abuse, such as phishing through copycat websites or malware distribution, the registrar can suspend resolution by applying the clientHold status code, which tells the registry not to activate the name in the DNS. These contractual duties apply to ICANN-accredited registrars for gTLD names; ccTLD registrations follow the ccTLD registry’s own policies.
Step 1: Identify the sponsoring registrar via RDAP
As of 28 January 2025, ICANN made the Registration Data Access Protocol (RDAP) the definitive source for gTLD registration data in place of the sunsetted WHOIS services, so legacy whois output can no longer be relied on for gTLDs. Use RDAP to query the authoritative registry record. You can look any domain up in the public ICANN Lookup. Key fields to extract:
- Sponsoring registrar: The legal name and IANA identifier of the registrar entity.
- Abuse contact email: The registrar’s abuse email and phone, which ICANN’s gTLD RDAP profile requires in the record.
- Registration timestamp: The exact date and time the subject was registered.
- Current status: EPP status codes (such as
ok, which RDAP displays asactive,clientHold, orserverHold). - Name servers: The delegated DNS hosts directing traffic for the domain.
You can query RDAP data and mapped abuse channels with the free domain abuse contacts tool. The provider abuse contacts directory lists the documented reporting channel and evidence requirements for many registrars and hosts.
Step 2: Collect objective, verifiable evidence
ICANN expects the evidence to be actionable: enough for the registrar to make a reasonable determination that the domain is being used for DNS Abuse. Present verifiable observations only:
- Probed URLs: Provide the exact URLs observed serving abusive content, including the full scheme and path (such as
https://lookalike-domain.example/login). - Host IP and ASN: Document the resolved IP address and Autonomous System Number hosting the content at probe time.
- Capture timestamps: Note the precise UTC timestamp when the content was observed live.
- Visual match evidence: If deceptive assets (such as copied logos, favicons, or authentication forms) were served, include unedited screen captures showing the browser address bar and what the page impersonates.
- DNS and mail records: If the domain has mail exchange (MX) records, which mail senders look up to deliver to it, or sender policy (SPF) records, which authorize hosts to send mail using it, provide the DNS query records.
Step 3: Submit the report via the designated channel
Registrars publish either a web form or an email address (such as abuse@registrar.example). Documented channels for several major registrars: GoDaddy, Namecheap, Porkbun, Hostinger, and IONOS. When submitting:
- State the specific abuse category in the subject line (for example:
Phishing Report: [domain] targeting [brand]). - State the verified observations in a factual, chronological structure.
- Attach the capture image and full technical header or DNS record transcript.
- Request confirmation of receipt and application of
clientHoldor suspension pending investigation.
Step 4: Escalation for non-responsive registrars
If an ICANN-accredited registrar fails to investigate an actionable phishing or malware report promptly, or if their designated abuse contact bounces:
- Report to the upstream registry: gTLD registry operators must publish an abuse contact, and with actionable evidence of DNS Abuse they must at least refer the domain to the sponsoring registrar or act on it directly.
- File an ICANN compliance complaint: Submit an official complaint to ICANN Contractual Compliance under the Registrar Accreditation Agreement. ICANN investigates whether the registrar is fulfilling its contractual obligations under Section 3.18, including the duty to promptly take appropriate mitigation action once it has actionable evidence of DNS Abuse.
If the domain itself infringes your trademark and abuse reporting does not resolve it, filing a UDRP complaint can transfer ownership of the domain to you.
Abuse reporting reacts to domains you have already found. Domain monitoring finds new lookalike registrations in daily registration feeds and records the registrar, DNS, and site facts this process requires when they are observed.
Sources
- ICANN Compliance advisory: DNS Abuse obligations in the Registrar Accreditation Agreement (Section 3.18)
- ICANN: registrar abuse reports and complaint options
- ICANN Lookup: public RDAP search for any domain
- ICANN Contractual Compliance complaint form
- ICANN: 2013 Registrar Accreditation Agreement
- ICANN: launching RDAP, sunsetting WHOIS (27 January 2025)
- ICANN: gTLD RDAP Response Profile (February 2024)
- ICANN: EPP status codes
- RFC 8056: EPP and RDAP status mapping
- ICANN: Uniform Domain Name Dispute Resolution Policy
- RFC 5321: Simple Mail Transfer Protocol
- RFC 7208: Sender Policy Framework (SPF)
Frequently asked questions
The registry publishes the TLD zone and the registrar offers the registration. When a registrar places a domain on clientHold, the registry does not activate the name in the DNS, so it does not resolve. A hosting provider administers the servers that hold the content; a host can remove that content while the domain itself remains registered.
Since the DNS Abuse amendments took effect on 5 April 2024, Section 3.18 of the ICANN Registrar Accreditation Agreement (RAA) works in steps. Under 3.18.1 the registrar publishes an abuse contact and confirms receipt of each report, by email or on screen. Under 3.18.2, once it has actionable evidence, it must promptly take the appropriate mitigation actions reasonably necessary to stop or otherwise disrupt the domain’s use for DNS Abuse: malware, botnets, phishing, pharming, and spam that delivers those. ICANN sets no fixed deadline for “promptly” and reviews it case by case. Under 3.18.3, well-founded reports from law enforcement and similar authorities must be reviewed within 24 hours. These duties bind ICANN-accredited registrars for gTLD names; ccTLD registrations follow the ccTLD registry’s own policies.
Whatever a privacy or proxy service shows for the registrant, the RDAP record of a gTLD domain must still name the sponsoring registrar and include its abuse email and phone. You submit the report directly to the registrar abuse desk, not the privacy or proxy service.
The registrar’s abuse duty covers DNS Abuse (malware, botnets, phishing, pharming, and spam that delivers those), not trademark similarity on its own. Under the UDRP, a registrar cancels or transfers a registration on the registrant’s instructions, an order from a court or arbitral tribunal of competent jurisdiction, or a UDRP administrative panel decision.
Related tools and resources
Ongoing brand monitoring
notolens checks new domain registrations across 1,570 TLDs and app store results daily, search ads multiple times a day, and trademark registers weekly. When a lookalike domain, conflicting mark, copycat app, or ad using your name appears, notolens checks it, explains the risk, and hands you the records and possible next steps.