server-assisted
WHOIS lookup
Registration report for a domain: registrar, expiry dates, transfer lock, statuses and DNSSEC — RDAP-first with WHOIS fallback.
we only read public registry data (RDAP/WHOIS) — nothing is stored
Enter a domain above to run the check.
Where this data comes from
The report is built from RDAP, the structured successor to WHOIS, falling back to classic WHOIS for registries that have not migrated. RDAP is why the dates, statuses and lock flags come back as fields rather than as a wall of text that differs per registry.
What you get is the registration side of a domain: who it is registered through, when it expires, whether it can be transferred right now, and whether DNSSEC is signed at the registry.
Why is the registrant's name hidden?
Most registries redact personal data by default. Redaction is the registry's policy, not a gap in the lookup — the operational fields that matter for infrastructure work, the dates, statuses and nameservers, are still published.
What is clientTransferProhibited, and should I worry?
It is the transfer lock, and seeing it is good. It stops a transfer request from being accepted without you unlocking the domain first, which is the cheapest available defence against domain hijacking. A production domain without it is one compromised registrar account away from moving.
The expiry date is far away but my site went down. Is the domain the problem?
Then it is not registration. Expiry only tells you the domain still belongs to you; whether it resolves is a DNS question — start with the DNS health check, which looks at the delegation and the nameservers.
Why do two lookups of the same domain show different fields?
Registries publish different subsets, and some only answer classic WHOIS. A .com and a country-code domain will not return the same shape of record no matter which tool you use.
Related tools: DNS health, DNS lookup and SSL / TLS audit.