Your firewall logs a brute-force run from an address you have never seen, a customer forwards a phishing page hosted on a domain you do not know, or a route leak is breaking reachability to a prefix and you need the operator's NOC. The question is the same each time: who do I actually write to? The answer is spread over several registries, PeeringDB, DNS records and the site itself, and the obvious-looking address is often the wrong one.
Network & Abuse Contact Finder takes an IP address, an AS number or a domain, follows it to the network, the origin AS, the registrar and the website, and lists the contacts each of them publishes for abuse, security, operations and peering. Every contact carries its source, the object it belongs to and how authoritative it is, so you can pick the right one instead of the first one.
What is a network and abuse contact finder?
In simple terms
Networks, registrars and websites publish role mailboxes for specific jobs: an abuse desk for spam and attacks, a security contact for vulnerability reports, a NOC for outages, a registrar abuse desk for abusive domains. A contact finder looks these up for one resource and tells you which mailbox is for what. It does not guess addresses and it does not look for people.
Technical background
Each contact type lives in a different system:
| Source | What it publishes | Standard |
|---|---|---|
| RIR abuse contact | The abuse mailbox registered for an IP block or AS (in the RIPE database the abuse-c attribute); RIPEstat's abuse-contact-finder returns it for all five RIRs | RIR policy |
| RDAP | Registration records for IP networks, AS numbers and domains, with entities carrying roles such as abuse, noc, technical, administrative and registrar, each described as a jCard (JSON vCard) | RFC 9083 |
| PeeringDB | Points of contact a network operator publishes itself (NOC, Abuse, Policy, Technical, Maintenance) and its peering policy URL | PeeringDB data |
| security.txt | Contact: fields under /.well-known/security.txt for vulnerability reports | RFC 9116 |
| DMARC | rua (aggregate) and ruf (failure) report addresses in the _dmarc TXT record | RFC 7489 |
| SOA RNAME | The zone's "responsible person" mailbox, written as a domain name (hostmaster.example.com means [email protected]) | RFC 1035 |
An RDAP vCard with kind: individual describes a natural person; the Contact Finder counts such entities and never displays them.
Why use the Contact Finder?
- Reach the right desk. Abuse from a network, a phishing domain and a vulnerability in a website go to three different places. The tool labels each contact with the job it is for.
- Avoid dead mailboxes. A registry abuse contact is registered specifically for abuse reports; an SOA mailbox often goes unread. Provenance labels make the difference visible.
- See the whole chain at once. Domain → registrar → hosting address → network → AS → organization in one report, instead of separate WHOIS, RDAP and PeeringDB lookups.
- Know which sources answered. The source table shows whether a missing contact is unpublished or its source was down.
Who should use it?
SOC analysts and administrators reporting attacks or spam, network engineers who need another operator's NOC or peering contact, security researchers looking for a disclosure contact, and operators checking what their own resources publish.
How the Contact Finder works
Your browser sends only the resource to the NetTools.tech API (operation contact-finder). The NetTools server queries fixed services; no URL you type is fetched except the target's own security.txt. Each source runs independently with its own 14-second timeout and reports a state; a failed source never hides the others. The whole lookup is limited to 45 seconds.
IP address. In parallel the server asks:
- RIPEstat abuse-contact-finder for the abuse contact registered with the responsible RIR (up to 10 addresses, plus the RIR name).
- RDAP of the IP network, at the server found through the IANA bootstrap registry: network name, holder, country and the role contacts.
- RIPEstat network-info for the routed prefix and its origin AS.
If an origin AS was found, the AS step runs next.
AS number. In parallel: RIPEstat abuse-contact-finder for the AS, RDAP of the AS number (autnum), RIPEstat's AS overview for the AS name, and PeeringDB for the network record. From PeeringDB only contacts the network marked Public are used, with their role, never a person's name; the peering policy URL is added as a Peering / policy contact. Without a PeeringDB API key on the server the lookup is anonymous, which the source row says.
Domain or hostname. In parallel:
- RDAP of the domain; for a hostname such as
www.example.comthe server walks up to the registered domain. The registrar's nested abuse entity becomes the Registrar abuse contact. - security.txt from
https://<host>/.well-known/security.txt(then/security.txt), and if none exists, from the parent domain. Onlymailto:,tel:andhttps://Contact values are used; an expired file is flagged. - DMARC record of the domain or, if it has none, its parent;
ruaandrufmailto addresses are extracted, and addresses outside the domain are marked as external reporting mailboxes. - SOA of the zone (walking up the labels), whose RNAME is converted to an address, respecting escaped dots.
- A record (or AAAA if there is no A record) through public resolvers 1.1.1.1 and 8.8.8.8. The first public address is then looked up as an IP, so the network and AS contacts that follow belong to the hosting network.
Merging. The same role and value from several sources become one entry that lists every source and every object it belongs to; the best provenance wins. Contacts are sorted by role, then by provenance. RDAP entries are limited to two phone numbers and two URLs per entity.
Refused input. Non-public IP addresses and special-use AS numbers have no operator contacts and are rejected with an explanation; email addresses are refused because this is not a people search.
Rate limits and caching. A lookup costs 3 tokens of the per-client API budget (a burst of 20, then 30 tokens per minute). RIPEstat answers are cached in server memory for 30 minutes and PeeringDB network records for 6 hours; the report itself is not stored.
How to use the NetTools.tech Contact Finder
- Open Network & Abuse Contact Finder.
- In IP address, AS number or domain, enter an IPv4 or IPv6 address,
AS13335or13335, or a domain or hostname. A pasted URL is reduced to its host, and IPv6 in brackets is accepted. You can also click one of the examples under Try:. - Press Find contacts. Progress steps show which sources are being queried.
- Read the Primary contacts first, then check the notes and the source table.
- Click a row in Contact availability to list only that role in the contacts table; click again or × Show all roles to reset.
- Use the buttons under the summary to continue in IP Lookup, the BGP Looking Glass, the ASN Explorer, IXP & Peering Explorer, WHOIS, the security.txt Checker or DMARC Lookup.
- Export with CSV, JSON, Copy all or Print. The page URL (
/contact-finder?q=193.0.6.139) can be bookmarked or shared and reruns the lookup.
Understanding the results
| Result | Meaning | What to look for |
|---|---|---|
| Subtitle | Number of contacts, how many sources found something out of how many were asked, retrieval time in UTC | Few sources found means check the source table before concluding |
| Network & organisation | Input type, registered domain, registrar, IP address (for a domain: the address it resolves to), network name and prefix, ASN, organisation and country from the registry, RIR | For a domain, the network is the hosting network, not the site owner |
| How the contacts were found | The chain Input → Domain → Registrar → Address → Network → ASN → Organization → number of contacts and roles | Shows which object each contact group belongs to |
| Primary contacts | Cards for Abuse, Security (security.txt), NOC, Registrar abuse and Peering / policy: the best contact (email preferred), its provenance, its sources and "+N more" | "Not found in the sources that answered" is not proof that none exists |
| Notes | Hosting-network warning, no origin AS, unresolvable domain, number of withheld individual contacts, no abuse contact found | Read these before sending anything |
| Contact availability | Matrix of roles × sources with counts; Abuse, Security, NOC, Technical and Registrar abuse always appear | Abuse confirmed by both RIPEstat and RDAP is the strongest signal |
| Source coverage | Bar and table: each source, what it was asked, its state, contact count, message and age of the data | Source unavailable or Rate limited means retry later |
| All contacts | Role and what it is for, contact with notes, provenance, the objects it belongs to, organization and links to each source | Notes such as "external reporting mailbox" or "security.txt is expired" |
Provenance labels:
| Label | Sources | How to treat it |
|---|---|---|
| Verified / authoritative | RIPEstat abuse-contact-finder, RDAP role contacts of the IP network, AS or domain/registrar | First choice for abuse reports |
| Published by target | security.txt, DMARC, PeeringDB | Correct for its purpose (security reports, NOC, peering); DMARC addresses are report mailboxes only |
| Inferred / derived | DNS SOA RNAME | Last resort, often unmonitored |
Source states: Found, Not found, Source unavailable (an error or no answer within the timeout) and Rate limited. "Not found" with a message such as "No security.txt is published" or "The registry publishes no role contacts for this domain" means the source answered and had nothing.
Example: looking up 193.0.6.139 and ripe.net
The following results were checked on 23 October 2026; registry and DNS data can change.
193.0.6.139 (an address of the RIPE NCC). The chain reads 193.0.6.139 → 193.0.0.0/21 (network RIPE-NCC) → AS3333 → the registry holder → contacts. The Abuse card shows the RIPE NCC abuse mailbox at ripe.net, labelled Verified / authoritative, with two sources: RIPEstat abuse-contact-finder and RDAP (rdap.db.ripe.net). In the availability matrix the Abuse row therefore has a tick in both columns. Because an origin AS was found, AS3333 was looked up too, and its RDAP, RIPEstat and PeeringDB results appear as separate rows in the source table.
ripe.net (the domain). The summary shows registrar Gandi SAS. The Registrar abuse card comes from the .net registry's RDAP server (rdap.verisign.com) and is Verified / authoritative. The Security card shows the security mailbox at ripe.net from the site's security.txt, Published by target. The DMARC rua address points to an external reporting service and carries the note that it is a report mailbox at an external domain. The SOA of ripe.net yields the dns mailbox at ripe.net as an Inferred / derived DNS hostmaster contact. A note says that 18 registry contacts of individual people were not shown. The domain's address is then followed to its hosting network, with a note that those network contacts belong to the hosting network.
What to use: the abuse mailbox for an attack from 193.0.6.139, the security.txt contact for a website vulnerability, the registrar abuse contact for an abusive registration. The DMARC and SOA addresses suit none of these.
Common use cases
- Attack or spam source: enter the source IP and send logs to the Abuse contact.
- Phishing site: enter the domain; report the registration to Registrar abuse and the content to the hosting network's abuse contact.
- Routing problem or peering request: enter the AS number and use the NOC or Peering / policy entry.
- Checking your own resources: confirm that your IP blocks, AS and domains publish working abuse and security contacts.
Troubleshooting
"No abuse contact was found in the sources that answered"
First check the source table: if RIPEstat or RDAP shows Source unavailable or Rate limited, retry in a minute. If both answered with Not found, the holder has not registered an abuse contact; fall back to the NOC or technical contact, or to the upstream network shown in the BGP Looking Glass.
A domain shows only CDN or hosting provider contacts
That is expected: network contacts belong to the address the domain resolves to. A CDN can usually forward or act on abuse reports for its customers. For the registration itself use the Registrar abuse contact.
"No RDAP service" for a domain
Some country-code registries run only classic WHOIS, which has no structured contact roles, so no registrar abuse contact can be read. Use WHOIS Lookup for the registration data.
"No origin AS was found for this address in BGP"
The address is not announced in BGP right now, so AS and PeeringDB contacts were not looked up. The registry contacts of the network are still shown.
security.txt shows "Not found" although the site has one
Only /.well-known/security.txt and /security.txt on the host and its parent are tried, and an HTML page returned with status 200 does not count. Check the file with the security.txt Checker.
Common mistakes
- Writing to a DMARC rua address. It receives machine-generated XML reports, often at a third-party service.
- Reporting a website to its CDN only. The registrar and the origin host may be the ones who can act.
- Treating the SOA mailbox as authoritative. It is derived and frequently goes to a DNS provider.
- Concluding "no contact exists" from one failed source. Read the source states first.
Limitations
- Only published data. If an operator has not registered or published a contact, the tool cannot find one, and it never guesses addresses such as abuse@ or security@.
- Registry data quality varies. A registered abuse contact can be outdated or unanswered; whether a mailbox is read is outside the tool's view.
- One address per domain. Only the first public A (or AAAA) address is followed; other addresses may belong to other networks.
- One origin AS. For a prefix announced by several ASes only the first one reported by RIPEstat is followed.
- Redacted and withheld data. Domain registrant data is usually redacted, and individual-person contacts are never shown.
- ccTLDs without RDAP give no registrar abuse contact.
- Snapshot in time. RIPEstat answers may be up to 30 minutes old and PeeringDB records up to 6 hours old.
Security & privacy
The Contact Finder is not a people search. It queries only RDAP servers listed by IANA, RIPEstat, PeeringDB, public DNS resolvers and the target's own security.txt; it does not query social networks or search engines and builds no profile of anyone. Registry contacts of individual people are withheld and only counted. Your browser sends the IP, AS number or domain to the NetTools.tech API, which contacts those sources from the server. The query and the report are not stored, and the URL contains only the resource you looked up. There is nothing secret to enter. To review what is public about your own email address, use the Digital Footprint Self-Check (guide). See the privacy policy.
Related tools
- IP Lookup – registry holder, range, BGP origin and reverse DNS of an address; guide.
- ASN Explorer – who operates an AS, its prefixes and neighbours; guide.
- BGP Looking Glass – how a prefix is routed and by whom; guide.
- IXP & Peering Explorer – PeeringDB data for a network; guide.
- WHOIS Lookup – full registration data for a domain; guide.
- security.txt Checker – validate a site's disclosure contact; guide.
- DMARC Lookup – the full DMARC policy behind the rua and ruf addresses; guide.
- IP & Network Utilities overview.
Summary
The Contact Finder follows an IP, AS number or domain to the network, AS, registrar and website and lists the abuse, security, NOC, peering and registrar contacts they publish, each with its source and a provenance label. Use authoritative registry abuse contacts for network abuse, the registrar abuse contact for abusive domains and security.txt for vulnerabilities. DMARC and SOA addresses are shown for completeness, individual people are never shown, and nothing is stored.
Frequently asked questions
Which contact should I use to report abuse from an IP address?
Use the abuse contact of the network the traffic comes from, shown first in the Abuse card. It is normally the address registered with the regional internet registry and is labelled Verified / authoritative.
Where do I report a phishing or malware domain?
Report the domain to its registrar's abuse contact, shown as Registrar abuse, and the content to the hosting network's abuse contact. The registrar can act on the registration; the hosting provider can act on the server that serves the content.
Why does a domain show contacts of a different company?
For a domain, the network and AS contacts belong to whoever operates the address the domain resolves to, often a hosting provider or CDN. They can deal with abuse from their network, but they are not the site owner.
What do Verified / authoritative, Published by target and Inferred / derived mean?
Verified / authoritative contacts come from registry data: the RIR's registered abuse contact via RIPEstat and role contacts in RDAP records. Published by target means the network or site published it itself (security.txt, DMARC, PeeringDB), and Inferred / derived means it was converted from a record not meant as a contact, the DNS SOA mailbox.
Why are some registry contacts not shown?
RDAP contacts whose vCard says they are an individual person are never displayed; the tool only reports how many were withheld. Domain registrant data is also usually redacted by the registry, so the domain record often has no role contacts besides the registrar's.
Can I contact a domain owner through the DMARC rua address?
No. rua and ruf addresses receive automated DMARC aggregate and failure reports and are frequently hosted by a reporting service. They are listed for completeness and marked as not a general contact.
Is the SOA mailbox a good contact?
Usually not. It is derived from the RNAME field of the zone's SOA record, which often names the DNS provider's mailbox and is rarely read. Use it only when nothing better was found.
Can I use the tool to find a person's email address?
No. It is not a people search: it only reads contacts published for operational, abuse or security purposes, refuses email addresses as input, and never shows registry contacts of individual people. To see what is public about your own address, use the Digital Footprint Self-Check.
Does NetTools store my lookups?
No. The query and the report are not stored; the URL only contains the IP, AS number or domain you looked up. Some upstream answers (RIPEstat, PeeringDB) are kept briefly in the server's memory cache to avoid repeating identical requests.