DNS status is a faster signal than WHOIS
WHOIS and RDAP records are cached by registries and often lag reality by minutes to hours. DNS resolution, by contrast, reflects what's happening right now — a nameserver either answers or it doesn't. Reading DNS status codes correctly turns your monitoring from "probably fine" into a precise read on what's actually happening to a domain.
The status codes you'll see
OK
The domain resolved normally and returned valid records. No action needed — this is the steady state for any actively used, correctly configured domain.
NXDOMAIN
"Non-existent domain" — the authoritative nameservers explicitly said this name doesn't exist. For a domain that was previously resolving, a sudden NXDOMAIN is one of the strongest early signals that registration lapsed or DNS was intentionally torn down. This is often visible before WHOIS reflects any status change at all.
SERVFAIL
The nameserver responded but couldn't process the query — commonly a broken DNSSEC chain, a misconfigured zone, or a nameserver that's up but serving corrupted data. Don't confuse this with NXDOMAIN: SERVFAIL means something is misconfigured, not that the domain is gone. It's frequently transient.
Timeout
No response at all within the query window. This can mean the nameservers are offline, unreachable from your resolver's network path, or simply overloaded. A single timeout is noise. A domain that times out consistently across multiple checks, from multiple resolvers, is a much stronger signal — possibly a nameserver delegation that no longer points anywhere real.
Error
A catch-all for malformed responses, unexpected record types, or resolver-side failures that don't cleanly map to the above. Worth a manual look if it persists.
Reading the pattern, not the single check
The real value isn't any single status — it's the transition. OK → NXDOMAIN after months of
stability is meaningfully different from a domain that's always returned NXDOMAIN (never configured
in the first place). OK → Timeout → NXDOMAIN over consecutive checks often traces the exact
moment a nameserver delegation was pulled — usually hours to days ahead of any visible WHOIS status change.
Pair it with WHOIS, don't replace it
DNS status tells you a domain stopped resolving. It doesn't tell you why — expired, on hold, or just misconfigured by an active owner look identical at the DNS layer. WHOIS/RDAP status codes fill that gap — see what each EPP status code actually means. Fast signal from DNS, ground truth from WHOIS — that combination is what actually shortens your reaction time.