WHOIS Lookup
Registrar, registration and expiry dates, status codes and name servers for any domain.
Checking for an existing session…
Enter a domain to look up.
How it works
RDAP is the modern, standardized replacement for WHOIS — one JSON response format per registry, published through IANA's own bootstrap registry, instead of WHOIS's decades of ad hoc per-registry text formats. This queries the RDAP server IANA lists for a domain's TLD and returns exactly what it says.
Registrant contact data is not here on purpose
Since GDPR took effect, the large majority of registrars redact registrant name, email and phone from public RDAP responses by default. What remains — registrar name, registration and expiry dates, status codes, name servers — is what almost every registry still publishes, and is usually what an investigation actually needs: when a domain was created, whether it is about to lapse, and where it currently resolves.
Not every TLD is covered
A handful of country-code registries have not adopted RDAP and publish no server in IANA's bootstrap list. For those, this tool says so explicitly rather than falling back to a legacy WHOIS query — RDAP and WHOIS are different protocols with different abuse profiles, and this tool only speaks the one it was built to speak safely.
Example
Look up a domain's expiry date before flagging typosquatting activity as active infrastructure — a registration that lapses next week reads very differently from one renewed a decade out. Compare name servers against a domain's actual DNS records (see the DNS Lookup tool) to spot a mismatch between who registered a domain and who currently operates it.
Frequently asked questions
Why RDAP instead of WHOIS?
WHOIS (port 43) has no standard response format — every registry formats its answer differently, which is why WHOIS output has always needed guesswork to parse. RDAP (RFC 9083) is its IETF-standardized, JSON-based replacement, published through IANA’s own bootstrap registry per TLD. For generic TLDs, ICANN made RDAP the definitive source of registration data in place of port-43 WHOIS in January 2025, and it is what this tool actually queries.
Why does the registrant name and email not show?
Because the registry almost never sends it. Since GDPR took effect, the large majority of registrars redact registrant contact fields from public WHOIS/RDAP responses by default, replacing them with a privacy-proxy notice or omitting them entirely. This tool shows exactly what the registry returns — it does not have contact data to withhold.
Why does looking up a ccTLD sometimes say "not covered"?
Because not every country-code registry participates in RDAP. IANA’s bootstrap file lists which ones publish an RDAP server, and a handful of ccTLDs still do not — for those, there is no standardized machine-readable lookup to fall back to, so the honest answer is that this specific TLD cannot be queried here rather than silently returning nothing.
Related tools
DNS Lookup
Query A, AAAA, MX, TXT, NS, CNAME, SOA and CAA records for any domain.
Sends dataSSL Certificate Lookup
Every certificate publicly logged for a domain, decoded — via Certificate Transparency, not a live handshake.
Sends dataCommon Ports Lookup
Look up what normally listens on a TCP or UDP port, and why it matters if it is exposed.
LocalPort Checker
Check whether one well-known port on a host answers — open, closed, or timed out.
Sends dataCIDR Calculator
Network, broadcast, mask and usable range for any block — and split it into subnets.
LocalIP Subnet Calculator
Enter an IPv4 address with a prefix or subnet mask, see the whole subnet, and divide it.
Local