Skip to content
AdminKit

How do you read a WHOIS or RDAP lookup result?

AdminKit's WHOIS/RDAP lookup returns different fields depending on the target: for a domain, its registrar, key dates (registration, last changed, expiry), status codes controlling transfer or deletion, and its authoritative nameservers; for an IP address, the allocated block, the assigned organization, and the regional registry that manages it.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • A domain lookup answers “who sponsors this name, until when, under which locks, and which nameservers answer for it”. An IP lookup answers “which network holds this address block, and which regional registry manages it”.
  • RDAP returns the same data WHOIS always did, but as structured JSON: people and companies sit in entities with roles, dates sit in events, and locks sit in status.
  • client transfer prohibited (EPP clientTransferProhibited) is a normal protective lock. server hold, redemption period or pending delete on a domain you rely on needs attention.
  • Redacted registrant fields are the normal case for gTLDs, not a warning sign. The registrar, dates, status and nameservers stay public.
  • The two cheapest trust checks are the registrar name and the nameserver list: both should match what you set up.

Why does a lookup result have so many fields?

Because a single record answers several unrelated questions at once. As a registration-data companion to the record-level lookups in AdminKit’s DNS cluster, this guide covers a single WHOIS or RDAP query, which packs together several unrelated pieces of information: who registered a name, when, through which company, under what restrictions, and which servers answer for it. That breadth is intentional — the original WHOIS protocol (RFC 3912) was designed in an era when “who do I contact about this domain or IP block” was the whole point, and registries have kept extending the same record ever since rather than splitting it into separate lookups.

RDAP, the modern replacement (specified in RFC 9083 and described for registrants on the ICANN RDAP page), carries the same categories of data but as structured JSON instead of loosely formatted text, which is what lets a tool like AdminKit’s Whois / RDAP lookup parse and label each field reliably instead of guessing at a registry-specific text layout. Legacy WHOIS has no schema at all: RFC 3912 only defines a TCP connection to port 43, a query line, and free text back.

How does a lookup find the right registry?

Through a bootstrap step that maps the thing you typed to the registry that holds it. RFC 9224 defines bootstrap files that IANA publishes, such as the IANA bootstrap registry for domain names, which lists the RDAP base URL for each top-level domain. Similar files cover IPv4 blocks, IPv6 blocks and AS number ranges, each pointing at one of the five regional internet registries.

AdminKit’s tool sends your query from the browser to rdap.org, a public bootstrap and proxy service that performs this routing for you. Regional registries run bootstrap servers as well: ARIN’s RDAP documentation explains that a client simply sends RDAP queries to such a server and receives HTTP redirects to the authoritative one. The query paths themselves come from RFC 9082:

You look upRDAP pathWho answersObject returned
A domain name/domain/example.comThe TLD’s registry, often with a link to the registrar’s own RDAP serverdomain
An IPv4 or IPv6 address/ip/192.0.2.10 or /ip/2001:db8::1The regional internet registry for that blockip network
An AS number/autnum/64500The regional internet registry that assigned itautnum
A nameserver/nameserver/ns1.example.netThe registry, where it supports this querynameserver

AdminKit’s lookup accepts a domain or an IP address. AS numbers are queried directly against a registry’s RDAP service with the autnum path above.

What does a domain RDAP response look like?

A JSON object whose top level describes the domain, with nested arrays for the parties, dates and servers attached to it. The example below is trimmed to the members that matter when reading a result.

Example output (illustrative, documentation names and addresses):

{
  "objectClassName": "domain",
  "ldhName": "example.com",
  "status": ["client transfer prohibited", "client delete prohibited"],
  "events": [
    { "eventAction": "registration", "eventDate": "2019-03-14T09:21:07Z" },
    { "eventAction": "last changed", "eventDate": "2026-02-02T17:40:51Z" },
    { "eventAction": "expiration",   "eventDate": "2027-03-14T09:21:07Z" }
  ],
  "entities": [
    {
      "objectClassName": "entity",
      "roles": ["registrar"],
      "vcardArray": ["vcard", [["fn", {}, "text", "Example Registrar, Inc."]]],
      "entities": [
        {
          "objectClassName": "entity",
          "roles": ["abuse"],
          "vcardArray": ["vcard", [["email", {}, "text", "abuse@example.net"]]]
        }
      ]
    }
  ],
  "nameservers": [
    { "objectClassName": "nameserver", "ldhName": "ns1.example.net" },
    { "objectClassName": "nameserver", "ldhName": "ns2.example.net" }
  ]
}

Read it from the outside in. objectClassName tells you what kind of object came back. entities holds every party, each tagged with one or more roles; RFC 9083 §10.2.4 defines values such as registrant, technical, administrative, abuse and registrar. Contact details live inside each entity’s vcardArray, a JSON form of a vCard where fn is the display name. Entities can nest, which is why the registrar’s abuse contact often appears inside the registrar entity rather than at the top level. events (§4.5) is a list of actions with timestamps, and an event may be dated in the future, which is how expiry is expressed. status (§4.6) is the list of locks and states.

Where a field sits in the JSON, and what AdminKit’s tool shows for it:

What you wantWhere it is in RDAPShown by AdminKit’s tool
Registrarentity with role registrar, fn in its vCardRegistrar
Created, changed, expiry datesevents with registration, last changed, expirationRegistered, Last changed, Expires (with days left)
Locks and statesstatusStatus
Authoritative nameserversnameservers[].ldhNameNameservers
Abuse contactentity with role abuseOnly in the raw RDAP JSON

For the abuse contact specifically, see finding the abuse contact in a WHOIS/RDAP result.

Which domain fields matter most?

The registrar, the expiry date, the status codes and the nameservers. Everything else is context.

Registrar. The company the domain is registered through — not necessarily who runs the website, which can be a different provider entirely. If you don’t recognize the registrar name on a domain you believe you control, that’s worth investigating immediately; it’s also the first field worth checking against a seller’s claims before buying a domain, as our domain portfolio owners and buyers page covers.

Key dates. Registration date, last-updated date, and expiry date. The expiry date is the one with real consequences: once it passes without renewal, most registries put the domain through a grace period and then release it for anyone to register. Losing a domain this way requires no attack at all, just a missed renewal — see our guide on domain expiry and renewal for the realistic timeline and how to avoid it. RDAP dates are in UTC (the trailing Z), so a domain can expire on a different calendar day than your local clock suggests. A last changed date you can’t account for is worth a closer look, since it records any update to the registration.

Status codes. These are standardized EPP codes, not free text, so the same code means the same thing regardless of registrar or registry. clientTransferProhibited and clientDeleteProhibited are locks your registrar applies, usually on by default, that block an unauthorized transfer-away or deletion — a protective feature you want to see present, not a warning sign. Status codes starting with server instead of client are set by the registry itself and more often indicate a dispute, a policy action, or a domain already moving through deletion.

Nameservers. The authoritative nameservers listed here are what actually control where the domain’s DNS records (A, MX, TXT and so on) are published. These should match what you configured with your DNS provider; a nameserver you didn’t set is one of the clearest signs of a hijack at the registrar level, distinct from a router-level DNS hijack — see is my router’s DNS hijacked? for that separate failure mode.

What do the domain status codes mean?

Each one is either a lock, a hold or a lifecycle state. Registries manage domains with EPP, and RFC 8056 maps each EPP code to an RDAP value written in lower-case words. That is why the same lock reads clientTransferProhibited in WHOIS text and client transfer prohibited in RDAP JSON. ICANN’s EPP status code reference notes that server codes are set by registries and take precedence over client codes.

EPP codeRDAP valueSet byWhat it means for you
okactiveRegistryNo pending operations or prohibitions. Normal.
clientTransferProhibitedclient transfer prohibitedRegistrarTransfer lock. Normal and protective; your registrar removes it when you move the domain.
clientHoldclient holdRegistrarThe domain is not published in DNS, so it stops resolving. Ask your registrar what triggered it.
serverHoldserver holdRegistrySame effect, imposed by the registry. Ask your registrar why.
redemptionPeriod / pendingDeleteredemption period / pending deleteRegistryThe domain has been deleted and is on its way out. Restore during redemption if you still can.

serverTransferProhibited, serverUpdateProhibited and serverDeleteProhibited together usually come from a registry lock service that the registrant asked for on purpose. On a high-value domain that is a good sign; just confirm you know who can lift it.

What does an IP or ASN lookup return?

A registration for the network, not for a name. An RDAP lookup for an IP address returns different information: the allocated address range it falls within, the organization that range is assigned to, and which regional internet registry (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC) manages it. This is useful for a different kind of question than a domain lookup answers — not “who owns this name” but “who operates this network,” which matters when you’re trying to judge whether traffic from an address looks like a residential ISP, a cloud provider, or something else. AdminKit’s DNS lookup tool complements this by resolving a domain to the IP addresses it currently points at, so you can chain the two lookups together.

Example output (illustrative, documentation addresses):

{
  "objectClassName": "ip network",
  "handle": "EXAMPLE-NET-1",
  "startAddress": "192.0.2.0",
  "endAddress": "192.0.2.255",
  "ipVersion": "v4",
  "name": "EXAMPLE-NET",
  "type": "ASSIGNED PA",
  "country": "NL",
  "status": ["active"]
}

AdminKit’s tool shows the range (startAddress to endAddress), the name or holder, the country and the status. Three cautions apply. The range is the registered block, which can be far larger than the one customer using your address. The country is where the block is registered, not necessarily where the server sits. And name is often a network label chosen by the holder, so the organization behind it may only be visible in the entities list.

An ASN lookup returns an autnum object with startAutnum, endAutnum, a name and its own contacts. It tells you which organization runs the network that announces a route, which is useful when an IP block has been sub-assigned to a customer you can’t identify. See ASN for what the number represents.

Why is some registration data redacted?

Because privacy law and ICANN policy require registrars to withhold personal data from public output. Since the EU’s GDPR took effect, most registrars operating globally redact registrant personal data (name, email, phone, postal address) from public WHOIS/RDAP output by default, replacing it with a privacy-proxy service’s contact details or an empty field. This applies most consistently to individual registrants; organizational registrants are more likely to have their business name remain visible, since the legal protection is narrower for a company than a natural person. A redacted result is the normal, expected case today — it does not by itself indicate anything suspicious about the domain.

For gTLDs, ICANN’s Registration Data Policy sets out which elements must be redacted where redaction applies, requires the output to show that a value is redacted rather than silently omitting it, and requires registrars to publish an email address or web form that relays messages to the registrant without revealing who they are. RFC 9537 gives RDAP a standard way to say what was withheld:

Example output (illustrative):

"redacted": [
  {
    "name": { "description": "Registrant Name" },
    "postPath": "$.entities[?(@.roles[0]=='registrant')].vcardArray[1][?(@[0]=='fn')][3]",
    "method": "emptyValue",
    "reason": { "description": "Server policy" }
  }
]

The method tells you how the value was hidden: removal, emptyValue, partialValue or replacementValue. An empty registrant name with a matching redacted entry is policy at work, not a broken record. Country-code TLDs set their own rules, so a ccTLD result may show more or less than a gTLD one.

How do you use a result as a quick trust signal?

Check the registrar and the nameservers first. None of this is a substitute for a dedicated security check, but a WHOIS/RDAP result gives you two cheap sanity checks worth running on any domain you’re relying on: does the registrar match who you actually registered through, and are the nameservers the ones you configured. Both are fields an attacker who compromises a registrar account would typically change, so an unexpected value in either is worth investigating before you trust anything else about the domain. For a deeper look at whether a domain’s current DNS configuration has actually been tampered with — rather than just its registration record — pair this with is my router’s DNS hijacked?, which also covers the registrar/provider-level case.

MisreadingWhat the field actually says
“The registrar runs the website”It only sponsors the registration. Hosting is whoever the A/AAAA records point at.
“Transfer prohibited means something is wrong”It is the default protective lock on most domains.
“Redacted means the owner is hiding something”Redaction is the default for personal data under current policy.
“The IP’s country is the server’s location”It is the country recorded for the block’s registration.
“Last changed means the owner changed DNS”It covers any registration update, including registrar-side changes.

If you’re weighing AdminKit’s live-only Whois/RDAP lookup against tools that also keep historical snapshots or offer paid monitoring, see how AdminKit compares to who.is, whois.com and MXToolbox.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

What's the difference between a WHOIS and an RDAP lookup?

WHOIS is an old, text-only protocol (RFC 3912) with no standard output format, so every registry formats its reply slightly differently. RDAP is its IETF-standardized successor, returning the same category of registration data as structured JSON over HTTPS with a consistent schema (RFC 9082 for the query format, RFC 9083 for the JSON response), which is why AdminKit's lookup tool and most modern tooling query RDAP rather than legacy WHOIS.

Why is the registrant's name or email hidden in the result?

Most registrars redact personal registrant data by default under privacy rules such as GDPR, replacing the name, email and address fields with a privacy-proxy placeholder or an empty field. Organizational registrants — companies that register a domain in their business name — are more likely to remain visible, since the redaction obligation is narrower for them. This is normal, not a sign anything is wrong with the domain.

What do status codes like clientTransferProhibited actually mean?

These are EPP (Extensible Provisioning Protocol) status codes that the registry or registrar attaches to a domain to control what can happen to it. clientTransferProhibited and clientDeleteProhibited are locks your own registrar sets, usually by default, to stop an unauthorized transfer or deletion — they are a protective feature, not a problem. serverHold or pendingDelete, by contrast, usually signal a registry-level dispute, policy violation, or expiration already under way, and are worth investigating if you see them on a domain you control.

Can I tell if a domain was hijacked just from a WHOIS/RDAP result?

It gives you two useful signals, not a verdict: whether the registrar and nameservers listed are the ones you actually set up, and whether an expected security lock (like clientTransferProhibited) is still in place. A registrar you don't recognize, nameservers you didn't configure, or a lock that disappeared without your action are all strong signs something changed without your knowledge — see our guide on DNS hijacking for how to confirm and respond.

Why does a lookup sometimes return no result at all?

Two common reasons: the domain genuinely isn't registered, or you're querying a registry that hasn't deployed RDAP yet and only supports legacy WHOIS (a shrinking but not zero set, years after the push to migrate). For an IP address, a missing result usually means the address falls in a reserved or not-yet-allocated range rather than one assigned to an organization.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.