Begin with the status list
A domain can have multiple statuses at once. They describe conditions or restrictions on registration operations. A transfer lock can be an intentional protective setting, so the presence of a restriction does not automatically indicate a problem.
Common examples include:
- clientTransferProhibited: a registrar-set restriction on transfers.
- serverTransferProhibited: a registry-set transfer restriction.
- clientHold or serverHold: a condition that prevents normal DNS publication for the domain.
RDAP responses can express statuses as words such as client transfer prohibited rather than the compact EPP labels. Compare the meaning with ICANN’s EPP status-code reference. Ask the registrar why a specific restriction exists and what action, if any, is appropriate.
What nameservers tell you
Nameservers identify where authoritative DNS information is delegated. The returned hostnames are clues about DNS infrastructure, not conclusive evidence of the company hosting the website or operating the business.
If you see a familiar provider’s nameserver suffix, record that observation. Avoid converting it into a claim about ownership. A site can use one company for registration, another for DNS, and another for hosting.
Our checker displays registry-reported nameservers. It does not run a complete live DNS investigation, inspect every record, or test whether the website and email are reachable. For an operational problem, inspect the zone through your DNS provider as well.
What DNSSEC adds
DNSSEC lets validating resolvers check cryptographic signatures on DNS data, helping detect tampering. It does not encrypt website traffic or certify that the site’s content is trustworthy. ICANN’s DNSSEC explanation describes these protections and their scope.
The checker labels the registry’s reported state as signed, unsigned, or not reported. A signed flag is not a live end-to-end validation test. “Not reported” means the relevant data was not supplied; it should not be rewritten as “unsigned.”
Use the right next step
If a planned transfer is blocked, begin with the registrar and the restriction shown in your account. If a domain stops resolving, check registration status and nameserver settings, then ask the DNS provider about its configuration. If DNSSEC settings are involved in a migration, coordinate the change with the providers managing the delegation and zone.
Record exactly what you saw and when. For example: “Registry lookup reported client transfer prohibited at 10:00 UTC” is useful evidence. “The domain is unsafe” is a conclusion that status does not support.
Keep registration age separate
An old domain can have a DNS problem, and a new domain can be configured correctly. Neither the age nor the status list substitutes for a service-health check. Use the RDAP guide to understand the source, and the troubleshooting guide when the record itself cannot be retrieved.