Skip to content
AdminKit

How do you find the right abuse contact from a WHOIS or RDAP lookup?

AdminKit explains how to find the right abuse contact in a WHOIS or RDAP result: a domain's abuse contact is the registrar's ICANN-required address, exposed in RDAP as an entity with the role "abuse"; an IP's abuse contact instead belongs to whichever regional registry (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC) holds that block — the two are looked up differently.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • A domain’s abuse contact belongs to its registrar. In RDAP for gTLD domains it is an entity with the role abuse, nested inside the registrar’s entity.
  • An IP address’s abuse contact belongs to the network holding that address block, as recorded by a regional internet registry. Look up the IP itself, not a domain that points to it.
  • The registrant’s own details are the wrong place to report abuse, and are often redacted anyway.
  • If no abuse role appears (common with some ccTLDs), fall back to the registrar’s published abuse address or the network’s general contact.

Why are domain and IP abuse contacts different?

“Who do I tell about this” turns out to be two unrelated questions depending on whether you’re looking at a domain name or an IP address, and a WHOIS/RDAP result answers each one through a different field. A domain’s abuse contact traces back to its registrar, under rules ICANN imposes on every company it accredits to sell domain registrations. An IP address’s abuse contact instead traces back to whichever organization a regional internet registry — ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC — shows as holding that specific address block. AdminKit’s Whois / RDAP tool fetches the RDAP record directly from your browser via the rdap.org proxy, which routes your query to the correct registry for either kind of lookup automatically, but reading the right field out of the result still means knowing which one you’re looking at.

The routing itself is standardised. RFC 9224 defines bootstrap registries that IANA publishes: files mapping each top-level domain, IPv4 range, IPv6 range and AS number range to the RDAP service of the registry responsible for it. rdap.org describes itself as a bootstrap server that aggregates the known RDAP servers and redirects each query to the right one, so a client only needs a single starting URL. That is also why the curl example below uses -L: the first answer is a redirect, not the record.

Domain nameIP address
Whose record it isThe registrar’s, published by the registryThe address holder’s, published by the RIR
RDAP query path (RFC 9082)/domain/example.com/ip/192.0.2.10
Where the abuse contact sitsEntity with role abuse inside the registrar entityEntity with role abuse, at the top level or inside the holder’s entity
Rule that requires itICANN Registrar Accreditation Agreement (gTLDs)Each RIR’s own policy, e.g. RIPE NCC’s abuse-c
Who acts on the reportThe registrar, about the domain registrationThe network operator, about traffic from its addresses

Where does a domain’s abuse contact sit in RDAP?

A modern RDAP result represents everyone associated with a domain as an entry in an entities array, and each entry carries one or more roles — standardized labels defined in IANA’s RDAP JSON Values registry and used by the JSON schema RFC 9083 specifies. Common roles include registrant (who registered the domain), technical (who manages its technical configuration), and — the one you want for reporting a problem — abuse. ICANN’s accreditation agreement requires every registrar it accredits to publish a dedicated abuse-report contact, specifically so that reports about spam, phishing, malware distribution, or other misuse of a domain reach someone with the standing to act on the registration, rather than an inbox the registrant may never check (or that privacy redaction has hidden entirely). That requirement is why the abuse entity is often the one piece of contact information still visible in an otherwise heavily redacted result.

The exact wording is in §3.18.1 of the 2013 Registrar Accreditation Agreement: the registrar “shall maintain an abuse contact to receive reports of abuse involving Registered Names sponsored by Registrar”, publish an email address for it on its website, and “take reasonable and prompt steps to investigate and respond appropriately”. §3.18.2 adds a separate contact, monitored around the clock, for reports from law enforcement and similar authorities.

Where it appears in the JSON is set by ICANN’s gTLD RDAP Response Profile. Its §2.4.5 says the server must include an entity with the abuse role within the registrar entity, and that it must carry tel and email members. So the abuse contact is one level down, not in the top-level list. A trimmed response looks like this (illustrative values; the registrar, address and NANP 555-01xx phone number are placeholders):

{
  "objectClassName": "domain",
  "ldhName": "example.com",
  "entities": [
    {
      "objectClassName": "entity",
      "roles": ["registrar"],
      "vcardArray": ["vcard", [["fn", {}, "text", "Example Registrar, Inc."]]],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": ["abuse"],
          "vcardArray": ["vcard", [
            ["fn", {}, "text", "Abuse Contact"],
            ["tel", {"type": "voice"}, "uri", "tel:+1.2025550100"],
            ["email", {}, "text", "abuse@registrar.example"]
          ]]
        }
      ]
    },
    {
      "objectClassName": "entity",
      "roles": ["registrant"],
      "vcardArray": ["vcard", [["fn", {}, "text", "REDACTED FOR PRIVACY"]]]
    }
  ]
}

A tool or script that only scans the top-level entities misses it. If you work with raw RDAP from the command line, search the whole tree for the role instead. This jq filter prints the email of every abuse entity at any depth:

curl -sL https://rdap.org/domain/example.com \
  | jq -r '.. | objects | select((.roles // []) | index("abuse"))
           | .vcardArray[1][] | select(.[0] == "email") | .[3]'

Why isn’t the registrant’s contact the right address?

It’s an easy mistake to assume the registrant’s email, when visible, is also the right place to report abuse — but that conflates two different relationships. The registrant is whoever registered the name, which privacy rules such as GDPR frequently redact behind a privacy-proxy placeholder regardless of whether the domain is being misused. The abuse contact exists precisely because the registrant’s own cooperation can’t be assumed: it’s a mandatory channel into the registrar’s own abuse-handling process, which can act on a domain — suspending it, requiring changes, or escalating to the registry — independently of whether the registrant ever responds at all.

Where does an IP address’s abuse contact come from?

IP addresses are allocated through an entirely separate system from domain names, so they have their own abuse-contact mechanism. Running AdminKit’s Whois / RDAP tool against the IP address directly (not a domain that merely resolves to it) returns an RDAP result scoped to that address block: which regional internet registry manages it, and which organization the registry’s own records show as the current holder. Larger network operators typically register a dedicated abuse-contact role in their registry entry for exactly this purpose; smaller allocations sometimes only list a general technical or administrative contact, in which case that’s the best available starting point even though it isn’t a dedicated abuse address.

The registries set their own rules here. RIPE NCC’s abuse-c policy, implemented from 2013, requires every resource it allocates or assigns to carry an abuse-c: attribute: the organisation object references a role object whose abuse-mailbox: holds the address. In RDAP that shows up as an entity with the abuse role, which IANA’s registry describes as the entity that “handles network abuse issues”. Its position in the JSON varies between registries, which is one more reason to search the whole tree as above.

The tool takes IPv4 and IPv6 addresses alike. Either way, the answer is an RDAP IP network object (RFC 9083) describing the whole registered block, with its start and end addresses, not a record for the single address you typed. Remember what an IP lookup tells you: who runs the network the address belongs to. For a cloud or hosting range, that is the provider, not its customer, and the provider is the one who can act.

What if no abuse contact shows up at all?

ICANN’s abuse-contact requirement binds its accredited registrars and the generic top-level domains (.com, .org, .net and the newer gTLDs) it oversees — it does not automatically extend to every country-code top-level domain, many of which run independent registries with their own, separately set policies. A ccTLD domain’s RDAP result may therefore have no entity carrying the abuse role at all, even though the registrar still maintains some abuse-handling process elsewhere, typically published on the registrar’s own website rather than surfaced in the structured RDAP data itself. In that situation, falling back to the registrar’s general published policy page is the practical next step, rather than assuming no reporting path exists.

Which contact should you use for what you’re reporting?

What you’re reportingLook upRole to findFallback
A phishing or malware domainThe domainabuse inside the registrar entityThe registrar’s published abuse address
Spam or attacks from an IP in your logsThe IP addressabuse (RIPE: abuse-c)The network’s technical or administrative contact
A phishing page on a shared hosting IPBothHosting network’s abuse for the content; registrar’s for the domainReport to both; each can act on its own layer
Traffic from a whole networkThe IP, then its ASNabuse on the network or ASN recordThe operator’s published abuse address

What can an abuse contact do for you?

Identifying the right contact is the first step of reporting a problem, not a guarantee the problem gets resolved — what happens after a report lands depends entirely on that registrar’s or registry’s own abuse-handling process, staffing, and policies, none of which an RDAP lookup can see into. See how to file an abuse report from a WHOIS/RDAP result for what to put in the report itself once you’ve found this contact, and what response you can realistically expect back. It’s also worth pairing an abuse report with the broader context of why you’re investigating an address or domain in the first place: if you arrived here because an IP got flagged as a source of spam, see why is my IP address blacklisted? for how that reputation gets built and what delisting actually involves, separate from the abuse-reporting path covered here. See our security analysts and SOC teams page for how this lookup fits into triaging an unfamiliar address more broadly. This guide is part of AdminKit’s DNS cluster of WHOIS/RDAP and other DNS guides and tools.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Is the abuse contact the same as the registrant's own email address?

No, and conflating the two is the most common mistake. The registrant's contact details are frequently redacted entirely under privacy rules such as GDPR, and even when visible, they identify who registered the name — not who handles abuse reports for it. The abuse contact is a separate, dedicated address that ICANN's registrar accreditation rules require every registrar to maintain specifically for receiving reports about a domain, independent of whether the registrant's own details are shown at all.

Where exactly does the abuse contact show up in an RDAP result?

Inside the RDAP response's entities array, as an entity whose roles list includes the value "abuse" — a specific, standardized role value defined in IANA's RDAP JSON Values registry and used by the JSON response format RFC 9083 specifies. That entity typically carries its own vCard with a name, email and sometimes a phone number, separate from the registrant or technical-contact entities that may appear alongside it in the same result.

What if a domain's RDAP result has no entity with an "abuse" role at all?

That's more common with country-code TLDs (ccTLDs) than with generic TLDs, since ICANN's abuse-contact requirement applies specifically to its accredited registrars and gTLD registries, not to every ccTLD registry worldwide — many of which run their own, independently set policies. When no abuse role appears, the next-best step is the registrar's own published abuse policy page, which registrars are required to maintain even when a given RDAP response doesn't surface a dedicated entity for it.

How is reporting abuse for an IP address different from reporting a domain?

A domain's abuse contact comes from its registrar; an IP address's abuse contact instead comes from whichever regional internet registry's record shows the organization that address block is allocated to — a completely separate lookup, since domain registration and IP address allocation are managed by different systems. An RDAP lookup on the IP itself, rather than on any domain that happens to resolve to it, is what surfaces that registry-level abuse contact.

I found an abuse contact — does reporting to it guarantee the problem gets fixed?

No. It routes your report to whoever is contractually or administratively responsible for that resource, but what happens next depends entirely on that registrar's, registry's, or network operator's own abuse-handling process and how quickly they act on it — AdminKit's lookup only identifies the correct contact, it has no visibility into, or influence over, what happens after a report is sent.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.