Who holds this domain, and is it locked?
Reads the registration record straight from the registry over RDAP — the registrar, the dates, the nameservers, and the transfer lock that stops a domain being moved out from under you.
Example result
Transfer lock
The registrar has locked the domain against transfer to another registrar. This is the lock that matters most: an attacker who gets into the registrar account still cannot move the domain to a registrar you do not control, which is the step that makes a hijack hard to reverse. It is set correctly here.
client delete prohibited · client transfer prohibited · client update prohibitedOther registry locks
The registrar has locked the domain against deletion. The registrar has locked the domain against changes to its registration details.
client delete prohibited · client update prohibitedRegistration dates
The registration runs to 4 Mar 2028, 412 days from now. It was first registered on 4 Mar 2015, 11 years ago. The registry last recorded a change on 2 Feb 2026.
registered 4 Mar 2015 · expires 4 Mar 2028 · changed 2 Feb 2026Registrar
example-company.com is managed through Example Registrar LLC (IANA registrar ID 9999). This is the company the registration is held with and the only party who can change the locks above, renew it, or move it. The registry publishes an abuse contact for them at abuse@example-registrar.com, which is the route for reporting misuse of a domain rather than for ordinary support.
Example Registrar LLC · IANA 9999 · abuse abuse@example-registrar.comNameservers
The registry delegates example-company.com to 2 nameservers: ns1.example-company.com, ns2.example-company.com. This is the delegation as the REGISTRY holds it, which is the authoritative statement of who answers for the domain — worth comparing against what the nameservers themselves say if a change has recently been made.
ns1.example-company.com · ns2.example-company.comDNSSEC
The registry holds no signed delegation for example-company.com, so its DNS answers are not cryptographically verifiable. That is the ordinary state for most domains and is not a misconfiguration — DNSSEC is opt-in, and running without it is a deliberate and common choice.
delegationSigned falseContacts
This registry publishes no contact details; they are held by the registrar and are withheld for privacy on virtually all domains. That is how .com is run — the registry keeps only the technical record, and the registrant, administrative and technical contacts sit with the registrar named above. This tool queries the registry alone, so the section is empty by scope rather than because anything is missing or hidden from it.
no contact entities from rdap.verisign.comExample result · registry record only · nothing stored · no account