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.