Knowing how to buy a domain name safely matters most when you negotiate directly with its owner. Direct contact can make discussions faster and clearer, but it also means you must perform the checks a broker might otherwise coordinate. Use this checklist before money changes hands, whether you found the name through domain listings on DomainsNoBroker or through your own outreach.

The goal is not to eliminate every possible issue. It is to confirm the asset, the counterparty, the payment path, and the handoff before you commit.

1. Research the domain before discussing price

Start with the name itself. Confirm the exact spelling, extension, and whether it resolves to a website. Look for prior use that could create reputational, technical, or brand-fit concerns. A domain can be valuable as a short name yet still be a poor fit for your planned business.

Check registration facts, not assumptions

Use ICANN’s Registration Data Lookup Tool to identify the registrar, registry status, nameservers, and available registration data. Treat the results as a starting point, not proof that the person emailing you owns the name: some registrant data may be unavailable or redacted.

• Record the exact domain and the registrar shown in the lookup.
• Check expiration timing and visible status codes, including transfer-lock indicators.
• Search the name, former websites, and social references for obvious misuse or confusion.
• For a brand-led purchase, search similar marks in the USPTO trademark database and obtain qualified advice if the result raises questions.

2. Verify the seller’s identity and control

A seller’s ability to describe a domain is not evidence that they can transfer it. Ask who is authorized to sell: the individual registrant, a company officer, a portfolio manager, or another designated representative. If a company owns the name, request confirmation from an email address tied to that company or another independently verifiable channel.

Use a live, limited proof-of-control test

Ask the seller to make a reversible change you specify, such as adding a unique temporary DNS TXT record or placing a random token on the live site. Verify it yourself, then ask them to remove it. Do not ask for registrar passwords, full account access, or an authorization code before the agreed transfer stage.

• Keep communication in one documented thread.
• Independently verify any changed bank, email, or escrow instructions by using a known contact method.
• Pause if the seller refuses reasonable proof, pushes for urgent payment, or will not identify the registrar.

3. Make an offer with written transaction terms

State the domain, currency, total price, who pays transaction fees, the proposed escrow provider, the transfer route, and deadlines. A clear offer prevents a common direct-deal problem: both parties believe they agreed, but they mean different things by “transfer” or “payment received.”

Include the minimum terms in one confirmation

• Exact domain name or list of names, stated character for character.
• Purchase price, currency, fees, and the party responsible for each fee.
• Escrow service, inspection period, and conditions for release of funds.
• Transfer method: same-registrar account push or transfer to another registrar.
• What is included besides the registration, if anything, such as a website or email assets.
• Each party’s name, contact details, and authority to act.

For a significant purchase or a deal involving business assets beyond the domain, have your written terms reviewed by an appropriate professional before funding.

4. Use a trusted third-party escrow service correctly

Do not send funds directly to a seller merely because you have seen apparent control of the name. Choose a reputable third-party escrow service, open the transaction yourself at its official web address, and ensure the agreement matches the written deal. A typical domain escrow workflow has both parties agree to terms, the buyer’s payment verified, the domain transferred, and the buyer given an inspection step before release; see the process described by Escrow.com.

Protect the payment instructions

• Type the escrow provider’s address yourself or use a saved, verified bookmark.
• Compare the domain, price, and buyer and seller details before paying.
• Never rely only on a link or amended wire instructions sent in an unexpected email.
• Fund only the transaction record you can access in your own escrow account.

5. Coordinate the domain transfer step by step

Agree on the transfer route before funding. A same-registrar account push may be practical when both parties use the same registrar. An inter-registrar transfer typically requires an authorization code and actions at the gaining registrar. ICANN explains that an authorization code is used to help identify the registered name holder for eligible gTLD transfers.

Plan for locks and confirmation messages

Transfer eligibility can be affected by registrar locks, registration timing, registrant changes, and extension-specific rules. ICANN’s Transfer Policy describes standardized transfer requirements, but your registrar can explain the operational steps for the specific name.

• Create and secure your receiving registrar account before the seller begins.
• Use a unique password and multi-factor authentication on that account.
• Follow transfer confirmations promptly, but verify the sender and the domain first.
• Do not approve escrow release because an email says the transfer started; verify control in your account.

6. Verify receipt, then preserve the record

Before approving release, confirm the domain appears in your registrar account, that you can manage its nameservers, and that the registrant information is correct where your registrar displays it. Then save the accepted offer, escrow agreement, payment receipt, transfer confirmations, and relevant messages. After closing, enable registrar lock and multi-factor authentication. If you need help finding a seller or reporting a marketplace concern, contact DomainsNoBroker.

A careful process does not make direct negotiation cumbersome. It gives both parties a shared sequence: verify, agree, fund through escrow, transfer, inspect, and document.

Frequently Asked Questions

Can RDAP or WHOIS results prove that a seller owns a domain?

No. Registration lookup data can help you identify the registrar and domain status, but public registrant data may be redacted or incomplete. Ask for a limited live proof of control, such as a temporary DNS TXT record, and verify it independently.

Should I pay a domain seller directly after they prove control?

For a meaningful purchase, use an appropriate trusted third-party escrow service rather than sending payment directly. Open the transaction from the provider’s official site, confirm the terms, and release funds only after you verify the domain is under your control.

Is a registrar account push safer than an inter-registrar transfer?

Neither route is automatically safer. A same-registrar push can be simpler, while an inter-registrar transfer may better fit your preferred registrar. Choose the method in advance, confirm transfer eligibility, and verify the domain in your receiving account before escrow release.

What should I save after buying a domain?

Keep the final written terms, escrow transaction record, payment confirmation, proof-of-control request, transfer emails, and a record showing the domain in your account. These records help reconcile the purchase and support later internal, accounting, or professional review.

Related topic: domain escrow service.

Related topic: sell domain without broker.

Related topic: sell domain without commission.