WHOIS / RDAP Lookup

Current record

{{ sourceUsedLabel }} {{ registrarBadgeLabel }} {{ expiryBadgeLabel }} Created {{ summary.created }} {{ statusBadgeLabel }}

Domain:

Enter one bare domain such as example.com; pasted URLs are reduced to the host.

Lookup source order:

RDAP first fits most registries; use WHOIS first to compare fallback coverage.

Lookup timeout:

Range: 2500-15000 ms in 500 ms steps; raise for slow registries.

Field	Value	Copy
{{ row.label }}	{{ row.value }}
No lifecycle fields available The selected lookup source did not return registration dates or status fields for this domain.

Field	Value	Copy
{{ row.label }}	{{ row.value }}
No public contact fields returned Registry privacy or RDAP redaction can hide registrant, admin, technical, and billing contact values.

Field	Value	Copy
{{ row.label }}	{{ row.value }}
No nameserver fields returned The WHOIS or RDAP source did not publish nameserver fields in this response.

Field	Value	Copy
{{ row.label }}	{{ row.value }}
No registrar profile fields returned Try the WHOIS-first fallback if the RDAP source omits registrar contact fields.

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Domain registration data explains the administrative state of a domain name. It can show the registrar, registry status codes, registration dates, expiry date, nameserver set, public contact roles, and source record used for the lookup. That information matters before a renewal, transfer, incident response, ownership review, or DNS delegation check.

RDAP is the structured successor to WHOIS. It returns registration data as machine-readable records, while traditional WHOIS data is often flatter, less consistent, and more dependent on provider parsing. Public contact data may still be redacted or absent, so a registration lookup is strongest when dates, status, registrar, and nameservers all tell a consistent story.

A registration lookup does not ask the live DNS zone for current address records. Nameservers in registration data describe delegation and registrar-facing records. Live DNS can still fail because a nameserver is unreachable, a zone is misconfigured, or a status code blocks publication.

The safest first reading is simple: confirm the domain, source used, registrar, expiry date, current statuses, and nameservers. Use public contact rows only when they appear, and treat blank registrant or administrative fields as normal when privacy rules or registry policy redact them.

How to Use This Tool:

Use one bare domain name per lookup. Pasted URLs are reduced to their host, and invalid domain shapes are rejected before any public registration request is made.

Enter a domain such as example.com in Domain. Avoid paths, query strings, email addresses, and private notes.
Keep RDAP first, WHOIS fallback for most checks. Use RDAP only when you want structured registry data only, or WHOIS first when comparing provider fallback coverage.
Adjust Lookup timeout only when slow registries need more time or incident triage needs a faster failure. The accepted range is 2500 to 15000 milliseconds.
Run Lookup and read the summary badges for source, registrar, expiry state, creation date, and status.
Open Registration Lifecycle for dates, status, age, and days to expiry. Use Registrant Contacts, Name Server Set, and Registrar Profile for the public fields returned by the selected source.
If expected contact or registrar fields are missing, try the alternate source order before assuming the data is unavailable everywhere.
If the lookup fails, confirm the domain has at least two labels, contains only letters, digits, and hyphens in each label, and is not an internal-only name.

For renewal or transfer review, copy the domain, registrar, status, expiry date, days to expiry, and nameservers into your ticket before investigating live DNS records separately.

Interpreting Results:

The lifecycle fields carry the highest operational value. Expires and Days to Expiry show renewal urgency. Status can reveal locks, holds, pending transfer states, or deletion-related states. Nameservers should match the DNS host you expect to serve the zone.

RDAP source usually means the record came from a structured registry path and is easier to compare across domains.
WHOIS fallback can fill gaps, but field names and contact completeness depend on the provider's parsed record.
Blank contact rows often mean privacy redaction, not a broken domain.
Nameserver rows show delegated servers in registration data. Confirm live resolution with DNS tools when outage symptoms involve actual records.

Technical Details:

Registration data access has two different traditions. WHOIS began as a simple text lookup service and never produced one universal response shape. RDAP defines HTTP query patterns and JSON responses for domains, nameservers, entities, IP networks, and autonomous systems, which makes domain lifecycle data easier to parse and compare.

For domains, RDAP base services are located through IANA bootstrap data for the top-level domain. Once a domain record is returned, events, statuses, nameservers, and entity roles are mapped into user-facing sections. A WHOIS provider fallback can be useful when an RDAP service is missing, incomplete, unreachable, or intentionally limited.

Lookup Core

The lookup accepts a host-shaped domain, normalizes it to lowercase, strips schemes and paths, removes leading or trailing dots, and rejects names that do not fit the visible domain pattern. The selected source order then determines whether RDAP is attempted first, RDAP is required, or a WHOIS provider is attempted before RDAP fallback.

Registration lookup source modes
Source order	First attempt	Fallback behavior	Best use
`RDAP first`	Structured RDAP record for the domain's top-level domain	WHOIS provider if RDAP does not return a usable record	Default checks where structured data is preferred.
`RDAP only`	Structured RDAP record	No WHOIS fallback	Audits that require standards-shaped RDAP output.
`WHOIS first`	Parsed WHOIS provider data	RDAP if the provider result is unusable	Comparing legacy-style coverage against RDAP fields.

Formula Core

Registration dates are copied from the public source, while age and expiry runway are computed from timestamps. Both day counts are convenience values for triage, not separate registry facts.

\begin{array}{l} ageDays & = & floor (\frac{now - createdAt}{86400000}) \\ daysToExpiry & = & max (0, ceil (\frac{expiresAt - now}{86400000})) \end{array}

ageDays floors partial days after creation. daysToExpiry rounds up remaining partial days and never displays a negative value, so expired or same-day domains appear as zero days remaining.

Domain registration fields and caveats
Field group	Typical source data	Interpretation caveat
Lifecycle	Creation, update, expiry, status, provider age	Different registries name events differently, and some dates may be omitted.
Contacts	Registrant, administrative, technical, and billing roles	Public privacy rules often remove personal or organization details.
Nameservers	Delegated hostnames published in registration data	Delegation records can differ from live answers served by the zone.
Registrar profile	Name, IANA identifier, URL, email, phone when present	Registrar branding can vary; the IANA identifier is the more stable clue when present.
Status	RDAP status values or WHOIS status text	Status codes need domain-specific reading, especially hold, lock, redemption, and pending states.

Accuracy and Privacy Notes:

The entered domain is sent to public registration-data services selected by the source mode. Do not use this lookup for confidential internal names, investigation notes, unpublished acquisition targets, or private customer context.

Registration data can be redacted, delayed, incomplete, or unavailable for some top-level domains.
Status codes indicate registry or registrar state, not the full health of the website or mail service.
Nameserver data should be compared with live DNS checks before changing outage or delegation plans.
WHOIS fallback output depends on the provider's parsed record shape and may not expose the same fields as RDAP.

Worked Examples:

A renewal review for example.com starts with RDAP first. The summary shows the registrar and expiry state, while Registration Lifecycle gives Expires and Days to Expiry. If the days remaining are low, verify the registrar account rather than relying only on the public lookup.

A transfer check finds a status that includes a lock-like or pending state. The domain may be protected from transfer, waiting for an operation, or blocked by a registry condition. Use the status text as a clue, then confirm the exact meaning with the registrar or ICANN status documentation.

An expected registrant email does not appear in Registrant Contacts. That is common with privacy redaction. Try WHOIS first to compare coverage, but rely on registrar profile, status, and nameserver rows when public contact details remain absent.

FAQ:

Why are registrant contacts blank?

Many registries and registrars redact public contact data. Blank contact rows usually mean the selected source did not publish those fields, not that the domain record is broken.

Does this show live DNS records?

No. Nameserver rows come from registration data. Use a DNS record lookup to confirm live A, AAAA, MX, TXT, and other zone records.

Why try WHOIS after RDAP?

RDAP is structured and preferred, but some domains have incomplete or unavailable RDAP records. WHOIS fallback can sometimes return registrar or lifecycle fields that the RDAP path did not expose.

What does an invalid-domain error mean?

The input must be a host-shaped domain with at least two labels. Remove paths, ports, emails, spaces, leading dots, trailing dots, and unsupported characters before running the lookup again.

Glossary:

RDAP: Registration Data Access Protocol, a structured HTTP and JSON protocol for public registration records.
WHOIS: A legacy registration lookup service whose text responses vary by registry, registrar, and provider.
Registrar: The organization sponsoring the domain registration on behalf of the registrant.
Registry status: A domain state such as lock, hold, pending transfer, redemption, or normal operating status.
Nameserver set: The delegated DNS servers published in registration data for the domain.

References:

Registration Data Access Protocol Query Format, RFC Editor, June 2021.
JSON Responses for the Registration Data Access Protocol, RFC Editor, June 2021.
Requirements for RDAP Servers providing Domain Name Data, IANA.
RDAP Bootstrap Registry Data, IANA.
EPP Status Codes, ICANN, June 16 2014.