WHOIS lookup failed

DomainDash couldn't retrieve your domain's registration record. The cause is usually the registry's WHOIS server, and your domain is rarely affected. Check DNS first: if your site is still up, you're almost certainly fine.

Symptom

• The site's Domain registration card says "Something went wrong looking up your domain. We'll try again soon." A failed lookup doesn't make the site Down
• The Domain registration card shows no expiry date or registrar information
• Running whois example.com from a terminal may time out or return an error (or it may work normally, see below)
• Your site itself may be loading fine

What it means

WHOIS is the public record system that stores domain registration details: who registered a domain, when it expires, and which nameservers it uses. When DomainDash runs a domain registration check, it queries the WHOIS or RDAP (Registration Data Access Protocol, the modern replacement for WHOIS) server for the TLD registry or registrar. If that server is unavailable or returns an error, the check fails with whois_lookup_failed.

The TLD registry's authoritative database holds your registration, and WHOIS only reads from it. When WHOIS is down, your domain is still registered and DNS still works.

A WHOIS failure is a loss of visibility, not a confirmed problem, so DomainDash records the failed check, leaves the registration status as it was, and doesn't mark the site Down. The card doesn't show the last-known registration details while the lookup is failing. They come back when WHOIS responds again.

Common causes

• The TLD registry's WHOIS or RDAP server is temporarily overloaded or under maintenance
• DomainDash's check infrastructure is being rate-limited by an aggressive WHOIS server (some registries throttle queries by IP)
• The registrar's RDAP endpoint is down (RDAP is served by registrars as well as registries, and quality varies)
• The domain's TLD uses a less reliable WHOIS infrastructure: obscure country-code TLDs (ccTLDs) are more prone to this than .com, .net, or a large country-code TLD like .co.uk
• The domain is on a registrar hold that has also suppressed the WHOIS record (unusual, but possible for compliance-related suspensions)
• A network issue between DomainDash's check locations and the WHOIS server's geography

How to fix

1. Run a WHOIS lookup from your own machine. Run whois example.com from a terminal. If it returns your registration details, the WHOIS server is responding and the failure was likely transient or regional from DomainDash's side.

2. Check whether the failure is persistent. Look at Check history on the site's Domain registration page in DomainDash. A single failure followed by recovery was almost certainly transient, so no action is needed. If the failure has persisted for more than 24 hours, investigate further.

3. Verify your domain is healthy via DNS. Run:

   dig example.com A +short @8.8.8.8
   dig example.com A +short @1.1.1.1

   If both return an IP address, your domain is resolving and your site is up. The WHOIS check is for visibility only, so a failing WHOIS lookup alongside healthy DNS is a low-priority issue.

4. Try alternative WHOIS tools. If the whois command fails locally, try who.is, ICANN Lookup, or Whois.com to see if any web-based tool can reach the registry.

5. Contact your registrar if it persists beyond 24–48 hours. Ask them to confirm the domain is active and in good standing. Most WHOIS outages resolve on their own. Persistent failures are rare, so report one to your registrar and ask them to investigate.

How to verify

A whois_lookup_failed error is resolved when WHOIS queries succeed again:

1. Run whois example.com locally; it should return registration details including the expiry date.
2. Try the ICANN Lookup tool for an independent check.
3. In DomainDash, open the site's Domain registration page. Once the registry responds again, the next domain registration check shows the registrar and expiry date, and new entries in Check history stop showing failed lookups.

If WHOIS recovers and the card now shows Expiring, Expiring soon or Expired, or your own lookup shows a hold status (DomainDash doesn't read holds), the failed lookup had been hiding a real problem. Follow the guide for that case.

Related

• Domain suspended or on hold — if WHOIS does respond but shows a hold or suspension status
• Domain expired — if WHOIS recovers and reveals the domain has lapsed
• Domain registration — how DomainDash runs domain registration checks and what the results mean
• DNS troubleshooting — if DNS is also failing alongside the WHOIS error