Network & Abuse Contact Finder
AvailableFind who to contact about an IP address, AS number, domain or hostname: the registered abuse contact, network and AS role contacts from RDAP, PeeringDB NOC and peering contacts, the site’s security.txt, the registrar’s abuse contact and DMARC report addresses — each with its source and how authoritative it is.
Find network and abuse contacts
Contacts
How it works
For an IP the NetTools server asks RIPEstat for the abuse contact registered with the responsible RIR and reads the role contacts of the IP network in RDAP, then follows the routed prefix to its origin AS (RDAP autnum and PeeringDB contacts). For a domain it reads the registrar abuse contact from the domain’s RDAP record, the site’s security.txt, the DMARC report addresses and the SOA mailbox, then follows the domain’s address to its hosting network. Contacts are merged and labelled as authoritative, published by the target or derived.
Where the contacts come from
- Verified / authoritative — the regional internet registry’s registered abuse contact (RIPEstat abuse-contact-finder, which names the responsible RIR; it does not have an abuse address for every network — RDAP is asked as well) and role contacts in the RDAP records of the IP network, the AS number and the domain’s registrar.
- Published by target — what the network or site publishes itself: its security.txt (RFC 9116), DMARC report addresses and PeeringDB NOC / policy contacts.
- Inferred / derived — the responsible mailbox in the DNS SOA record, converted to an address; often a DNS provider’s mailbox and rarely read.
- For a domain, the network contacts belong to the network hosting its address — often a hosting or CDN provider, not the site owner. Use the registrar abuse contact for abusive domains and security.txt for vulnerabilities.
- Registry contacts whose vCard says they are an individual person are not shown, only counted. Reports are not saved; public answers from RIPEstat, RDAP and PeeringDB are cached briefly in server memory.
Safeguards & responsible use
- Only contacts published for operational, abuse or security purposes; registry contacts of individual people are not shown (only counted).
- No social networks or search engines are queried and no profile of any person is built.
- Queries go only to RDAP servers listed by IANA, RIPEstat, PeeringDB, public DNS resolvers and the target’s own /.well-known/security.txt.
- Rate limited and time limited; reports are not saved (public source answers are cached briefly in memory).
Learn more
What is Network & Abuse Contact Finder?How it works, how to read the results, troubleshooting and FAQs. Complete guide →Frequently asked questions
Which contact should I use to report abuse?
The abuse contact of the network the traffic comes from — shown first, normally the address registered with the regional internet registry. For an abusive domain (phishing, malware) use the registrar abuse contact; for a vulnerability in a website use its security.txt contact.
Why does a domain show contacts of another company?
The network contacts belong to whoever hosts the domain’s address, often a hosting provider or CDN. They can act on abuse from their network but are not the site owner.
What do authoritative, published and derived mean?
Authoritative contacts come from registry records (RIR abuse contacts, RDAP). Published contacts are what the network or site publishes about itself (security.txt, DMARC, PeeringDB). Derived contacts are inferred from records not meant as contacts, such as the DNS SOA mailbox.
Why are some registry contacts missing?
Contacts that the registry marks as individual people are deliberately not shown. Registrant data of domains is also usually redacted by the registry.
Are DMARC addresses general contacts?
No. rua and ruf addresses receive automated DMARC reports, often at a reporting service. They are listed for completeness, not as a way to reach the domain owner.