Domain and IP Lookup
Look up a domain's RDAP registration data or an IP address's network and location.
What this lookup does
Read a domain's registration record through RDAP: registrar, status, registration and expiry dates, nameservers and DNSSEC signing. Or geolocate a public IP address: city, region, country, timezone, network and ASN. Both answers come from fixed public services, not from a service the input can choose.
How to use it
Choose whois and enter a domain such as example.com, or choose ip and enter a public address such as 8.8.8.8. RDAP is the structured successor to port-43 whois, so the result is fields rather than free text. Geolocation is approximate by nature; it describes the network's registered location, not the device's position.
Privacy and safety
The lookup runs on the tool server: the domain or address you enter is sent to RDAP or the geolocation provider for this request. Private and reserved addresses are refused, and the request target is a constant service, so the input cannot redirect it at an internal host.
Pick an action and enter a target. With whois it reads a domain's registration record from RDAP; with ip it geolocates a public address and names the network it belongs to.
The whois half asks `rdap.org`, which forwards to the registry for the domain's top-level domain, so a .uk and a .com return records from different registries in the same shape. A domain with no RDAP record comes back labelled as not found rather than as an error.
The ip half asks `ipwho.is` first and falls back to `ipinfo.io` when the first answer is not usable. Only globally routable addresses are accepted, so a private or loopback address is refused before any request is made.
What each action returns
The whois result carries the registrar, the status flags, the registration and expiry dates, the nameservers, and whether the registry marks the delegation as signed. A field the registry does not publish is reported as absent rather than filled in.
The ip result carries city, region, country, postal code, latitude and longitude, timezone, and the network's ASN and organisation where the service supplies them. The `source` field names which of the two services answered.
A 404 from RDAP is a real answer: the domain has no registration record there. Any other HTTP status is reported as a failure with the code.
- whois: RDAP registration data for a domain
- ip: city, region, country, coordinates, ASN, organisation
- A private or reserved address is refused, not looked up
Why a lookup can fail or age
Both services are third parties. A redirect to a registry that is slow or down, or a service that is rate limiting, produces a failure sentence rather than a stale record, and the page has no cache to fall back to.
Geolocation is approximate by nature. An address can be reported in a neighbouring city, and a VPN exit is reported where the exit is, not where the user is.
How to use the action choice
Pick the whois action and enter a domain, or the ip action and enter a public address, then run. The target is validated first: a private or loopback address is refused before any request.
Whois returns the RDAP registration or a not-found label; ip returns geolocation and network from `ipwho.is` with `ipinfo.io` as fallback. Requests run from the tool server, not the tab.
What to Expect
Best for
- Reading a domain's registrar and expiry date
- Checking where a public IP address is registered
- Finding the ASN and organisation behind an address
Not ideal for
- Private, loopback, link-local or reserved addresses, which are refused
- A registry that does not publish RDAP, where the record will be missing
- Proving where a person is, since a VPN or a mobile carrier breaks the mapping
What this tool keeps
- The registry's own dates and status flags, unedited
- The service name that answered the IP half
- A not-found answer for a domain with no RDAP record, distinct from a failure
What may need cleanup
- A geolocated city that is the network's hub rather than the user's town
- An organisation name that is the host's rather than the account holder's
- A record from a registry that lags a recent transfer
Common errors
- Looking up 192.168.1.1 and reading the refusal as a service outage
- Treating the country of an IP as the country of the person
- Reading a not-found answer as a tool failure
Example use cases
- Checking who registers a domain before contacting them
- Identifying the network behind an address in a log
- Confirming a domain's expiry date before a renewal
Sample input
Choose ip and enter the public address 8.8.8.8.
Sample output
A record naming the city, country, coordinates, ASN and organisation for that address, with `ipwho.is` as the source.
Who this is for
- System administrators tracing an address
- Security analysts checking a domain's registration
- Anyone who needs an ASN or an expiry date quickly
Frequently asked questions
What does each action return?
whois reads a domain's registration record from RDAP; ip geolocates a public address and names the network it belongs to.
Can I look up a private or loopback address?
No. Private, loopback, link-local and reserved addresses are refused.
Why does the city look wrong?
A geolocated city is often the network's hub rather than the user's town, and a VPN or mobile carrier breaks the mapping.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.