Incomplete check result

An incomplete check result means a tool could not finish one or more of the checks needed to answer its question. The result may still contain useful observations, but it should not be read as a complete confirmation that a domain works or has no problems.

Why might a check be incomplete?

A DNS query can time out or return SERVFAIL. An RDAP server can limit requests. A remote service may be unreachable, or the checker may not support the information it needs. These outcomes differ from a successful check that finds a record or a valid response that says no requested data exists.

For example, a domain checker might successfully read the A record but fail to retrieve registration data because an RDAP server returned 429 Too Many Requests. The address result is still an observation, but registration status remains unchecked. A clear report should identify which parts succeeded and which did not.

Does “no issues detected” mean the check was complete?

Not necessarily. “No issues detected” is meaningful only for the checks that actually ran and the sources they consulted. If an important check timed out or was skipped, the tool cannot use the absence of an alert as proof that no issue exists. Read the scope and any warnings alongside the summary.

Related terms

• Timeout — a request did not finish in time
• Rate limit — a service refused a request after its request limit was reached
• No DNS record — an actual negative DNS result
• No issues detected — a result limited to completed checks