Tip: Paste a full URL like https://www.example.com/path and we'll extract just the domain. Subdomains get reduced to the registered base — blog.example.com looks up example.com.

About this tool

What you get back

  • Registrar — The company the domain was purchased through (GoDaddy, Namecheap, Cloudflare Registrar, GKG.Net, etc.). This is usually the answer you actually need: it tells you which account to log into to renew or transfer.
  • Created date — When the domain was first registered.
  • Expires date — When the registration runs out. Color-coded: yellow if within 60 days, red if expired.
  • Name servers — Which DNS servers are authoritative for the domain. Sometimes this is a different company than the registrar (e.g. registered at GoDaddy but using Cloudflare's DNS).
  • Status codes — EPP status flags like clientTransferProhibited (locked against transfer, normal default) or serverHold (suspended).
  • Abuse contact — Email/phone for reporting abuse from this domain (spam, phishing, malware).
  • DNSSEC — Whether the domain has DNSSEC signing enabled.

Why some fields are empty (that's normal)

Registrant name and contact info are usually hidden. Most registrars wrap consumer domains in a privacy proxy ("Domains By Proxy", "Privacy Service Provided By Withheld For Privacy", etc.) — this is a feature, not a missing field. The registrar field stays accurate, which is what you need for "where do I log in to renew this."

Which TLDs are supported

Most modern TLDs work great via RDAP — including all of .com, .net, .org, .io, .ai, .app, .dev, .co, .uk, .de, .eu, plus the new gTLDs (.tech, .cloud, .xyz, .online, etc.). Some country-code TLDs (.cn, .jp, .ru, .kr) don't expose RDAP publicly and will return an error — for those you have to use the country registry's own WHOIS site directly.

Privacy

The query goes from your browser to this site to the appropriate registry's RDAP server. We log nothing about who looked up what. Results are cached at the edge for 1 hour per domain so popular lookups are fast.

Why RDAP, not WHOIS?

The classic WHOIS protocol from the 1980s sends unstructured text over TCP port 43. Each registry returns data in their own format, with their own field names, and parsing it reliably is a nightmare. RDAP (Registration Data Access Protocol, RFC 7480-7484, finalized 2015) is the modern replacement — it's HTTP, returns clean JSON, has proper rate limiting and authentication. ICANN required all gTLD registrars to support RDAP by 2019. This tool uses RDAP exclusively for reliable, structured results.

When this is most useful

DNS audit. You're auditing a customer's DNS and find a domain you don't recognize. Run it through here — registrar tells you which account it's in, the expiration date tells you whether to renew it now, and the name servers tell you whether DNS is hosted at the same place. Combined with DNS Propagation Check you've got the full picture in 30 seconds without logging into anything.

Phishing investigation. A suspicious email arrives from a domain you don't recognize. Run the domain through here — registration age is a huge signal. A domain created last week is almost certainly a phishing operation; a 10-year-old domain is more likely a real (if compromised) sender. Pair with Email Header Analyzer to see the full delivery path and authentication results.

Outbound deliverability. Customer's email is bouncing. After running Email Health Check on their domain to verify SPF/DKIM/DMARC, run the domain through here to confirm it's not expired or about to expire — domains in their renewal grace period sometimes get held by registries, which silently breaks mail flow.