dotvitals

The registration data could not be read

InfoConfirmeddomain.rdap.registration-data-unavailable

What this check looks for

We could not get a registration record for this domain, so nothing in this section was checked. This is a limit of the lookup, not a finding about your domain, and it deducts nothing.

Why it matters

It matters because of what it does not say. Expiry, transfer locks and suspension statuses are unknown here — not fine. If this section is blank on a domain you care about, check it by hand at your registrar rather than reading the silence as a pass.

What it costs your score

This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.

Severity
info
Default confidence
confirmed
Status when triggered
info
Deduction
0 points
Family cap
none
Category
Domain registration
Module
Domain rdap
Fix owned by
user
In the ruleset since
2026.09

How the whole score is calculated

Technical detail

The lookup ended as: ‹reason›.

The sources tried, in order: ‹attempted›.

The reasons this happens, and what each means for you:

  • **The TLD has no RDAP service and no port-43 fallback we can use.** Around a dozen country-code registries — .de, .ro, .eu, .it, .es, .ch, .at, .ru, .jp, .cn, .us, .io, .co, .me at the time of writing — are absent from the IANA bootstrap registry (RFC 9224), and several publish very little even on port 43.
  • **The registry rate-limited us.** Registry terms forbid high-volume automated queries and every one of them throttles. Waiting and re-running usually works.
  • **The server was unreachable, or answered with something that is not a registration record.**

In none of these cases do we guess. A domain whose registration we could not read is reported as unread.

Standards and references

Test this on your domain

Run the check that produces this finding, on its own, against any domain.

Open the domain rdap checker

Other domain rdap checks