A failed registry lookup should lead to an information-gap review. It does not prove that the domain is expired, unlocked, unsigned or healthy.

Inspect the note

1. Open PD Modules → Domain Radar → Needs attention.
2. Choose Notes only if needed and find Could not be checked.
3. Read What we found to distinguish an unavailable lookup service, no answer or an unreadable answer.
4. Compare the domain’s checked time and the latest sweep result in Report or Activity.

The module uses the published lookup-service map and cached registry endpoints. Some extensions may have no usable endpoint in that map; a transient refusal, timeout or unreadable response is a different situation. Do not assume that a note proves the domain does not exist.

Do not trust old fields as new evidence

Portfolio fields from a previous successful check can remain visible after a failed one. The latest checked timestamp records the attempt, not necessarily a successful registry response. Likewise, an earlier critical finding can disappear from the open list when the failed check produces only the unavailable note.

Check the actual domain position through your normal authorised domain-management process before saying an earlier problem was fixed. A clear summary or green report is not proof that every lookup succeeded.

Review lookup coverage

Review automatic scanning, batch coverage and the exact note before trying another appropriate batch. Repeated immediate scans can make rate limiting worse and are not a substitute for diagnosis.

See the PD Domain Radar Blesta guide for related tasks, or explore PD Domain Radar.