Read domain registration data with an RDAP lookup
This lookup requests domain registration data through RDAP and displays selected fields returned by the service, including a registrar name, registration dates, nameservers, and status values when present. RDAP responses use a JSON structure described by RFC 9083, but records can differ and fields may be omitted. The displayed response is not a verification of who owns a domain, whether it is available, or whether its DNS currently resolves.
How to look up domain registration data
- Enter a domain name without a URL scheme or path and choose Look up registration.
- Review the fields returned by RDAP, such as registrar, dates, nameservers, and status values.
- Treat absent fields as unavailable in this response; the response may not explain why they are absent.
- Use a separate DNS lookup when you need to inspect DNS records or resolution.
When this lookup can help
- Review registration data that a domain's RDAP service makes available.
- See which registrar name, dates, nameservers, or status strings appear in a response.
- Choose a separate DNS check when investigating DNS answers or name resolution.
Frequently asked questions
Does this tool query WHOIS or RDAP?
It requests domain registration data through RDAP and displays selected values from the response. RDAP is a structured data protocol; this page does not promise a legacy WHOIS TCP query.
Which fields can appear in a result?
Depending on the response, the page can show a registrar, event dates, nameservers, and status strings. The available fields vary by record and response.
Why is a field missing?
A response may omit a field. The omission alone does not establish why it is absent, and RDAP does not guarantee that every record contains the same public data.
Do the results identify the domain owner or show whether it is available?
No. Registration fields such as registrar, dates, nameservers, and status strings do not by themselves establish ownership or availability.
Do status strings explain what is happening to a domain?
The result may display status values supplied by RDAP. Their interpretation can depend on context from the responsible registry or registrar; this page does not assign a meaning to every value.
Example result
View a fictional RDAP registration-data result
Illustrative data only. This example uses fictional registration data for example.test; opening it does not run a lookup.
Scroll the table horizontally to read every column.
| Field | Fictional value | How to read it |
|---|---|---|
| Domain | example.test | The queried name shown in this fictional response. |
| Registrar | Example Registrar | A registrar name reported in the response; it does not identify an owner. |
| Registered | 2030-01-15 | A creation date supplied by this fictional response. |
| Last changed | Not reported | This response has no updated-date value; omission does not establish why it is missing. |
| Registry expiration | 2031-01-15 | An expiration-related date supplied by this fictional response. |
| Nameservers | ns1.example.test · ns2.example.test | Names listed by this response; this is not a DNS resolution check. |
| Statuses | exampleStatus | A raw fictional status string; this example does not assign it a meaning. |
RDAP responses can differ and fields may be absent. Registrar, dates, nameservers, and status strings do not prove ownership or whether a name is available.
What the returned fields can tell you
A registrar field names a registrar reported in the response. Event dates are values supplied by the registration service and may be absent or differ by record. Nameservers and status strings are shown as registration data; a status value may need context from the responsible registry or registrar. RDAP does not guarantee a complete set of public fields, and an omitted value does not establish why it is missing. Use a separate DNS lookup to inspect DNS answers.
- Selected registration fields returned through RDAP
- Registrar, dates, nameservers, and status values when supplied
- Missing fields are not treated as proof of a particular cause
- Registration data does not establish ownership or availability
Free. No signup. Browser tools (subnet, JWT, password strength) run locally; lookup tools query public APIs (Cloudflare DoH, RDAP, certificate logs). Full per-tool breakdown at /methodology/.
Sources (2)
- Hollenbeck, S., & Newton, A. (2021). JSON Responses for the Registration Data Access Protocol (RDAP). RFC 9083, IETF (June 2021).
- Internet Corporation for Assigned Names and Numbers (ICANN) (2018). Registration Data Access Protocol (RDAP) FAQs. ICANN FAQ (31 August 2018).
These are the IETF RFCs, NIST publications, and W3C standards the tool implements or queries. Locate them on the IETF Datatracker (datatracker.ietf.org) or the official standards body.
By Marco B. ·