RDAP Lookup & WHOIS Checker

Free WHOIS and RDAP Domain Lookup

The Utiliverse WHOIS Lookup retrieves public domain-registration information using RDAP, or Registration Data Access Protocol. RDAP is the modern standardized replacement for older text-based WHOIS and can return structured data such as registrar, registration and expiration events, nameservers, domain status codes, DNSSEC information, registry identifiers, and public entity information.

Not every registry returns the same fields. Privacy rules, privacy-protection services, and registry policy can limit public contact details, so a missing registrant name does not necessarily mean the record is incomplete.

How to Use the WHOIS Lookup

Enter a domain or URL

Type a domain such as example.com or paste a full URL. Utiliverse removes the scheme, path, query string, port, and leading www prefix before performing the lookup.

Run the RDAP lookup

The browser sends the domain to the public RDAP bootstrap service at rdap.org, which routes the request to the appropriate registry RDAP service. No API key is embedded in the page.

Check the registrar

The registrar field identifies the organization responsible for managing the registration when that information is returned. An IANA registrar identifier is displayed when available.

Review important dates

Registration, expiration, and last-updated events are converted into readable dates. Utiliverse also estimates domain age and the amount of time remaining until the reported expiration date.

Inspect domain status codes

EPP status codes describe registration controls and pending operations. Transfer-prohibited or update-prohibited statuses are often security locks, while other statuses may describe deletion, renewal, or registry actions.

Check nameserver delegation

The nameserver list shows DNS servers delegated for the domain by the registry. This is useful when checking a DNS-provider migration or registrar configuration.

Check DNSSEC

When secure-DNS information is returned, the tool reports whether the registry delegation is signed. This is a registry-level indicator and not a complete end-to-end DNSSEC validation test.

View raw RDAP JSON

Use Raw RDAP to inspect the complete structured response, including registry-specific fields, notices, links, entities, and remarks that may not appear in the summary cards.

RDAP & WHOIS Lookup Quick Reference

This page uses live RDAP data to answer the domain-registration questions people often associate with WHOIS. RDAP is structured JSON delivered over HTTPS, while traditional WHOIS is an older text-oriented protocol. The summary below reflects what this tool can actually retrieve and display.

What is an RDAP lookup?

RDAP stands for Registration Data Access Protocol. It returns domain-registration data over HTTPS as structured JSON. This page sends the normalized domain to rdap.org, which routes the request to the relevant registry RDAP service, then summarizes the result into registrar, dates, status codes, nameservers, DNSSEC, registry handle, and selected entity information.

RDAP vs. WHOIS

WHOIS is the traditional term and legacy protocol for registration lookups. RDAP is the modern structured successor used by this tool. The practical goal is similar—finding registration information—but RDAP provides standardized JSON, clearer status semantics, HTTPS transport, and better support for differentiated access and redaction.

Domain registry WHOIS and registrar WHOIS lookup

The registry and registrar play different roles. The registry operates the top-level-domain database, while the registrar manages the customer's registration relationship. This tool can display registry-level information such as handle, statuses and delegation data, and it can identify the registrar entity when the RDAP response exposes that role.

Why registrant details may be hidden

Public RDAP records often omit or redact personal contact information. Privacy law, registry and registrar policies, proxy/privacy services, and differentiated-access rules can all limit what is returned publicly. A hidden registrant name does not mean the domain lacks an owner or registrant.

Lookup Methodology, RDAP Interpretation, and Important Limits

The tool normalizes the entered value to a hostname, performs a basic domain-format check, then requests https://rdap.org/domain/<domain> with an RDAP/JSON Accept header. The returned structured JSON is summarized into registrar, registration events, nameservers, DNSSEC, status codes, registry handle, and selected entity information.

Worked example: URL normalization

Worked example: domain age and expiry wording

RDAP is live external data, not a local registry database

The page does not ship with registration records. Every lookup depends on rdap.org and the authoritative registry/registrar RDAP services behind it. Network failures, rate limits, unsupported top-level domains, registry outages, or policy restrictions can therefore make a valid domain lookup fail.

A 404 response does not conclusively prove a domain is available

The tool reports a 404 as “not found,” but that can mean the domain is unregistered, the queried hostname is not the registrable domain, the registry does not expose a compatible public record through this path, or the RDAP service cannot resolve the request. Do not treat a failed lookup as proof that a domain can be registered.

Subdomains are not usually separate registration objects

The normalizer removes a leading www., but it does not calculate the public suffix or automatically reduce arbitrary subdomains such as shop.example.com to the registrable parent example.com. If a subdomain lookup fails, try the registered parent domain.

Registrar and entity data may be incomplete or redacted

The implementation looks for a registrar role in the returned RDAP entities and then reads selected vCard fields. If those fields are absent, redacted, represented differently, or omitted by policy, the page shows “Not provided.” Missing public contact data should not be interpreted as proof that no registrant or organization exists.

Event labels vary between RDAP servers

The page recognizes several common event-action labels for registration, expiration, and last update. RDAP servers can return additional or differently worded events that remain visible in Raw RDAP but may not appear in the summary cards.

Domain age is an approximation

Age is calculated from the reported registration event using the current browser clock. Years use 365.25 days and remaining months use approximately 30.44 days. The result is a readable estimate, not a legal or registry-defined age calculation.

Expiration timing is also approximate

The tool compares the returned expiration timestamp with the current browser time and rounds the absolute difference to whole days. Registry grace periods, renewal processing, auto-renew behavior, redemption states, and billing status are not inferred from that number.

DNSSEC reporting is registry-level only

The summary checks the RDAP secureDNS.delegationSigned field. “Signed / enabled” means the delegation is reported as signed by RDAP; it is not a live cryptographic validation of the domain's full DNSSEC chain or current DNS answers.

Nameservers are delegation data, not full DNS records

The nameserver section displays RDAP nameserver objects returned for the registration. It does not query A, AAAA, MX, TXT, CNAME, NS glue, or other live DNS records, and it does not prove that the delegated servers are reachable.

Status codes require context

RDAP can return EPP-style status values describing locks or lifecycle states. This page displays the strings as returned but does not independently interpret every possible status into an operational recommendation. Review the raw record and registrar documentation when a transfer, renewal, or update is blocked.

Raw RDAP is the most complete view available in this page

The summary intentionally selects only a subset of the response. Notices, links, remarks, redaction information, additional entities, registry-specific properties, and other fields can remain only in the Raw RDAP JSON panel.

Common mistakes

• Assuming a failed RDAP lookup means a domain is available to register.
• Looking up a deep subdomain instead of the registrable parent domain.
• Treating a reported expiration date as proof that renewal has or has not been paid.
• Assuming old domain age proves reputation or continuous ownership.
• Confusing registry nameservers with a complete live DNS-record check.

Related Utiliverse Tools

Last reviewed: October 2026 · Host normalization, validation, rdap.org request behavior, registrar/entity extraction, event parsing, domain-age/expiry calculations, DNSSEC interpretation, nameserver rendering, raw JSON, copy fallback, and theme behavior reviewed against the current implementation.

Practical Uses

Domain renewal checks

Use the reported expiration date as a quick reference when reviewing renewal schedules, while confirming final renewal status in the registrar account.

Registrar identification

Find the registrar managing a domain when ownership records are old, several registrars are used, or a website was inherited from another administrator.

DNS troubleshooting

Compare the registry nameserver delegation with the DNS provider you expect to use. This complements, rather than replaces, a full DNS-record lookup.

Transfer troubleshooting

Review EPP status codes when a domain transfer or update is being blocked. Transfer locks are common security controls and may need to be changed at the registrar.

Domain research

Registration date and age can provide context during technical or vendor research, but age alone does not prove legitimacy, trustworthiness, or continuous ownership.

WHOIS Lookup FAQ