Select the object
A domain, IP address or ASN follows a different RDAP path and bootstrap registry.
Direct answer: An RDAP lookup returns structured registration data over HTTPS, including typed events, entity roles, statuses, notices and source links when the responding service publishes them.
The server sends the normalized domain or public IP address to the selected HTTPS RDAP service and retains the returned source link. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this rdap lookup tells you
RDAP returns typed JSON over HTTPS for domains, IP networks and autonomous systems. Use it when you need explicit event types, entity roles, notices, links and source-aware structured data rather than free-form WHOIS labels.
- Which authoritative RDAP service IANA bootstrap selected
- What statuses, events, entities and notices the service returned
- Whether a field is absent, redacted or explained by a notice
If the selected service is unclear, the RDAP bootstrap guide explains how IANA data routes domain and number-resource queries.
When the response contains registration, expiration or last-changed events, use the registration event timeline reference to keep each action attached to the correct date.
How the evidence is collected
Find the service
The client uses IANA bootstrap data rather than guessing a vendor endpoint.
Retain structure
Events keep their eventAction, entities keep their roles, and notices stay attached to the response.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| eventAction | The kind of event, such as registration, expiration or last changed. | That every timestamp is an expiry date. |
| roles | How an entity relates to the object, such as registrar or abuse. | Verified real-world identity. |
| status | Standardized object states returned by the server. | A security verdict. |
| notices / remarks | Service terms, redaction context or response-specific explanation. | Boilerplate safe to discard. |
Registration and last-changed events differ
Keep both events with their labels. The registration event describes object creation; last changed says the registration object changed, not which field changed or when the website content changed. Follow the self and related links to preserve provenance.
Common mistakes
- Flattening all events into a single date
- Displaying an entity name without its role
- Ignoring notices that explain redaction or terms
- Sending every query to one hard-coded provider
RDAP Lookup FAQ
Why does RDAP return less data than an old WHOIS record?
Public disclosure rules and server policy can limit fields. RDAP makes notices and redaction structure clearer, but it does not make private data public.
Is RDAP only for domains?
No. The protocol defines domain, nameserver, entity, IP network and autonomous-system objects.
Why is HTTPS important?
It protects the query and response in transit and enables normal web authentication and caching controls; it does not independently verify the truth of every supplied field.