WHOIS and RDAP: How to Read Domain Registration Data
A field-by-field guide to WHOIS and RDAP records, including the status codes that tell you whether a domain is locked, on hold or about to drop.

WHOIS and RDAP are two ways to look up who registered a domain, when, through which registrar, and where its DNS is hosted. WHOIS is the older plain-text protocol; RDAP (Registration Data Access Protocol) is its modern replacement that returns structured JSON and is now the primary source for generic top-level domains like .com. To read either, focus on the dates, the registrar, the status codes and the name servers, and expect personal contact details to be redacted.
Key takeaways
- Both protocols show the same core facts: creation, update and expiry dates, registrar, status codes and name servers.
- RDAP returns machine-readable JSON, supports secure HTTPS access and standardizes fields that WHOIS formatted differently per registry.
- ICANN has made RDAP the definitive source for gTLD registration data and no longer requires gTLD registries and registrars to run WHOIS.
- Since GDPR took effect in 2018, owner names, emails and addresses are usually redacted.
- Status codes such as
clientTransferProhibitedorredemptionPeriodtell you what can and cannot happen to the domain right now.
What registration data is
When someone registers a domain, three parties are involved: the registrant (the domain holder), the registrar (the company that sold the domain, such as a hosting company or domain retailer) and the registry (the operator of the top-level domain, for example Verisign for .com). The registry and registrar keep records about the domain, and WHOIS and RDAP are how those records are made publicly queryable.
WHOIS vs RDAP
| WHOIS | RDAP | |
|---|---|---|
| Format | Free-form text, varies by provider | Standardized JSON |
| Transport | TCP port 43, unencrypted | HTTPS |
| Finding the right server | Varies; often hardcoded lists | Bootstrap files published by IANA |
| Internationalization | Poor support for non-ASCII | Built in |
| Access control | None; everyone sees the same output | Supports differentiated access |
| Status for gTLDs | No longer required by ICANN | Required, definitive source |
RDAP is defined in a set of IETF standards; the JSON response format is specified in RFC 9083. Many country-code domains (ccTLDs) set their own policies, so some still offer only WHOIS or a web lookup, and their output may differ.
Reading a WHOIS record
Here is a typical WHOIS response for a .com domain, trimmed for readability:
Domain Name: EXAMPLE.COM
Registry Domain ID: 1234567_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.example
Registrar URL: https://www.registrar.example
Updated Date: 2025-08-14T07:01:31Z
Creation Date: 2012-08-13T04:00:00Z
Registry Expiry Date: 2027-08-13T04:00:00Z
Registrar: Example Registrar, Inc.
Registrar IANA ID: 9999
Domain Status: clientDeleteProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Name Server: NS1.EXAMPLEDNS.NET
Name Server: NS2.EXAMPLEDNS.NET
DNSSEC: signedDelegation
Field by field
- Creation Date: when the current registration began. If the domain once expired and was re-registered, this reflects the new registration, not the original one.
- Updated Date: the last time the record changed (renewal, name server change, contact change). It says nothing about website content.
- Registry Expiry Date: when the paid period ends. A domain is often auto-renewed around this date.
- Registrar and IANA ID: who manages the domain. This is who you contact for transfers, and where abuse reports go.
- Domain Status: EPP status codes (see below).
- Name Server: the DNS servers for the domain. These often reveal the DNS or hosting provider.
- DNSSEC: whether the domain's DNS is cryptographically signed.
unsignedis common and not an error.
Reading an RDAP response
The same information in RDAP looks like this (trimmed):
{
"objectClassName": "domain",
"ldhName": "EXAMPLE.COM",
"status": ["client delete prohibited", "client transfer prohibited"],
"events": [
{ "eventAction": "registration", "eventDate": "2012-08-13T04:00:00Z" },
{ "eventAction": "expiration", "eventDate": "2027-08-13T04:00:00Z" },
{ "eventAction": "last changed", "eventDate": "2025-08-14T07:01:31Z" }
],
"nameservers": [
{ "objectClassName": "nameserver", "ldhName": "NS1.EXAMPLEDNS.NET" },
{ "objectClassName": "nameserver", "ldhName": "NS2.EXAMPLEDNS.NET" }
],
"secureDNS": { "delegationSigned": true },
"entities": [
{ "objectClassName": "entity", "roles": ["registrar"],
"publicIds": [{ "type": "IANA Registrar ID", "identifier": "9999" }] }
]
}
The mapping is straightforward: events holds the dates (registration, expiration, last changed), status holds the status codes in lowercase words, nameservers lists DNS servers, and entities holds the registrar and any contacts, each with a roles array. Because it is JSON, scripts can read it reliably without guessing at text formats.
Status codes worth knowing
Status codes come from the EPP protocol registries use. "Client" codes are set by the registrar; "server" codes are set by the registry.
| Status | What it means |
|---|---|
ok / active | No restrictions; normal state. |
clientTransferProhibited | Transfer lock is on. Common and good: it protects against hijacking. Remove it at your registrar before transferring. |
clientHold / serverHold | The domain is not published in DNS, so the website and email stop working. Often caused by non-payment, unverified contact details or an abuse case. |
autoRenewPeriod | The domain passed expiry and was auto-renewed by the registry; the registrar may still cancel it if the owner does not pay. |
redemptionPeriod | The domain was deleted after expiry. The original owner can usually still restore it, typically for a fee. |
pendingDelete | The domain is about to be released and cannot be restored. It will soon be available to register again. |
pendingTransfer | A transfer to another registrar is in progress. |
The exact lengths of grace and redemption periods depend on the registry and registrar, so check your registrar's terms rather than relying on a general rule.
Privacy and redaction
Since the EU's GDPR took effect in May 2018, most registrars redact personal data for gTLD domains. You will often see "REDACTED FOR PRIVACY", a privacy service's details, or a web form link instead of an email address. The registrant's organization and country/state may still be shown in some cases. Many ccTLD registries have their own privacy rules.
If you need to reach a domain owner for a legitimate reason, use the contact form or anonymized email the record provides. For abuse such as phishing or malware, contact the registrar's abuse address, which is shown in the record.
Practical uses
- Before buying a domain: check the creation date and status. A recent creation date on a domain sold as "aged" suggests it dropped. You can confirm quickly with a Domain Age Checker.
- Protecting your own domain: confirm the expiry date is far enough away, transfer lock is on and the name servers are the ones you expect.
- Troubleshooting a site that went offline: look for
clientHold,serverHoldor an expiry date that has passed. - Vetting a vendor or a suspicious email: a domain registered last week that claims to be an established bank is a red flag.
- Finding the DNS provider: name servers tell you where to make DNS changes.
To run a lookup, enter the domain in a Whois Checker. For gTLDs you can also query RDAP directly through the registry's RDAP service listed in IANA's bootstrap file.
Querying RDAP from the command line
RDAP is plain HTTPS, so any HTTP client works. Requests follow a simple pattern: the RDAP base URL for the TLD, then /domain/ and the domain name. A request looks like this:
curl -s -H "Accept: application/rdap+json" \
"https://rdap.registry.example/domain/example.com"
Replace the base URL with the one IANA's bootstrap file lists for the TLD you are checking. The registry's response sometimes includes a links entry pointing to the registrar's own RDAP server, which can hold extra registrar-level details. If you get a 404, the domain is usually not registered; a 429 means you are being rate limited and should slow down.
Common mistakes
- Treating "Updated Date" as the date the website was last changed.
- Assuming the creation date is the original registration, even after a drop and re-registration.
- Panicking about
clientTransferProhibited; it is a normal security lock. - Letting the registrant email go stale, then missing renewal and verification notices.
- Assuming every TLD follows the same rules; ccTLDs vary.
Quick checklist
- Expiry date at least several months away, with auto-renew on.
- Transfer lock enabled unless you are moving registrars.
- Name servers match your current DNS provider.
- No
holdstatuses on the domain. - Registrant contact email current and monitored.