How a WHOIS lookup actually works
WHOIS is one of the simplest protocols on the internet, defined in RFC 3912: open a TCP connection to port 43, send the query terminated by CRLF, and read free-form text until the server closes the socket. There is no schema, no authentication, and no guaranteed field names — which is why two WHOIS tools can disagree about the same domain.
Finding the right server takes three steps, and this tool performs all three on every lookup:
- Ask IANA.
whois.iana.orgholds the root zone database and answers with the WHOIS server delegated for each TLD. For.comthat iswhois.verisign-grs.com; for.lolit iswhois.nic.lol. - Query the registry. The registry is authoritative for dates, EPP status codes, DNSSEC state, and the delegation nameservers. This is the data that governs whether your domain resolves and whether it can be transferred.
- Follow the registrar referral once. Thin registries such as Verisign publish only a pointer —
Registrar WHOIS Server:— and the registrar holds the contact details. This tool follows that referral a single time and merges the two responses, with registry values always winning.
Read the full explanation of whois lookup results ↓Show less ↑
Reading the fields that matter
Dates
Creation date is the moment the name first entered the registry and never changes for the life of the registration — dropping and re-registering a domain resets it. Expiry is a hard deadline: at expiry the domain typically enters a 30-day auto-renew grace period, then a 30-day redemption period during which only the registrant can recover it (for a fee, often $80–200), then a 5-day pending-delete window, after which it is released to the public. Updated date changes on almost anything: a nameserver edit, a lock change, a contact update.
EPP status codes
Status codes are the most under-read part of a WHOIS record and the most operationally important. Codes prefixed client were set by your registrar; codes prefixed server were set by the registry and you cannot remove them yourself.
| Status | What it means | Action |
|---|---|---|
| clientTransferProhibited | Registrar transfer lock is on | Normal and desirable — unlock only when transferring |
| clientHold / serverHold | The domain has been pulled from the zone | The domain will not resolve at all — contact the registrar immediately |
| pendingDelete | Final stage before public release | Recovery is no longer possible through the registrar |
| redemptionPeriod | Expired and deleted; recoverable at a premium | Redeem now — this window is short |
| autoRenewPeriod | Passed expiry and auto-renewed | Confirm payment went through; the renewal can still be reversed |
| ok / active | No restrictions at all | Turn on a registrar transfer lock |
Nameservers
The nameservers in WHOIS are the *delegation* — what the registry tells the world. They are not necessarily the NS records inside the zone. When those two disagree you get intermittent, provider-dependent resolution failures that are maddening to debug. Compare this list against the NS record lookup; if they differ, the registry list is the one resolvers follow.
Why so many fields say "redacted"
Since GDPR took effect in 2018, ICANN's Temporary Specification has required registrars to withhold registrant name, email, address, and phone from public WHOIS for most domains, replacing them with "REDACTED FOR PRIVACY" or an anonymised relay address. Many registrars apply it globally rather than only to EU registrants, and privacy-proxy services (Domains By Proxy, Withheld for Privacy, Super Privacy Service) redact by default on top of that.
Redaction does not affect the fields that matter for operations. Dates, status codes, registrar identity, DNSSEC state, and nameservers are still published and still authoritative. If you genuinely need registrant contact details — for a trademark dispute or a legal notice — the route is a request to the registrar's abuse or legal contact, which remains published, or ICANN's Registration Data Request Service.
RDAP: the structured replacement
RDAP (Registration Data Access Protocol, RFC 7483) returns JSON over HTTPS instead of free-form text over a cleartext socket, with proper internationalisation, standard field names, and the ability to authenticate for differentiated access. ICANN required gTLD registries and registrars to run RDAP from 2019, and the contractual requirement to run WHOIS is being retired. In practice both are still available for most gTLDs today; WHOIS remains the only option for a number of ccTLDs. See RDAP vs WHOIS for what changes in day-to-day use.
The same lookup from your terminal
whois google.com | grep -Ei "registrar:|creation date|expiry date|status|name server"
Registrar: MarkMonitor Inc.
Creation Date: 1997-09-15T04:00:00Z
Registry Expiry Date: 2028-09-14T04:00:00Z
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.GOOGLE.COM# 1. which server is authoritative for the TLD?
whois -h whois.iana.org com | grep '^whois:'
whois: whois.verisign-grs.com
# 2. ask the registry (the "domain " prefix forces an exact match)
whois -h whois.verisign-grs.com "domain google.com"
# 3. follow the referral for thick data
whois -h whois.markmonitor.com google.comOnce you know the registration is healthy, the next checks are usually the nameserver delegation and how long is left before renewal — the domain age checker turns the same registry dates into age and days-to-expiry.