Skip to main content
network-tools

Whois for Domain Due Diligence: Check Before You Buy

A domain is often the first thing you buy, inherit, or investigate; and it is the one asset where the entire history is public. A whois lookup takes seconds and routinely surfaces facts that a pretty landing page hides: the domain was registered last month, it expires in six days, or it changed hands three weeks ago. Here is how to read a whois record like an auditor instead of like a tourist.

What a whois record actually contains

Run any domain through the whois lookup tool and you get a handful of fields. The ones that matter:

  • Creation date — the true age of the domain. Not the launch date on the "About us" page; the day someone first paid for it at a registry.
  • Expiry date — when the current registration lapses, and therefore when the domain is at risk of being lost or auctioned.
  • Registrar — who manages the registration. Unusual registrars are not proof of anything, but they set the context for a transfer.
  • Status codes — EPP codes such as clientTransferProhibited, redemptionPeriod, pendingDelete. These tell you what state the domain is in more precisely than the expiry date alone.
  • Name servers — whether the domain is actually being used. A parked name server farm and a production cluster tell very different stories.

Registrant contact details used to be the headline field. Since GDPR, most records replace them with privacy-protection placeholders. Judge the other fields instead.

Buying a used domain: the age check

The classic mistake is paying a premium for "an aged domain" that is not aged. Sellers list domains with 2014-style content and 2014-era design, and buyers assume the registration is old too. The creation date is the only evidence that counts.

Age alone is not the goal, though. An old domain that spent most of its life parked, or that passed through redemptionPeriod twice, carries far less trust than a steadily maintained one. When you see expiry dates that were repeatedly renewed and status codes that show normal custody, that is the profile of a healthy asset. If the record shows a recent registrarTransfer-class event combined with a short remaining term, ask why. Legitimate transfers happen; a domain one step ahead of its own expiry is a negotiation lever, not a detail.

One more practical scenario: you bid on a domain and win it, and the seller's whois still shows their registrar. Before you wire money, confirm the EPP status. If you see pendingDelete, the domain is in the registry's deletion pipeline — no seller can transfer it to you, and it will soon drop and become available to anyone with a drop-catching service. People have paid for domains that were days away from becoming free for others to grab.

Vetting a company, vendor, or counterparty

Due diligence is not just for buyers. Before you send an invoice, sign a reseller agreement, or click a link from a "supplier," check their domain the same way:

  1. Age vs claims. If the website says "serving customers since 2009" and the creation date is this year, that is a red flag worth a conversation. New companies exist and start clean — but the mismatch itself is information.
  2. Consistency. A company claiming EU operations, registered through a registrar that serves a different region, with name servers parked at a domain-monetization service — each data point is weak alone; together they sketch a picture.
  3. Expiry runway. A vendor whose core domain expires in three weeks is either forgetting to renew or already halfway out the door. Either way you want to know before you depend on it.
  4. Status codes. serverTransferProhibited on a registry level usually means a dispute or registry lock. On a vendor's domain, that is worth asking about.

Pair the whois read with a domain reputation check when the risk is high, and with DNS lookups to see what the domain currently resolves to. Whois tells you the contract; DNS tells you the reality.

Reading status codes without a handbook

EPP status codes look cryptic; in practice you need about six of them:

  • ok or active — normal, transferable state.
  • clientTransferProhibited — registrar lock, usually set by the owner. Good sign on your own domains; neutral on others.
  • redemptionPeriod — expired, owner has ~30 days to restore at a premium. The domain is effectively in limbo and cannot be transferred.
  • pendingDelete — scheduled for deletion within roughly five days. No one can transfer it; after release, drop-catchers compete for it.
  • serverHold / clientHold — DNS delegation suspended. The domain resolves nowhere. Common causes: unpaid renewal, registry non-compliance, or a dispute.
  • addPeriod — very recently registered, sometimes with a short grace window for a full refund.

The codes matter because dates lag reality. A domain whose expiry date passed two weeks ago is not "expired, grab it" — it is walking through a documented grace-and-redemption pipeline that lasts from one to two months. If you plan an acquisition around an expiry date, plan around the status codes too.

Pitfalls that burn people

Privacy protection is normal. Do not treat redacted registrant data as evidence of fraud. Millions of legitimate owners protect their data. Look at behavior — history, nameservers, DNS, content — rather than at the absence of a personal name.

Thin registries. Some TLDs (notably several ccTLDs) return only a pointer to the registrar's whois server, so a single query gives you nothing. Re-query against the registrar's server, or accept that your data will come in two steps. If your tool returns an empty shell, that is why.

Shared hosting tells its own story. A reverse IP lookup on a "enterprise vendor" that resolves to a shared host with sixty unrelated sites is not proof of anything — but if you are wiring them a five-figure retainer, it's a data point you'd want before, not after.

Whois is a snapshot. Records change. Capture the output with dates when you are making a decision, and re-check before closing a deal, not only at first contact.

Dropped domains carry ghosts. If you are acquiring a previously dropped domain, the whois creation date will be new, and old reputation — links, spam flags, previous brand use — is invisible in whois. Use a separate reputation pass for that history.

A five-minute pre-flight checklist

  1. Run whois. Note creation date, expiry, registrar, statuses, nameservers.
  2. Compare the age against any public claims the owner makes.
  3. Check DNS resolution to confirm the domain is actually operating.
  4. If money is changing hands, verify that no redemptionPeriod or pendingDelete is in play.
  5. Run a reputation scan on high-stakes targets.
  6. Save the record snapshot with the date — you may need to compare later.

Whois data rarely tells you the whole story, and that is fine. The point of due diligence is not certainty; it is going into a deal knowing exactly where the uncertainty lives. Five minutes of reading registry fields has saved more acquisitions, vendor relationships and phishing incidents than any amount of gut feeling.