The registration data could not be read
Updated
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
Technical detail
The lookup ended as: ‹reason›.
The sources tried, in order: ‹attempted›.
The reasons this happens, and what each means for you:
- **The registry publishes no machine-readable registration service.** Several country-code registries —
.ro,.euand.itamong them — are absent from the IANA bootstrap registry (RFC 9224) and publish no RDAP service at all. A few,.deamong them, run one that their own terms do not clearly permit a site like this to use, and we query only what is unambiguously permitted. Either way there is no source for the registration layer, and the section above names the registry’s own lookup so you can read it yourself. - **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. The technical side of the domain — its nameservers and DNSSEC — comes from our own DNS queries and is reported in full in the DNS section.
Standards and references
Test this on your domain
Run the check that produces this finding, on its own, against any domain.