MyIP.dogChecking…
IP WHOIS lookup
Read internet number registration data using RDAP, the structured successor to traditional WHOIS.
Read internet number registration data using RDAP, the structured successor to traditional WHOIS.
Checking…
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.
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 IP WHOIS 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. An IP WHOIS 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 IP WHOIS 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.
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. An IP WHOIS 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.
The source link opens the exact registry endpoint used for the result. The observation time tells you when this tool retrieved it. An IP WHOIS 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.
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 IP WHOIS 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.
Regional registries distribute or record internet number resources under their policies. Networks can then make more specific assignments or provide connectivity to customers. An IP WHOIS lookup can expose one level of this hierarchy without revealing every commercial relationship beneath it. A consumer's internet provider, wholesale carrier, parent organization, and registered network holder need not share the same public brand name.
Shared public addresses add another limitation. NAT, mobile gateways, enterprise proxies, and VPN exits can place many users behind one observed address. An IP WHOIS lookup cannot identify which user produced a request or how many customers shared the address at that moment. Keep registration evidence distinct from account records, authenticated activity, and service logs that might answer different parts of an investigation.
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. An IP WHOIS lookup should make the origin of its information visible, especially when a missing field could otherwise be mistaken for a negative finding.
The IP WHOIS lookup does not scan ports, test connectivity, measure latency, or detect malware. It also does not assign a fraud score. A network registered to a hosting provider may carry both ordinary and abusive traffic, while a consumer network can contain compromised devices. Registration alone cannot establish whether a particular connection is safe, authorized, or associated with a real person.
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 IP WHOIS lookup reports that condition explicitly. It does not replace a failed response with an unrelated allocation or an invented owner.
If your input is private, use local network information instead. An address like 192.168.1.1 may identify a router in one household and an entirely different router elsewhere. An IP WHOIS lookup cannot choose which local network you meant. Device settings, router configuration, and internal address management records are the appropriate evidence for those cases.
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 IP WHOIS lookup deliberately avoids presenting unrelated personal contact fields as if they identify the sender.
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.
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.
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.
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.
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.
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 an IP WHOIS lookup supports an operational decision.