IP WHOIS lookup

Read internet number registration data using RDAP, the structured successor to traditional WHOIS.

Internet registration (RDAP)

IP addresses only. Requests use the IANA directory and the responsible regional internet registry.

Example report

Illustrative data. Run a lookup for live results.

Internet registration found

Example report

The registry returned a network record. It describes allocation and public registration, rather than the subscriber using an address.

Next step: Check the source and time beside each record. Use ASN lookup for routing or reverse DNS for a hostname; rerun missing sources later.

1.1.1.1IPv4
IP address
1.1.1.1
Address family
IPv4
Registered network
Example netblock
Registry handle
EXAMPLE-NET
Address range
1.1.1.0 – 1.1.1.255
Registration country (not location)
AU
Regional registry
APNIC (RDAP)
RDAP source
https://rdap.apnic.net/
Query time (UTC)
2026-01-15T14:23:00.000Z

Registration events

  1. registration
  2. last changed

How IP registration is retrieved

  1. An IP address

    Normalize its notation and classify special-use ranges.

  2. IANA directory

    Choose the responsible regional registry for public space.

  3. RDAP request

    Read the network object returned by the registry.

  4. Registration evidence

    Show sourced range, fields and actual event dates.

This is an address-allocation lookup, not a scan of the device or a geographic measurement.
On this page

Learn more about IP WHOIS lookup

Run an IP WHOIS lookup

An IP WHOIS lookup retrieves registration information for an internet address range. Enter a public IPv4 or IPv6 address to find the responsible network record. This tool uses RDAP, the structured Registration Data Access Protocol, rather than opening a traditional text WHOIS connection. The familiar task remains an IP WHOIS lookup: identify relevant registration data, name its source, and understand what the record can establish.

Read more

The tool first classifies the input, then uses IANA's RDAP directory to select a regional internet registry. It requests the address record from that registry and displays the supported fields. The registration lookup allows only recognized registry endpoints and checks referrals before following them. User input is treated as an address, never as an arbitrary URL that the server should fetch.

Enter only the address. Domain names, full URLs, port numbers, CIDR prefixes, and interface suffixes belong to different questions. A registration lookup is not a domain registration lookup. A website's domain registrar and the organization holding its hosting network can be entirely different businesses. Choose domain WHOIS lookup for domain registration details; keep registration lookup for internet number records. Use DNS lookup to inspect published addresses for a domain, then investigate the appropriate address record if that is your actual task.

Read IP WHOIS lookup fields

The registered network name and handle identify a registry object. Start and end addresses describe the range covered by the returned record. The type field can indicate an allocation, assignment, or other registry-specific category. A registration lookup may return a record covering a broader network than the individual address's current customer. Interpret those fields together with the registry source, rather than treating the first organization-like string as a person's identity.

Read more

The source link opens the exact registry endpoint used for the result. The observation time tells you when this tool retrieved it. A registration lookup is a current observation; it does not reconstruct every historical reassignment. If you are investigating old log entries, preserve the event time separately and use suitable historical evidence. A network holder shown today might not have held the same range at the time of an earlier event.

Registration country is not physical location

The country field, when present, belongs to registration data. It can describe an administrative association rather than the physical position of a user or server. This registration lookup labels it as registration country and does not draw a map marker from it. Missing values are shown as not provided. Neither a present nor an absent country field proves where a particular packet originated geographically.

Limits of an IP WHOIS lookup

This tool reports selected network fields. It does not claim to reproduce every registry extension, nested contact entity, policy notice, or historical record. Consult the linked source when you need the complete registry response and its usage conditions. A registration lookup should make the origin of its information visible, especially when a missing field could otherwise be mistaken for a negative finding.

Read more

Why an IP WHOIS lookup can return no record

Some addresses are private or reserved for special purposes. They do not identify a public internet subscriber through ordinary registry data. Other queries can fail because a registry is unavailable, limits traffic, lacks a matching record, or refers the request to an unsupported endpoint. The registration lookup reports that condition explicitly. It does not replace a failed response with an unrelated allocation or an invented owner.

Responsible use during an abuse investigation

Collect the relevant event timestamps, source addresses, destination details, and behavior before drawing conclusions. A network registration record can help identify where to investigate further, but it should not be used to accuse a person. If you need an abuse contact, consult the complete authoritative record and the registry's documented process. This registration lookup deliberately avoids presenting unrelated personal contact fields as if they identify the sender.

Sources

The tool uses IANA's IPv4 RDAP directory and IPv6 RDAP directory. ARIN's registration documentation describes its structured service, and RFC 9083 defines RDAP JSON responses. Always consult the registry's own data and conditions when a registration lookup supports an operational decision.

IP WHOIS lookup questions

Why does this tool use RDAP?

RDAP provides structured responses over HTTP and supports discoverable services. That makes fields and error handling easier to interpret than arbitrary text formats. The IP WHOIS lookup label describes the user's registration task, while RDAP describes the protocol used here. A structured response still needs careful interpretation: machine-readable data does not make registration country equivalent to geolocation or network ownership equivalent to personal identity.

Can I use an IP WHOIS lookup for IPv6?

Yes. IANA publishes separate bootstrap information for IPv4 and IPv6, and the tool chooses according to the parsed address. Compressed IPv6 notation is supported and normalized. An IP WHOIS lookup of an IPv6 address examines its registered network; it does not test whether your device can connect using IPv6. Use the IPv6 test for a live browser reachability observation.

IPv6 test

Why do two tools show different organizations?

They may select different levels in a registration hierarchy or combine registration with geolocation, routing, or commercial datasets. They may also have different update times. Compare the actual source records, query time, and field definitions. An IP WHOIS lookup should not silently substitute a geolocation provider's organization label for a registry network name, because those values may represent different relationships.

Is reverse DNS the same information?

No. A PTR record is a name published through DNS, while an IP WHOIS lookup retrieves network registration data. The name in a PTR answer may be generic, absent, or unrelated to the legal holder's branding. Use reverse DNS lookup when your question concerns PTR records. Neither source provides a complete list of websites hosted on an address.

reverse DNS lookup

How do I preserve a useful result?

Use the copy button to retain the address, returned fields, source URL, and observation time. Include the question you were investigating and any relevant event time. Review the content before sharing it publicly. A good IP WHOIS lookup report states what the registry returned and avoids claims that the record cannot support, such as an exact home location or a verified identity behind shared traffic.

Does the registration contact identify the individual using an IP?

No. Public registration concerns address resources and organizations, with contacts subject to publication policy. A shared gateway, customer allocation or reassigned range can separate that record from the subscriber responsible for a particular connection.

Is a registered country a measured server location?

No. Registration and physical location are different kinds of evidence. A registry record can describe an organization or allocation without locating the machine serving your request. Keep it separate from an approximate geolocation response.

Why can the returned range be larger than one address?

Registration records commonly describe an allocation or assignment containing the query. A containing range does not mean every address belongs to one device or is currently reachable. Preserve the range boundaries when sharing the result.