What is a domain registration lookup?
A domain registry keeps the registration records for its ending. A registrar handles the registration relationship with the customer. Looking up their published data helps you identify the name you're dealing with before you troubleshoot it, contact someone, or arrange a transfer.
This tool uses Registration Data Access Protocol, or RDAP, rather than querying a WHOIS server. ICANN's RDAP guide explains the change for generic domains. Country-code coverage and the fields each provider publishes still vary, so an incomplete response is not proof that the missing fact doesn't exist.
Which domain should I enter?
Use the domain itself or paste a web address. For example, https://www.example.co.uk/pricing is checked as example.co.uk, the registered name rather than the page path. The result identifies a reduction or conversion when needed.
Internationalized names can be entered in their readable form. Their ASCII form starts with xn-- where conversion is needed. Neither form reveals who runs the website. If you need to compare the spellings, use the Punycode converter.
How to read a domain registration record
Start with the question that brought you here. A transfer problem calls for the statuses and registrar; a renewal question calls for the dates. A name that doesn't resolve needs a DNS check as well.
| Information | What it establishes |
|---|---|
| Registrar | The sponsoring registrar identified in the returned record. This can differ from the reseller you paid. |
| Registration date | The registration event reported for the current record. It is not necessarily the first time anyone ever registered the name. |
| Expiry dates | The dates published by the registry and registrar, kept separate when both exist. Neither proves that a renewal payment succeeded. |
| Status codes | Published conditions such as transfer restrictions or holds. An absent code does not reveal every account-level restriction. |
| Nameservers | The delegation information in the registration record. It does not prove those servers answer correctly. |
| DNSSEC data | Published delegation-signing information. Its presence does not prove a valid chain of signatures. |
| Contacts and redaction | The contact fields and withholding declarations actually returned, not a complete private customer record. |
A domain's age does not establish the age of its website, owner, or business. The Domain Age guide explains re-registration and the history checks that can put a date in context.
Why are registry and registrar answers kept separate?
The two services can contribute different facts. Merging them into one unlabeled record would hide which provider published an expiry date or withheld a contact field. The source labels let you follow each fact back to its response.
A registrar lookup may be unavailable even when the registry answers. In that case, the registry data is still useful, but missing registrar information stays missing. Raw responses are available for checking the interpretation; they are not a private or historical version of the record.
Expiry dates deserve particular care. Registry auto-renewal and processing differences can produce different published dates. This tool cannot tell whether you've paid or when your registrar will suspend service. Confirm a discrepancy in your account. The expiry checker focuses on that question without treating expiry as a promised release date.
What does “last updated” actually refer to?
Several timestamps can appear near the same record. They answer different questions, so a recent fetch must not be mistaken for a recent ownership change.
| Date | Meaning |
|---|---|
| Record last changed | A change event reported for this domain record. It usually does not identify the changed field. |
| Registry database updated | A timestamp for the provider's published data, not evidence that this particular domain changed. |
| Fetched | When stack127 retrieved the response, including a cached response when indicated. |
These event names come from the RDAP event definitions. They are not an audit trail. To establish what used to be there, you need historical evidence collected at the time.
Why are registrant details missing?
Public registration services may withhold personal information under their policies and applicable law. Some return a structured redaction declaration; others omit fields without explaining why. The tool shows a declaration when one exists and does not turn every blank into a claim of redaction.
A privacy or proxy service can also appear in place of the person you hoped to contact. That is not proof of wrongdoing, and the registrant is not necessarily the website operator. The registrant lookup explains public contact routes and requests for nonpublic data.
What should I check next?
For a website problem, compare the registration with live DNS. A hold can explain why a registered name isn't resolving, but registration data alone cannot test the website, mail server, or certificate. The domain report combines registration and DNS checks when you need both.
For a transfer, use the transfer readiness checker and confirm account-level requirements with the registrar. For an abuse report, use the published registrar contact and include evidence of the specific incident. Registration age or a hidden name alone is not evidence of abuse.
Where does the lookup go?
The submitted name goes to stack127's server, which queries the relevant RDAP services. Responses may be cached to reduce repeated requests, and rate limits protect the lookup service. This is not a local-only operation.
A timeout, blocked request, or unsupported ending leaves the answer unresolved. It does not mean the name is free. Check the TLD directory for registry details and use the registry's or registrar's own lookup when this tool cannot obtain a public RDAP answer.