MCP documentation menu

Why is a domain registered but missing or not resolving?

The most common question: “Domain X is in WHOIS/RDAP, so why is it missing from your listings, or why doesn’t it resolve?”

Short answer: the domain is registered but not active in DNS. A registration record (registrar, dates, status) can be complete while the registry withholds the domain from its TLD zone, usually because of an EPP hold. DataPulse listings contain domains that are active and functioning at a point in time, so a registered-but-held domain does not appear even though its registration exists. “Not discovered yet” is rarely the explanation; why is in datapulse_help(topic="methodology").

Registered is not active

WHOIS and RDAP are registration databases. Delegation is a separate step: for a domain to resolve, the registry must publish its nameservers in the TLD zone (the .com zone for .com, not the root). A hold tells the registry to omit that entry, so the domain is unreachable as a website, mail host or anything else. The status codes that withhold a domain (client hold, server hold, pending delete, redemption period, pending create, inactive) are listed with their meanings in datapulse_help(topic="rdap").

last_changed dates a change, not which change

last_changed (the RDAP “last changed” event, WHOIS “Updated Date”) is when the registration record last changed in any way: a lock added or removed, a nameserver edit, an abuse-contact update, or the hold itself. It does not say which. What changed, and when a hold appeared, comes only from the RDAP history (datapulse_dns_rdap_history), which shows the status at each observation.

  • Trap 1: “created ≈ last_changed means it was held at birth.” A gap of seconds between registrationdate and last_changed is usually the registrar setting its standard locks (client transfer prohibited, client update prohibited), not a hold.
  • Trap 2: “the current last_changed is when the hold was applied.” The most recent change is often something else, as in the example below.

Worked example: FYRIOS.COM

A cached RDAP answer can be old. datapulse_live_rdap without force may answer from a stored crawl (source: "datapulse", dated by researchdate); force=true asks the registry now. For FYRIOS the difference mattered:

Unforced (crawl of 2026-03-27)force: true (2026-06-17)
last_changed2026-01-19T15:18:14Z2026-04-21T08:19:54Z
statusclient hold, client transfer prohibited, client update prohibitedclient hold only

Constant across both: registrationdate 2026-01-02T15:05:49Z, and DNS answers NXDOMAIN. The forced last_changed of 2026-04-21 is when the registrar removed its two locks, not when the hold was applied (Trap 2).

The RDAP history settles it:

  • Observation 2026-01-04: last_changed 2026-01-02T15:06:02Z, status client transfer prohibited + client update prohibited. No hold: the change 13 seconds after creation was the standard locks (Trap 1).
  • Observation 2026-03-27: last_changed 2026-01-19T15:18:14Z, status now includes client hold.

So FYRIOS was registered on 2 January, locked seconds later, and put on client hold around 19 January. The corpus history (datapulse_dns_dphistory) shows the listing side of the same story: listed as active on 2026-01-04 (a), services dropping to none on 2026-02-01 (c, once the hold took it out of DNS), and de-listed on 2026-03-01 (d). That a → c (empty) → d arc is how a once-active domain that was later held leaves the listings.

Diagnosis workflow

  1. datapulse_domain_overview(domain, force=true): DNS, RDAP and the web scrape in one call, with RDAP fetched fresh.
  2. datapulse_live_rdap(query=domain, force=true): status shows any withholding code, beside registrationdate, last_changed, expiration_date and the nameservers.
  3. datapulse_live_dns(domain): confirm the domain does not resolve (NXDOMAIN, or no A/AAAA). Live DNS is always live, so force makes no difference there.
  4. datapulse_dns_rdap_history(domain): the status at each observation; the only source that dates when a hold appeared.
  5. datapulse_dns_dphistory(domain): the a / c / d timeline; when DataPulse listed the domain, when its services dropped, and when it left.

Steps 4 and 5 are where any timeline comes from. A forced RDAP answer gives the current status and one last_changed; live DNS shows the domain is dark now, not when or why. Both history tools are described in datapulse_help(topic="history").

When a hold is lifted and the domain is published in the zone again, the next collection cycle (about monthly) lists it again, as a new a version.

Common scenarios

What you observeLikely meaning
Registered, NXDOMAIN, status client holdRegistrar suspension: non-payment, unverified contact data, a dispute
Registered, NXDOMAIN, status server holdRegistry, court or ICANN-compliance suspension
Registered, NXDOMAIN, redemption period or pending deleteExpired and dropping; may return to the available pool
Registered, NXDOMAIN, pending createRegistration not yet finalized in DNS
Registered, NXDOMAIN, no nameservers or inactiveNever delegated
Resolves fine but absent from a listingTiming: the next collection cycle includes it

Registration records carry no registrant contact data (GDPR-redacted); see datapulse_help(topic="rdap").

Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026. Your AI assistant reads this page by calling datapulse_help(topic="why_missing").