Finding the right domain is only the beginning. Before you negotiate seriously or send money, establish whether the person on the other side can authorize the sale and complete the transfer. A convincing email address, a polished landing page, or a listing alone is not enough. Good domain ownership verification combines independent record checks with a small, time-limited proof of control and a clear transfer plan.
The aim is not to demand sensitive account credentials or make the seller prove more than necessary. It is to reduce avoidable uncertainty before an offer becomes a payment obligation. Use several signals, record what you learn, and treat a mismatch as a reason to pause rather than something to explain away.
Start with the domain’s public registration record
Look up the name through ICANN Lookup. Note the registrar, registry expiry date, creation date, domain status codes, and listed nameservers. Save a dated copy or screenshot for your transaction file. Public registration data can be privacy-redacted, so the absence of a visible registrant name does not prove that a seller is illegitimate. It does, however, give you a baseline for checking whether the seller’s statements about the domain and registrar are consistent.
Compare the seller’s claimed organization, email domain, and location with any public information that is available. A perfect match is useful, but do not treat it as conclusive: records can be outdated, privacy-protected, or held by an employee, agency, investor, or corporate affiliate.
Confirm the identity behind the offer
Ask the seller to identify the legal person or business that will authorize the sale, the capacity in which they are acting, and the registrar currently holding the name. If a company owns the domain, ask for confirmation from a company-controlled email address or a person who can reasonably approve the disposition. When you contact domain owner directly, make these questions routine before discussing payment terms.
Keep the request proportionate. A seller should not send passwords, government identification, registrar credentials, or an AuthInfo code simply to win your confidence. Instead, look for a consistent identity across the negotiation, the ownership proof, and the eventual transfer instructions.
Request a narrow proof of current control
For a valuable name or an unfamiliar seller, request one reversible challenge that is difficult for an unrelated party to complete. Common options are adding a unique temporary TXT record to DNS, publishing a short unique string at a specified URL on the live site, or changing a temporary page title. Provide a random phrase, specify a short deadline, and independently check the result.
A DNS or website-file challenge demonstrates control of a configuration path at that moment. It does not by itself establish who the registrant is, whether another party has a claim, or whether the person can transfer the name. Use it as one part of a verified domain owner assessment, not as a substitute for a properly structured closing.
Test transfer readiness without requesting secrets
Ask the seller to describe the proposed transfer route: a push within the current registrar account, an inter-registrar transfer, or another registrar-supported process. Ask whether the domain is unlocked, whether there is an active transfer restriction, and whether the seller has access to the registration email and transfer-capable account. Their answers should fit the registrar and status information you recorded earlier.
For many gTLD transfers, an AuthInfo code is used to identify the registered name holder in the transfer process, according to ICANN’s Auth-Code guidance. Do not ask a seller to disclose that code prematurely as “proof.” A legitimate seller can explain how it will be released only when the agreed transaction process calls for it.
Timing matters as well. ICANN’s Transfer Policy describes circumstances in which transfers can be restricted, including certain 60-day periods after registration, transfer, or a change of registrant. Confirm the route before setting a closing date, especially if your business needs the domain by a fixed launch date.
Document the deal before funds move
Create a simple transaction record containing the exact domain name, seller identity, agreed price and currency, transfer method, expected timeline, registrar names, and the communications used to confirm each point. Preserve emails, challenge results, record snapshots, and any material changes in one folder. If a different person later sends payment instructions, stop and reconfirm through an already verified channel.
Verification lowers impersonation risk; it does not make a payment safe by itself. Use a transaction structure that clearly ties payment release to the agreed transfer outcome, and make sure both parties understand who performs each registrar step. Consider obtaining appropriate legal, tax, and security advice for a material transaction.
Red flags that justify a pause
| Signal | Why it matters | Practical response |
|---|---|---|
| Urgency paired with a demand for irreversible payment | It reduces time for independent checks. | Slow down and use the documented transfer plan. |
| Seller refuses any limited control challenge | You have no independent evidence of current access. | Request a different reversible challenge or walk away. |
| Registrar details or identity keep changing | Inconsistency can indicate confusion, poor authority, or impersonation. | Reconfirm using the original verified contact channel. |
| Request for credentials or a code outside the transfer process | Sensitive transfer information should be handled carefully. | Do not share account access or secrets. |
Know what each check cannot prove
Registration data identifies facts about a registration, but public fields may be incomplete or redacted. DNS proof shows a form of technical control, not necessarily legal authority to sell. A company email can support identity, but it does not establish that the sender has signing authority. Registrar access is operationally important, yet it does not resolve third-party claims, trademark issues, or contractual restrictions.
That is why domain ownership verification works best as a layered decision: public record consistency, identity consistency, a live control challenge, transfer readiness, and a documented transaction path. If any critical layer fails, do not rationalize it because the domain is attractive.
Use direct contact to ask better questions
When you browse domain listings on DomainsNoBroker, use the direct buyer-seller model to ask ownership, registrar, and transfer questions before you negotiate. You can also create a DomainsNoBroker account to engage with listings and review the marketplace on your own terms. A listing is a starting point for due diligence, not proof that every transaction concern has been resolved.
A careful first conversation can prevent an expensive mistake. Verify the person, verify current control, agree on the path to transfer, and only then decide whether the opportunity merits an offer.
Frequently Asked Questions
Does an ICANN Lookup result prove who owns a domain?
No. It can confirm current registration details that are publicly available, such as the registrar and certain dates or status information. Registrant details may be privacy-redacted, incomplete, or not aligned with the person authorized to sell the domain.
Is a DNS TXT-record challenge enough to prove ownership?
No. It is useful evidence that someone can make a current DNS change, but it does not prove legal ownership, signing authority, or an unrestricted ability to transfer the domain. Combine it with identity and transfer-readiness checks.
Should a seller send an AuthInfo code before I pay?
Usually, no. An AuthInfo code is sensitive transfer information. A seller can explain the planned transfer method and demonstrate readiness without disclosing the code before the agreed transaction process requires it.
What should I do if the seller cannot complete the requested verification?
Offer a reasonable alternative, such as a different temporary DNS or website challenge. If the seller cannot provide consistent identity, current-control, and transfer-readiness evidence, pause the negotiation rather than sending payment.