What Domain RDAP Lookup helps you do

Inspect public domain registration data, lifecycle dates, status codes, registrar details and nameservers through RDAP. It is the structured replacement for WHOIS lookups. The query goes through the public rdap.org bootstrap service, which redirects it to the registry responsible for the domain.

The domain you enter is sent to the public rdap.org bootstrap service to retrieve registration data. Haivix does not store the query.

How it works

Most tools here are offline calculators: the address math, RAID capacity, permission bits, TCP window sizing and transfer-time estimate all run in your browser with no request. The RDAP lookup is the exception, because registration data lives in public registries and the domain must be sent to a lookup service. Unit conventions matter throughout: a megabyte may mean 1,000,000 or 1,048,576 bytes, and a megabit is always one eighth of a megabyte. These are reference models, not live checks, so a port can be listed without a service running, a permission mode can be valid without being appropriate, and a RAID estimate can differ from formatted capacity.

How to use Domain RDAP Lookup

Enter a domain name such as example.com.
Run the lookup and wait for the registry response.
Read the registrar, dates, statuses and nameservers.
Copy the details for a ticket or investigation.

When to use it

Check when a domain was registered or expires.
See which registrar and nameservers a domain uses.
Investigate the status of a domain before a purchase.
Verify delegation before changing DNS.
Check whether a domain is in a redemption or hold state.
Collect registration facts for an incident report.

When not to use it

Do not use it for IP or ASN registration data; this tool queries domains only.
Do not expect owner details; privacy rules usually redact them.
Do not rely on it as legal proof of ownership.

Example

A lookup returns the registrar, the creation and expiration dates, the status list and the delegation nameservers. A pasted URL such as https://example.com/path is normalized to example.com before the query. A domain with no public record returns a not-found message rather than an empty table.

What you can do with Domain RDAP Lookup

Look up a registered domain.
Normalize a pasted URL into a domain.
Show registrar and registry handle.
Show registration, update and expiry dates.
List status codes and nameservers.
Copy a plain-text summary of the record.

Example: check the model against the live system

Note the unit convention before comparing figures. Mbps and MB/s differ by a factor of eight, and MB and MiB differ by about 5 percent.

Treat a lookup as a starting point. A port reference, a permission mode and a RAID calculation all describe expectations, not the state of a running host.

Confirm on the system itself where it matters: ss or netstat for listeners, ls -l for permissions, the controller utility for array status.

Keep RAID in perspective. It protects against a disk failure, not against deletion, corruption, ransomware or a lost site.

Record the inputs alongside the result so a later comparison uses the same assumptions.

Check the time unit on latency. A round-trip time is usually milliseconds, and entering seconds changes the bandwidth-delay product by a factor of a thousand.

Treat registry data as a snapshot. RDAP records can be redacted, cached or updated after a transfer, so confirm ownership and expiry with the registrar.

What to know before you start

The lookup is sent to the public rdap.org bootstrap service, which sees the query.
Privacy rules mean owner details are often redacted in the response.
Data is supplied by registries and may be delayed or incomplete.
It does not query IP, ASN or nameserver objects.

Common mistakes

Entering a full URL with a path and expecting it to be used verbatim.
Looking up a subdomain instead of the registrable domain.
Assuming a redacted record means no owner exists.
Treating a cached or delayed record as real-time truth.

Troubleshooting

If no record is found, the domain may be unregistered or the registry may not publish RDAP.

If the lookup fails, the service may be rate-limiting or offline.

If dates are missing, the registry may not publish them.

If the domain is invalid, check for a valid top-level suffix.

Domain RDAP Lookup