WHOIS Domain Lookup Guide
whois domain lookup · whois check domain · domain whois search
Complete guide to WHOIS domain lookup: registrar, dates, status codes, nameservers, RDAP fallback, and responsible use of registration data.
By DN01 Network Team
WHOIS (and modern RDAP) exposes public registration metadata for domain names — who registered, through which registrar, key dates, and often nameservers. It is the first stop when buying a domain, debugging email, or investigating phishing.
This guide walks through running a lookup with DN01 WHOIS, interpreting common fields, and knowing what privacy redaction hides.
Registration data answers «who controls the name» while DNS tools answer «what records publish» — use both when mail or HTTPS breaks after a registrar change.
Key WHOIS fields
Registrar: retail company where the registrant pays (may differ from registry operator for ccTLDs).
Created / Updated / Expiry: lifecycle timestamps — expiry drives renewal urgency.
Status codes: clientTransferProhibited, clientHold, etc. — affect transfers and resolution.
Name servers: delegation targets — cross-check with DNS Checker NS records.
WHOIS vs RDAP
Classic WHOIS uses port 43 text responses; RDAP returns structured JSON over HTTPS. Many gTLDs prefer RDAP; some ccTLDs remain WHOIS-only.
DN01 normalizes both into readable cards plus raw text for ticket attachments.
When automating lookups, prefer RDAP bootstrap URLs for gTLDs; for manual triage, DN01 cards are faster than parsing raw port-43 text.
Practical lookup workflow
Enter the domain in WHOIS — use punycode form for IDN if the UI accepts Unicode.
Verify expiry and transfer lock before purchase.
Compare nameservers with DNS Checker — mismatches explain «panel shows records but world sees old DNS».
Document findings; do not scrape bulk WHOIS for spam — registries rate-limit and GDPR limits personal data.
For acquisitions, save WHOIS output with timestamp — registrant redaction may change after transfer completes.
Status codes that block changes
clientTransferProhibited and serverTransferProhibited prevent moves between registrars until removed.
clientHold and serverHold stop resolution entirely — site and mail fail until registry lifts the hold.
pendingDelete and redemptionPeriod mean the name is leaving normal renewal flow — act before drop catchers register it.
Responsible use and rate limits
Registries throttle bulk WHOIS queries — use DN01 for occasional lookups, not scraping entire TLD zones.
GDPR limits personal data publication — treat visible contacts as operational metadata, not marketing lists.
Save normalized WHOIS cards with timestamps for compliance audits instead of forwarding raw port-43 dumps.
Frequently asked questions
- Is WHOIS data always accurate?
Dates and registrar are authoritative; registrant contact may be redacted or proxied via privacy services.
- Can I find the owner of any domain?
Not always — privacy, proxy contacts, and GDPR redaction hide individuals. Legal processes exist for abuse cases.
- Why does WHOIS time out?
Registry maintenance, rate limits, or TLD requiring RDAP — retry or check registry status page.
- Should I use WHOIS or RDAP?
DN01 abstracts both — use whichever the registry serves; fields normalize into the same card layout.