Registry · Tool 10

WHOIS Explorer

Live RDAP and WHOIS for any domain - ownership, expiry, nameserver assignments, both raw and parsed.

WHOIS Inspector (RDAP)

How this works - what gets checked, in plain English

What we query: live RDAP - the structured, machine-readable replacement for legacy WHOIS - direct from the authoritative registry for the TLD. Falls back to traditional WHOIS where RDAP isn't available yet.
What you see: registrar, creation and expiry dates, current nameservers, abuse-contact email, plus the raw RDAP / WHOIS response so you can verify the parser didn't lose anything.
Why expiry matters: the most common preventable outage is a forgotten domain renewal. Calendar reminders fail; auto-renewal at your registrar doesn't.
What we don't do: we don't keep query history, don't share lookups, and don't reveal anything the registry keeps private (registrant data is redacted by GDPR-compliant registrars).

Worked examples

What WHOIS actually tells you

Three patterns you'll see in real RDAP responses, with the line that matters and the action it implies.

Healthy

Domain in good shape

status:
  - client transfer prohibited
  - client update prohibited
  - client delete prohibited
events:
  - registration: 2014-09-01
  - expiration: 2028-09-01
  - last changed: 2024-05-12
nameservers:
  - ns-1234.awsdns-12.org
  - ns-567.awsdns-34.com

All three client*Prohibited flags are set - nobody can transfer or delete this domain without registrar contact. Expiry is > 12 months out. This is the pattern to copy.

Outage

clientHold - domain is suspended

status:
  - client hold     ← DNS suspended
  - server hold     ← registry suspended
events:
  - expiration: 2026-04-08
  - registrar action: 2026-05-09
nameservers: (empty)

clientHold / serverHold means the registrar has pulled the domain from DNS. Usually a billing dispute or abuse report. Site is dark globally until resolved with the registrar.

Mismatch

Registry says X, DNS resolves Y

registry nameservers:
  - ns1.oldhost.example
  - ns2.oldhost.example

actual DNS resolution:
  - ns-aws-1.amazonaws.com
  - ns-aws-2.amazonaws.com

You migrated to new nameservers but the parent zone still points at the old ones. Some resolvers cache the old answer for up to the TTL. Update the NS records at the registrar to match - until then, propagation will be inconsistent.

Keep digging

DNS Inspector

Full DNS audit with SPF, DKIM, and DMARC validation

Subdomain Finder

Discover subdomains and map the attack surface

Blacklist Check

Scan 58 blacklist databases for domain reputation

Intelligence Briefing

WHOIS & RDAP Registration Lookup

What We Just Queried

We pulled live RDAP data direct from the registry: ownership, registrar, creation date, expiry, and nameserver assignments - both raw and parsed so you can verify what the registry actually returned.

How GoZen Handles Your Domain

Register or transfer your domain with GoZen: 500+ TLDs with WHOIS privacy, and auto-renewal so it does not lapse by accident.

Explore GoZen Domains

WHOIS Explorer.