An address can be registered to one organization and announced by another. Read the registration, the routing declaration and the BGP observation as three separate pieces of evidence.
An IP WHOIS lookup returns the public registration record for the block containing an address. Enter one public IPv4 or IPv6 address from a log, a traceroute or a network inventory. The registered network and the start and end addresses show which part of the address space the record covers. If the registry publishes a network name or description, you can use it to recognize the allocation when comparing several addresses.
The tool matches the address against the IANA RDAP directory and sends the lookup to the corresponding regional registry. The record may include a registered organization, registration date, last update and allocation type. A registry can publish a description where another publishes a formal organization entry, and some fields may be absent. Open the original RDAP record if you need the exact wording of an allocation or an explanation supplied by the registry.
Read the registered origin ASN
An Autonomous System Number, or ASN, identifies an autonomous system that exchanges routing information with other networks. An origin ASN is the AS identified as originating a destination prefix in a BGP announcement. For the registered origin, this tool reads route and route6 objects from Internet Routing Registry data returned by RIPEstat. These objects record which AS an operator has listed as the origin of a prefix.
The registered IP block can be broader than an IRR route prefix. Check the prefix on the same line as each ASN and look at the registry listed beside it. Several IRR records may cover the address, and different records can list different origin ASNs for overlapping prefixes. Keeping the prefix and its source with each record lets you see where the data agrees or conflicts without relying on an organization name to identify the route.
Compare the observed BGP route
The BGP observation uses RIPE RIS, a network of route collectors that receives announcements from participating routers. When RIPEstat finds a match, its response identifies the observed prefix covering the IP and the origin ASNs associated with that prefix. Compare it with the IRR record using both the prefix length and the ASN. For example, a /24 BGP prefix can sit inside a /16 registration block and describe a more specific part of that allocation.
If RIPE RIS has no matching observation, the result may still contain a network registration and an IRR route object. Collector coverage, update timing and the scope of an announcement can all affect which routes appear. A temporarily unavailable source is shown separately from an empty result. For operations work, keep the input address and the source links with any result you share, since observations may differ when you run the lookup again.
Find the right contact for an IP address
For abuse reports, start with the public abuse mailbox published for the network. Include the relevant IP address, an accurate UTC timestamp and the minimum log excerpt needed to explain the report. Administrative and technical contacts can help identify the record, while the abuse mailbox is the role intended for reporting activity. If no contact is listed, the original record can show any notices, referral information or registry reporting instructions.
The registration country describes the network record. A mailing address can point to a network operator’s office even when the equipment and its users are elsewhere. The IP geolocation section estimates the address’s location and identifies its internet provider using a separate database. For a domain name and its registrar details, use the domain WHOIS tool.
Check the address format and keep the source links
Paste the address itself. If you copied a log entry, remove the port number, surrounding brackets and any interface suffix before looking it up. Use the registered network field to compare a block with an address inventory. The lookup takes a single address. The returned CIDR describes the registration and can cover many more addresses than the one you entered.
For an incident handoff, record the IP you searched, the registered range, the IRR prefix and origin, and the BGP prefix and origin if observed. Preserve the links so the next person can retrieve each source independently. When the sources disagree, the record dates and routing observations can help you decide which network team to contact for clarification.
If you are checking an address used by a cloud service, start with the record for that exact address. A provider can run the routing and hold the network registration while assigning individual addresses to customers. The public record usually stops at the organization or its network contact. To identify a particular server in your own environment, compare the address with your provider account, allocation inventory or network logs.