A worked example, rendered from real sample data. Sign in to run the tool on your own input.
example.com═══ What this tool did ═══
ℹ No WHOIS or RDAP query was sent. This page runs offline and makes no outbound network calls.
ℹ It builds the exact WHOIS/RDAP commands to run and explains what each field will mean.
═══ Domain ═══
Name: example.com
TLD: .com
Registrable guess: example.com
Registry WHOIS server: whois.verisign-grs.com
═══ Commands to run ═══
whois example.com
whois -h whois.verisign-grs.com example.com ask the registry directly (thin answer for .com/.net)
curl -s https://rdap.org/domain/example.com | jq . RDAP, the structured JSON successor to WHOIS
curl -s https://rdap.org/domain/example.com | jq -r '.events[] | "\(.eventAction): \(.eventDate)"'
dig example.com NS +short who actually serves the zone right now
dig example.com SOA +short the zone's own idea of its primary server
ℹ RDAP is authoritative and rate-limited far less aggressively than port-43 WHOIS. Prefer it in scripts.
═══ What the answer will contain ═══
• Registrar and Registry Domain ID — who the domain is managed through.
• Creation / Updated / Registry Expiry Date — the only reliable age signals.
• Domain Status — EPP codes such as clientTransferProhibited; paste the response back here to decode them.
• Name Server lines — compare these with `dig NS` to spot delegation drift.
• Registrant fields — usually REDACTED FOR PRIVACY since GDPR.
• DNSSEC — signedDelegation or unsigned.
ℹ Paste the whole response back into this box and every field, date and status code above will be decoded.
Build whois/RDAP commands and decode a pasted WHOIS response — dates, EPP status codes, nameservers and redactions (no registry is queried). Part of the DevTools Surf developer suite. Browse more tools in the Networking collection.