The Ultimate Guide to Avoiding Domain Name Scams

Chapter 1: What Domain Name Scams Are—and What They Put at Risk

Domain name scams are deceptive attempts to obtain money, credentials, confidential information, or control of a domain by misrepresenting a person, a service, an obligation, or a transaction. The familiar version is a fake renewal invoice. The more expensive version may look like a sophisticated acquisition, complete with a polite buyer, a professional-looking contract, and a supposed escrow officer. The central issue is not how convincing the presentation appears. It is whether the claims and instructions survive independent verification.

This guide treats the domain itself, the purchase money, and the surrounding business as separate assets that need protection. A buyer can pay for a name that the seller cannot lawfully deliver. A seller can transfer a name in response to a fabricated payment confirmation. A business can keep its registration while losing control of the email or DNS settings associated with it. These are different problems, and a useful prevention process must identify which asset is exposed before deciding what to do.

The asset is more than the word in the address bar

A domain registration is maintained through a contractual relationship with a registrar. It is not a promise that the registrant owns every trademark right associated with the word, and it is not automatically a purchase of a website, customer database, or business. ICANN’s registrant guidance explains the registration relationship and the registrar’s role in maintaining the name. Throughout this book, “ownership” is convenient commercial shorthand; the precise legal rights depend on the applicable agreement, extension, and jurisdiction. ^[5]

For transaction planning, separate registration control from operating control. Registration control concerns the account and records through which the name is managed. Operating control concerns the services that use it: the website, mail routing, verification records, and related systems. A buyer who can see a domain in an account still needs to establish that the account is genuinely theirs and that the delivered asset matches the agreement. A seller who has transferred the domain still needs evidence that the transaction’s payment conditions have actually been satisfied.

The surrounding business can be worth much more than the acquisition price. Consider a hypothetical company buying a name for $18,000 and spending another $90,000 on packaging, advertising, signage, and a launch. A defect discovered after launch would not be confined to the original payment. Reversing the branding decision could affect customers, staff time, supplier coordination, and public confidence. This is why a modest increase in verification effort may be commercially sensible even when the domain price alone seems manageable.

A scam can target either side of the table

Buyers should ask whether the seller is real, authorized, and able to deliver the exact rights being sold. They should also ask whether the payment destination and transaction provider are authentic. A legitimate domain with an illegitimate payee is still a dangerous deal. Equally, a genuine seller may unknowingly forward compromised instructions. The correct object of verification is the specific action about to occur, not merely the reputation of someone who participated earlier in the conversation.

Sellers face a different sequence of temptations. A surprisingly generous offer can make a small requested payment seem harmless. A message claiming that funds are already secured can make an early transfer feel routine. A buyer’s insistence that a particular appraisal or certification is necessary can turn the seller into the actual paying customer. DigiCert’s discussion of domain scams identifies buyer-directed appraisal requests as a recognized warning pattern. The practical lesson is to examine what the supposed buyer wants you to do before concentrating on the offered price. ^[6]

Neither side should confuse the other party’s confidence with proof. A buyer may have a polished corporate identity and no authority to spend the company’s money. A seller may have access to a registrar account and no lawful right to dispose of its contents. A broker may be a genuine professional while the person using that professional’s name is an impostor. Each of these situations requires a different check, which is why “they seemed legitimate” is an inadequate closing standard.

Three questions organize almost every prevention decision

The first question is: what claim am I being asked to believe? Examples include a claim of ownership, a claim that money has cleared, or a claim that a renewal deadline requires payment today. Write the claim in a sentence. That simple act removes much of the persuasive decoration. “This person is friendly and knowledgeable” becomes “this person says they can transfer the domain.” The second sentence is something that can be investigated.

The second question is: who can verify that claim independently? The seller is not an independent source for the seller’s authority. An email from the supposed escrow provider is not independent when the sender supplied the provider’s address. Independence means reaching a relevant source through a channel established without relying on the disputed instruction. Depending on the issue, that source might be an authenticated account, a registrar’s support team, a corporate officer, a bank, or qualified legal counsel.

The third question is: what irreversible action is being requested before verification is complete? Paying an unfamiliar party, releasing an authorization code, approving an account change, or clicking final acceptance can alter the balance of the deal. Identify the action, its consequence, and the person who may approve it. When the consequence is substantial, a pause is not a failure to negotiate. It is part of the transaction design.

Worked example: one offer, three separate problems

Imagine a seller receives an unsolicited $42,000 offer for an unused domain. The sender uses a company signature and says a board meeting requires completion tomorrow. An attachment appears to show money deposited with an unfamiliar escrow service. Before closing, the seller must pay a $240 “international ownership certificate” fee. No single detail proves every aspect of the message is fraudulent, but the sequence creates several unresolved claims.

The seller should separate them. Is the buyer connected to the named company? Does the escrow company exist, and does an independently accessed account show this transaction? What is the claimed certificate, who requires it, and why must the seller purchase it from the proposed vendor? The buyer’s willingness to pay $42,000 does not answer any of those questions. Nor does a screenshot establish that a real financial institution holds money under agreed instructions.

The safe response is procedural rather than argumentative. The seller can say that any sale must use a mutually verified provider and a written agreement, with no buyer-directed appraisal or certification purchase. They should not send a transfer code while those conditions remain unresolved. A genuine buyer can discuss the process. A supposed buyer who disappears has not deprived the seller of $42,000; the seller has declined an unverified proposition.

Prevention is a system, not a talent for spotting liars

This book does not require you to become an investigator of every person who emails you. It proposes a repeatable method: define the asset, verify the parties, agree on terms, authenticate the payment process, control the transfer, inspect delivery, and secure the result. Later chapters explain each step and the scams that exploit gaps between them. The goal is to make unsafe shortcuts difficult even when the people involved are tired, excited, or under pressure.

A qualified domain broker can be particularly valuable where these steps intersect with valuation, confidential outreach, negotiation, and a high-stakes closing. That is a reason to consider brokerage, not a reason to stop checking. The best arrangement combines a capable broker with an independently verified transaction provider, appropriate legal advice, and clear client approvals. Expertise should make the process more transparent and disciplined, not replace evidence with trust.

The standard to remember is simple: a credible opportunity must remain credible after its claims have been checked. You do not need to prove criminal intent before refusing an unsafe payment or transfer. You need enough reliable information to justify the action you are about to take. When that information is missing, the next task is verification—not persuasion, not speed, and not hoping that a professional-looking message tells the whole story.

Back to the contents

Chapter 2: The Immediate Safety Check: What to Do Before You Click, Pay, or Transfer

When a domain message creates panic or excitement, start with the next action rather than the entire story. Are you about to open an attachment, sign in, pay a fee, send bank details, disclose a transfer code, or approve delivery? Those actions have different consequences. You do not need to understand every domain scam to make the next few minutes safer. You need to avoid changing money, access, or ownership on the strength of a message that has not been authenticated.

Treat this chapter as a rapid triage procedure. It is deliberately more conservative than an ordinary sales conversation because it applies at the moment when uncertainty and consequence meet. It does not tell you to ignore genuine renewal notices, legal correspondence, or provider requests. It tells you to verify them through a route that the questionable message does not control. A real obligation remains real when checked independently; a fraudulent instruction often depends on preventing that check.

Pause the dangerous action, not every useful action

If you have not yet clicked or paid, leave the message intact and stop interacting with its links, attachments, QR codes, and embedded telephone numbers. Open your registrar or marketplace through a bookmark or an independently located official address. Check the account’s notices, domain status, renewal information, and transaction area. ICANN’s phishing guidance specifically cautions against messages impersonating its services and against attachments of uncertain origin. ^[7]

A pause should have a purpose. Write down what needs confirmation and where you will obtain it. For a renewal claim, the question is whether the real account shows an amount due for the actual domain. For a purchase, it may be whether the verified transaction account shows funds received and authorizes the next step. For a transfer request, it may be whether your own authorized decision maker approved this exact domain, recipient, and transaction.

Avoid replacing one uncertain channel with another. Searching the suspicious company name and calling the first advertisement does not necessarily create independence. Returning a call to the number in the message does not do so either. Use contact details from an established relationship, a verified official account, or a carefully checked primary source. When the potential loss is substantial, ask a second person to review how the contact information was obtained.

Establish which situation you are actually in

If the message is merely suspicious and no action has been taken, preserve it, verify the underlying claim, and decline unsafe requests. If you entered a password, the problem is now possible account compromise. If you approved a transfer or sent an authorization code, the problem includes domain-control risk. If you sent money, it includes financial recovery. These categories can overlap, and the response should address every category that applies.

When account compromise is possible, use a trusted device and the provider’s genuine interface to secure the account. Review recovery methods, active sessions, delegated access, and any newly created rules or integrations. A password change alone is not a complete investigation. The practical objective is to remove unauthorized paths back into the account while preserving enough information to understand what happened. In a business, involve the person responsible for information security rather than improvising across multiple systems.

When money has been sent under suspicious instructions, contact the financial institution immediately and explain the suspected fraud. The FBI advises victims of business email compromise to request that their institution contact the institution receiving the transfer, and to report through IC3. ^[8]

Do not wait for the other party to admit a problem or for a promised refund to arrive before making that contact. Recovery is uncertain, but delay does not improve the situation.

Protect the domain while preserving the evidence

If you suspect an unauthorized domain change, contact the registrar’s security or recovery team through verified channels. Provide the domain, your account identifier where appropriate, the last known authorized state, and the time you discovered the issue. Ask what protective steps are available and what evidence the team needs. ICANN’s recovery guidance emphasizes contacting the registrar and maintaining documentation that supports your registration history. ^[9]

Preserve original messages where possible, not just cropped screenshots. Keep transaction identifiers, full timestamps with time zones, invoices, agreements, and a concise timeline of actions. Do not circulate account passwords or authorization codes in an incident group chat. A useful incident record distinguishes what you observed from what someone claimed. “The sender said funds cleared at 14:00” is different from “the authenticated provider account displayed funding confirmation at 14:00.”

Do not conduct your own unauthorized recovery operation against someone else’s account. Do not threaten to publish personal information, attempt to break into a receiving account, or pay an unsolicited “recovery specialist” who promises certainty. Those actions can create new legal, financial, and evidentiary problems. Your immediate task is containment and a documented escalation through organizations that can actually act on the registration, payment, or account.

The minimum stop rules

Adopt a small number of non-negotiable rules before negotiation begins. Do not send registrar credentials to a buyer. Do not pay a buyer-selected appraisal or certificate fee merely to unlock a promised offer. Do not accept a new beneficiary account without independent re-verification. Do not transfer because an email attachment looks like a receipt. Do not approve final acceptance while a material delivery question remains unresolved.

These rules do not mean every advance payment or professional fee is fraudulent. A lawyer may require a retainer, a broker may have an agreed acquisition fee, and a verified escrow provider may charge for its service. The difference is the relationship between the fee, the contracted service, the verified recipient, and the actual transaction. The stop rule targets unexplained or coercive payments, not legitimate professional work that has been consciously commissioned.

A strong rule should specify who can approve an exception and what evidence is required. “Use judgment” is too vague when an excited seller believes the offer of a lifetime is about to disappear. A better instruction is: no change to payment destination without a fresh callback to a previously verified contact and written approval by the designated decision maker. For a solo investor, a trusted independent adviser can provide the second review on larger transactions.

Worked example: the last-minute bank change

A hypothetical buyer has agreed to pay $75,000 for a domain. The contract is signed and the transfer plan is ready. Thirty minutes before payment, an email in the existing conversation says the escrow provider’s usual account is undergoing an audit and supplies replacement bank details. The email includes the correct domain and price. That contextual accuracy makes the message worth investigating, not safe to obey.

The buyer pauses payment and enters the provider’s account independently. They contact support using a previously established route and ask whether the transaction’s funding instructions changed. They do not forward the new details to their bank as a provisional instruction. If the provider confirms that the message is unauthorized, the buyer preserves it and asks the other participants to review their communication security. If the change is genuine, it still requires confirmation through the agreed process before funds move.

The important result is not whether this particular message turns out to be fraudulent. The important result is that an email could not unilaterally redirect the money. A control that works only when someone notices a spelling mistake is weaker than a control that applies to every beneficiary change. The same principle can protect a recipient registrar account, a delivery address, or an instruction to release funds.

Decide what happens next

After triage, classify the matter as verified and safe to continue, unresolved and paused, or sufficiently concerning to abandon and report. Do not leave a paused deal in an ambiguous state where one participant assumes another has approved it. Send a short neutral message stating that no further payment, transfer, or release is authorized until the specified issue is resolved. Name the issue rather than accusing someone of a crime without evidence.

Then move to the relevant detailed chapter. Account and domain emergencies are addressed in Chapter 66; payments already sent are addressed in Chapter 67; reporting routes appear in Chapter 68. For an ordinary transaction that remains viable, return to the verification and closing chapters. The emergency procedure is not meant to become permanent paralysis. It is a way to regain control of the sequence so that the next step is supported by evidence rather than pressure.

Back to the contents

Chapter 3: How a Legitimate Domain Purchase or Sale Should Work

A legitimate domain transaction is an exchange of defined rights for an agreed price through a sequence that both parties understand. The sequence matters because payment and control do not necessarily move at the same instant. A buyer wants assurance that the domain will be delivered as promised. A seller wants assurance that the money is genuinely available under the agreed release conditions. A safe closing manages that gap instead of asking one side to trust a stranger completely.

There is no single workflow for every domain, registrar, jurisdiction, or platform. A small marketplace purchase may be highly automated. A premium acquisition may involve a broker, lawyers, a negotiated agreement, and a custody service. An installment arrangement introduces continuing obligations that a simple purchase does not have. The common principle is that each participant should know what must be true before the next irreversible step occurs, and who is responsible for verifying it.

Begin with an exact asset and an authorized counterparty

The parties should identify the domain in unambiguous text, including the extension and any internationalized representation that matters. They should state whether the transaction includes only the domain registration or also a website, content, trademarks, social accounts, data, or other assets. A phrase such as “the brand” is not precise enough for delivery. The agreed asset schedule should be the same in the contract, the transaction platform, and the transfer instructions.

Next, establish who is buying and selling. A company’s employee may negotiate without having authority to sign. A broker may be authorized to solicit offers but not to accept them. A person with technical access may administer the domain for someone else. The practical solution is to document the role and authority of each participant early, before the price discussion creates momentum that makes unresolved identity questions feel inconvenient.

A hypothetical buyer should be able to summarize the deal without referring to personalities: “Company A is purchasing the specified domain from Company B; the named signer has documented authority; the verified provider will handle payment under the agreed instructions; and delivery will be to Company A’s account.” If the summary instead depends on “the person who emailed us says their associate will sort it out,” the transaction architecture is not yet complete.

Agree on commercial terms before exposing the asset

Price is only one term. Specify currency, fees, taxes where applicable, timing, delivery method, inspection, acceptance, and what happens if the transfer cannot be completed. Decide whether any deposit is refundable and what conditions govern it. A seller’s willingness to accept the headline number does not settle whether they must deliver to another registrar, transfer associated content, or wait through a lengthy inspection period.

The buyer should define the intended outcome in operational terms. Does the business need the name in a particular registrar account? Must an existing website remain live during transition? Is email continuity essential? The seller should define what is excluded and what support they will provide. A narrow domain-only sale should not silently become an obligation to rebuild the buyer’s infrastructure. Clear scope protects both sides and reduces the room for opportunistic demands after payment.

For substantial transactions, obtain legal review of the agreement rather than treating a template as universally sufficient. A broker can help organize commercial terms and identify practical issues, but the broker’s role is not automatically that of legal counsel. The agreement should fit the parties, asset, and relevant law. The purpose of professional review is not to make the document longer; it is to make the obligations and remedies intelligible before a disagreement exists.

Authenticate the transaction provider and its instructions

A familiar provider name is not enough. Both parties should reach the genuine service independently, confirm the transaction details in their own authenticated accounts, and understand the selected service. Escrow.com’s standard domain workflow describes agreement, buyer funding, domain transfer, inspection, and payment to the seller. Its concierge offering adds a different custody role. These are examples of provider-specific arrangements, not a universal definition of what every company calling itself “escrow” will do. ^{[10] [11]}

Ask exactly what the provider verifies and what remains your responsibility. Does it hold only money, or also the domain? How does it establish delivery? What starts the inspection period? What happens if a party does not respond? Which disputes can it administer, and which require the parties or a court to resolve? A transaction can use a genuine provider and still be poorly designed if the parties misunderstand its scope.

The parties should also reconcile the sale agreement with the platform instructions. A private contract promising a lengthy investigation does not necessarily change an automatically running platform deadline. A buyer should not assume that sending an email to the seller constitutes a valid rejection inside the provider’s system. The safe approach is to resolve discrepancies before funding and obtain written confirmation where the provider supports a customized arrangement.

Move money and control in a coordinated sequence

The seller should rely on the verified provider’s actual funding status and instructions, not a buyer’s assertion that payment has been made. The buyer should fund only through authenticated instructions that match the agreed transaction. The transfer should then follow the documented method, whether that is an inter-registrar transfer, a permitted account change, or delivery into a verified neutral custody account.

At this stage, do not improvise around inconvenient restrictions. A domain may have transfer limitations, account requirements, or extension-specific rules that affect timing. Identify them before promising a closing date. If an alternative delivery method is proposed, both parties and the provider should approve it in writing. The existence of a technical workaround does not mean it satisfies the contract or preserves the intended protections.

Maintain a closing log with the important events: terms approved, funding instructions authenticated, funding confirmed, transfer initiated, delivery observed, inspection completed, acceptance authorized, and payment released. This is not paperwork for its own sake. It gives the parties a shared account of what happened and helps prevent one person’s assumption from becoming another person’s instruction. For high-value deals, a broker can coordinate the log while the relevant specialists verify their own portions.

Inspect the result, not merely the appearance of progress

A buyer’s inspection should test the agreed deliverables. Confirm the exact domain, the receiving account, the registrant details available through the provider, and the buyer’s administrative control. Review whether the seller retains access through delegates, integrations, or shared recovery methods. Check any included assets separately. A functioning homepage is not a substitute for registration control, and registration control is not proof that every promised website component was delivered.

The seller should retain evidence of delivery and monitor the provider’s process through completion. Do not assume that initiating a transfer proves receipt. Equally, do not assume that a buyer’s silence means immediate payment is due outside the service’s rules. Escrow.com’s published inspection guidance explains that acceptance and expiry of the agreed inspection period have consequences within its process. The parties need to understand the current applicable terms before the clock begins. ^[12]

After completion, both sides should remove obsolete access and listings. The buyer should establish renewal responsibility, secure recovery paths, and retain the acquisition file. The seller should remove the sold name from active sale channels and preserve records required for accounting, contractual, or legal purposes. A transaction is not operationally complete simply because the purchase price has changed hands.

Worked example: a simple deal with a disciplined structure

Consider a hypothetical $12,500 domain-only purchase. The buyer has no urgent launch and can accept the name at its existing registrar. The seller provides reasonable evidence of authority, and the parties agree on a verified provider, exact asset, fee allocation, and delivery route. They decide that no website, email archive, or trademark rights are included. The buyer creates a fresh receiving account under its own control rather than accepting the seller’s entire account.

When funding is confirmed through the genuine transaction interface, the seller follows the approved delivery instruction. The buyer checks the asset and account control, completes the agreed inspection, and authorizes acceptance through the provider. The seller receives payment according to the provider’s process. Both retain the contract and closing record. Nothing in this example requires dramatic technical expertise; it requires a sequence that makes responsibilities visible.

Now imagine the same name supports a public-company rebrand, the seller is a dissolved business, and the requested delivery date conflicts with a transfer restriction. The correct process would be more involved. That difference is the foundation of proportional protection. Use enough expertise and structure for the actual stakes. Where the domain is valuable, the ownership history is complicated, or the negotiation is sensitive, an experienced broker working with verified escrow and appropriate counsel can be a highly effective way to build that structure.

Back to the contents

Chapter 4: Fraud, Bad Deals, Mistakes, and Disputes: Knowing the Difference

Not every disappointing domain transaction is a scam. A seller can ask far more than a buyer considers reasonable. A broker can decline an asset. A registrar can charge a disclosed fee that another provider would not charge. A transfer can be delayed by a genuine restriction. None of those facts, standing alone, establishes deception. Accurate scam prevention requires a vocabulary that separates intentional misrepresentation from ordinary commercial disagreement, administrative error, and legal uncertainty.

The distinction matters practically. A mistaken invoice may be corrected through support. A contractual dispute may need negotiation or legal advice. A compromised account may require urgent security intervention. A fraudulent payment instruction may require immediate bank contact. Calling everything a scam can obscure the appropriate response, while treating every problem as a misunderstanding can leave a serious attack uncontained. Start with observable facts and the decision that must be made next.

An expensive offer is not automatically a deceptive offer

Domain pricing is negotiated, and different parties may place very different values on the same name. A seller’s asking price is a proposal, not an obligation and not a guarantee of market value. You can reject it without proving the seller is dishonest. A buyer who needs a particular name for a major launch may value it differently from an investor who needs a large resale margin. Those different objectives can explain a wide gap without requiring fraud.

The useful question is whether the seller misrepresented something material. Did they invent completed comparable sales? Claim to own a domain they do not control? Describe an internationalized lookalike as the ordinary ASCII name? Promise revenue that cannot be substantiated? The price may make a deal unattractive, but the misrepresentation changes the nature of the concern. Keep valuation analysis and authenticity analysis separate so that one does not substitute for the other.

A buyer should therefore maintain two independent decisions: whether the asset is genuine and deliverable, and whether the price makes commercial sense. Passing the first does not require approving the second. A verified seller can offer a bad investment. Conversely, a bargain price does not excuse missing ownership evidence. The safest acquisition process has room to say “legitimate but not worthwhile” as well as “potentially worthwhile but not verified.”

A disclosed service fee differs from a manufactured obligation

Professional services can cost money before a sale completes. A commissioned appraisal, legal review, acquisition search, or specialist consultation may be legitimate even if no transaction results. The relevant questions concern informed consent: what service was ordered, who will perform it, what it costs, what is refundable, and what outcome is actually promised. A clearly described service can still be poor value, but poor value and fabricated necessity are not the same claim.

A warning sign appears when the supposed buyer insists that a seller purchase a particular certificate or appraisal solely to unlock an attractive offer. The seller is being asked to fund a separate service whose independence and necessity are unproven. That pattern is different from the seller choosing an adviser to help set a price. The fee’s size is not the decisive issue. A small payment can be the entire objective of the approach.

Deceptive solicitations may resemble bills while fine print describes an optional listing or service. The FTC’s 2010 domain-registration enforcement announcement concerned alleged bogus bills and false impressions that customers would lose their addresses unless they paid. The broader lesson is to identify whether a notice reflects an existing obligation or merely solicits a new purchase. Read the service description, not just the prominent due date and domain name. ^[13]

Operational friction can have legitimate explanations

A domain’s transfer status, expiration state, or account configuration may prevent immediate delivery. A receiving provider may require identity checks. A company may need additional authority documents. These circumstances can be genuine, although a scammer may also use similar explanations. The correct response is to verify the particular restriction with the relevant provider rather than deciding that all delays are either harmless or fraudulent.

ICANN’s transfer FAQ and policy describe circumstances in which an inter-registrar transfer can be restricted, including certain recent registration, transfer, or registrant-change situations. Such restrictions do not all have identical rules, and they should not be generalized to every extension or every account operation. A seller who says a name cannot move today should be able to support the explanation through the actual registrar and applicable policy. ^{[14] [15]}

A sensible contract anticipates operational friction. It can distinguish a remediable delay from a failure to deliver, assign responsibility for obtaining information, and define what happens when a deadline cannot be met. The parties should not invent these rules during a crisis. For a high-value transaction, a broker can help identify practical contingencies while counsel determines how to express the parties’ agreement legally.

A dispute is not proof that one side committed a crime

Two parties may disagree about what was included, whether an inspection was satisfactory, or whether a representation was breached. Their disagreement may be serious without being criminal fraud. Avoid using public accusations as a negotiation tool. Preserve the agreement, communications, delivery evidence, and provider records. Describe the specific mismatch between the promised and delivered result, and obtain advice about the appropriate remedy.

For example, a buyer may believe a domain purchase includes the website because the seller used the phrase “online property.” The seller may believe only the registration was sold. The immediate problem is scope ambiguity. The answer depends on the actual agreement and relevant law, not on which party is more frustrated. This is precisely why a domain-only transaction should say what is excluded as clearly as what is included.

Trademark disputes require similar care. A domain holder’s refusal to sell does not automatically establish cybersquatting. A trademark owner’s legal demand is not automatically extortion. A dishonest demand can impersonate a genuine rights holder, while a genuine demand can raise issues that require a timely response. Chapters 51 and 52 explain how to verify legal communications and separate the available dispute mechanisms from ordinary purchase negotiations.

Worked example: a worrying invoice that is not a renewal

A hypothetical business receives a $289 notice headed “Domain Services Final Reminder.” It includes the company’s real domain and mailing address. The accounts team assumes it is a renewal, but the small print describes inclusion in a business directory. The company has not ordered that service. The immediate decision is not whether to launch a public accusation. It is whether an authorized purchase or renewal obligation exists.

The domain manager checks the actual registrar account and finds that renewal is already arranged. The accounts team records the notice as an unsolicited offer rather than an approved invoice. If the presentation appears deceptive, the business can preserve and report it through appropriate channels. It should not pay merely because the domain and address are correct; publicly available or previously exposed information can make a solicitation look familiar.

Now change one fact: the business did knowingly buy a directory placement last year and authorized renewal. The same price might represent a contractual issue rather than a fabricated invoice. The organization should review the original order and cancellation terms. The distinction rests on evidence about the relationship, not on the reader’s dislike of directories or the appearance of the letter alone.

Use precise language to make better decisions

In internal records, distinguish “unverified,” “inconsistent,” “unauthorized,” “disputed,” and “confirmed fraudulent” where the evidence supports those descriptions. Unverified means the claim has not been adequately checked. Inconsistent means sources do not agree. Unauthorized means the relevant person or organization did not approve the action. Disputed means the parties disagree about rights or performance. These labels guide different next steps and reduce the temptation to jump from suspicion to certainty.

You do not need a final legal classification to protect yourself. An unresolved beneficiary mismatch is enough to stop payment. An unexplained ownership gap is enough to decline acquisition. An unsupported demand for an advance fee is enough to refuse that fee. Commercial self-protection can be decisive without pretending that every uncertainty has been adjudicated.

This balanced approach strengthens the case for professional brokerage rather than weakening it. A capable broker should help distinguish a bad price from a bad counterparty, a routine restriction from a delivery failure, and a real opportunity from an invented one. The value lies in disciplined judgment and a sound process. A professional who calls every objection a scam—or dismisses every concern as normal—does not provide the discrimination that a serious domain transaction needs.

Back to the contents

Chapter 5: Urgency, Authority, Greed, and Secrecy: The Psychology of the Trap

A domain scam does not need to defeat your intelligence. It needs to persuade you to suspend one useful habit at one important moment. The requested exception may sound small: pay the appraisal now, use the replacement bank account, send the transfer code before the finance team closes, or keep the transaction away from colleagues because the buyer is famous. The common feature is not a particular emotional tone. It is pressure to act before a relevant claim can be checked.

The FTC’s general scam-prevention guidance identifies impersonation, manufactured problems or prizes, pressure to act immediately, and prescribed payment methods as warning patterns. Applied to domain deals, these patterns suggest a practical defense: separate the claimed opportunity from the requested process. An opportunity can be attractive while its proposed execution is unacceptable. You are allowed to negotiate the method as well as the price. ^[16]

Urgency turns a deadline into an authority

Real transactions have deadlines. Budgets expire, launches approach, and counterparties lose interest. The presence of a deadline therefore proves little by itself. What matters is whether the deadline is being used to bypass verification that the transaction genuinely needs. A buyer saying “we would like to close this week” is different from a buyer saying “do not contact the escrow provider because any delay cancels the offer.”

Before accepting urgency, ask who created it, what evidence supports it, and what actually happens if the deal pauses. A launch date may be real, but that does not make an unverified bank account safe. A seller may have another interested buyer, but that does not establish ownership. Treat deadlines as commercial constraints to plan around, not as evidence that unresolved facts have become true.

Prepare a response in advance: “We can work toward that date, but payment and transfer follow our verification procedure.” This language preserves cooperation without surrendering control. It also makes the deadline a shared planning issue. A genuine counterparty can help provide the necessary information. A party whose entire proposal depends on eliminating checks has revealed an important incompatibility, whether or not you can prove the underlying intention.

Authority can be borrowed from real institutions

A logo, job title, legal phrase, or recognized company name can make a message feel as though it has already been vetted. In reality, those elements are claims. An email that names your registrar does not establish that the registrar sent it. A person who invokes a lawyer does not establish that the lawyer represents them. A document headed “ICANN Compliance” does not establish an obligation to pay the sender.

The antidote is to verify the authority at its source. Contact the institution through an independent route and ask about the specific message or instruction. Do not ask only whether the employee exists; an impersonator can use a real employee’s name. Ask whether that person is involved in this transaction and whether the proposed action is authorized. Identity and instruction are separate questions, even when both concern a familiar organization.

Avoid status-based exceptions inside your own company as well. A senior executive’s apparent request should not override payment controls merely because it sounds urgent or confidential. The person responsible for authorizing a purchase can approve the business decision while the finance team still authenticates the beneficiary. A healthy process treats that separation as protection for the executive, not as disobedience.

A large promised gain can disguise a small certain loss

The appraisal scam illustrates a simple asymmetry. The seller is shown a large possible payment and asked to incur a small immediate cost. Because the cost is tiny relative to the promised sale, it can feel irrational to refuse. But the relevant comparison is not $200 against $50,000. It is a certain payment to an unverified service against an offer whose existence and completion remain unproven.

Reframe the decision without the headline number. Would you independently purchase this service from this provider on these terms? Does it solve a genuine problem in a transaction that has otherwise been verified? Who benefits if no sale occurs? These questions expose whether the proposed fee has a defensible purpose or merely borrows credibility from a hoped-for windfall.

The same reasoning applies to buyers offered a dramatic discount. A name supposedly worth hundreds of thousands of dollars may be offered cheaply for an immediate wire. The potential discount does not reduce the need to verify the asset. In fact, the transaction’s unusual terms deserve explanation. You should not convert uncertainty about legitimacy into an imaginary profit and then spend real money to capture it.

Secrecy can prevent the second opinion that matters

Confidentiality is normal in some acquisitions. A buyer may wish to conceal a planned rebrand or avoid revealing a budget. A seller may have commercial reasons not to publicize negotiations. But legitimate confidentiality can coexist with verification by a broker, lawyer, bank, or escrow provider under appropriate arrangements. “Keep this from the public” is different from “do not let anyone competent review it.”

Be especially cautious when a request combines exclusivity, flattery, and isolation. A supposed buyer may say that only you are trusted to handle the deal, that ordinary staff will misunderstand it, or that involving counsel will destroy the relationship. Those claims do not answer the underlying questions. A transaction that cannot tolerate private professional review is not made safer by the importance of the person allegedly involved.

Set the boundary early: confidential information will be limited to people who need it, but required checks will still occur. This creates a constructive alternative to indiscriminate disclosure. The buyer’s identity need not be broadcast to the market for the escrow provider to perform legitimate verification. A broker can help manage that distinction, provided the engagement does not promise anonymity from lawful compliance requirements.

Worked example: the flattering buyer and the tired seller

Imagine an investor receives a message praising an overlooked domain. The buyer says their acquisition committee has selected it after extensive research and offers $36,000 without negotiation. The investor has had a slow quarter and feels relieved. The buyer then explains that a particular appraisal must be completed that evening because the committee meets in another time zone. The language is courteous, not threatening.

The investor’s best intervention is to separate emotion from authorization. They can acknowledge the offer without accepting the fee: “Thank you. I am open to a verified sale through an agreed provider, but I do not purchase buyer-selected appraisals as a condition of an offer.” They can then ask for the buyer’s proposed agreement and verified transaction details. This response does not require diagnosing whether the praise was sincere.

Suppose the buyer replies that the investor is wasting a once-in-a-lifetime opportunity. That response adds pressure but no evidence. The decision remains the same. A real buyer can commission their own valuation or negotiate another acceptable process. The investor’s discipline has not made the domain less valuable; it has prevented a contingent promise from becoming authority to spend money.

Design around human limitations

Do not rely on perfect vigilance. Create cooling-off rules for unfamiliar fees, new payment destinations, unexpected transfer requests, and material contract changes. Decide which actions need a second reviewer. Keep a standard reply library so that refusing a shortcut does not require composing a delicate response while under pressure. A process that is easy to follow is more useful than a long policy that nobody remembers at closing.

For teams, normalize respectful interruption. A junior employee should be able to say that bank details have not been independently verified without being blamed for delaying a senior person’s deal. For solo investors, arrange an external review for transactions above a chosen risk threshold. The threshold can reflect personal circumstances; it need not be advertised to counterparties or presented as an industry standard.

The ultimate defense is not suspicion of every person. It is refusing to let emotion decide which claims require evidence. Excitement can motivate you to pursue a domain. Urgency can motivate efficient coordination. Confidentiality can shape who receives information. None of them should determine whether a seller has authority, a payment destination is genuine, or a transfer has been delivered. Those questions remain factual, even when the transaction feels deeply personal.

Back to the contents

Chapter 6: The Buyer’s and Seller’s Risk Map

A buyer and a seller can participate in the same domain transaction while fearing different failures. The buyer worries about paying without receiving the promised asset. The seller worries about delivering the asset without receiving dependable payment. Both can be harmed by impersonation, unauthorized instructions, misunderstood terms, and compromised accounts. A good risk map makes those differences explicit so that protection for one side does not accidentally create an unacceptable exposure for the other.

The purpose of a risk map is not to assign a mysterious numerical score. It is to identify what can go wrong, when it can go wrong, what evidence would reduce the uncertainty, and who must act. For a simple transaction, this can be a one-page record. For a high-value acquisition, it may become part of the closing checklist managed by the broker and reviewed by the relevant specialists.

Start with the buyer’s exposure

Before payment, the buyer’s central questions concern asset identity, seller authority, legal suitability, and the reliability of the proposed process. A premium-sounding word does not establish that the seller owns the exact domain. A clean-looking website does not establish an undisputed registration history. A legitimate escrow company does not necessarily investigate every legal risk associated with the name. Each question needs an appropriate source of evidence rather than a general feeling of confidence.

During closing, the buyer’s exposure shifts toward execution. The payment must reach the correct verified destination. The transfer must deliver the agreed asset to the agreed account. Inspection must occur while the buyer still has the contractual and procedural ability to raise a problem. The buyer should know who is checking each of these conditions and should not assume that the broker, lawyer, and provider all perform the same task.

After closing, the buyer’s exposure includes residual access, missed renewals, incomplete migration, and later claims about the asset. The purchase file should therefore survive the transaction. Keep the agreement, authority evidence, provider records, delivery confirmations, and relevant due-diligence materials. The purpose is not to hoard every message forever. It is to retain a proportionate record that explains what was acquired, from whom, and through which authorized process.

Map the seller’s different vulnerabilities

Before a sale is funded, the seller can lose money through appraisal fees, invented certifications, or other payments demanded by a supposed buyer. The seller can also expose credentials, business information, or domain-control mechanisms while trying to prove legitimacy. A useful seller policy distinguishes safe evidence of authority from dangerous disclosure. You can demonstrate that a transaction is genuine without handing a stranger the keys to the registrar account.

At delivery, the seller needs reliable confirmation that the agreed funding condition has been satisfied. A receipt supplied by the buyer is not the same as confirmation from the authenticated provider. The seller should know what delivery evidence the service recognizes and how the receiving account has been identified. If the buyer changes the destination account at the last moment, that change deserves the same seriousness as a changed bank beneficiary.

After delivery, the seller needs to complete the provider’s process, remove stale listings, and avoid inconsistent representations about the sold asset. An old buy-now listing can create a new problem even when the original sale was entirely legitimate. Where automated transfer networks are involved, understand and manage the relevant authorizations rather than assuming that a domain cannot move without a fresh manual decision. Afternic and GoDaddy describe automated transfer arrangements for eligible enrolled listings. ^{[17] [18]}

Consider the end user and the investor separately

An end user often evaluates a domain as part of a business project. The relevant downside may include launch disruption, rebranding costs, customer confusion, and dependence on the name for email or services. The acquisition price alone can understate the consequences of a defective transaction. This favors early coordination among the commercial owner, technical team, legal adviser, and transaction professionals rather than treating the purchase as an isolated marketing expense.

An investor may have a different pattern of exposure: many names, frequent inquiries, distributed registrar accounts, numerous sale listings, and recurring renewal obligations. The danger is not always one spectacular transaction. It can be a repeated small failure, such as paying nuisance fees, accepting weak buyer verification, or losing track of ownership and listings across a portfolio. Standardization becomes particularly valuable because repeated decisions should not depend on memory alone.

A business buying its first domain may need explanation more than speed. An experienced investor may need a second reviewer precisely because familiarity encourages shortcuts. Neither group is inherently immune. Tailor the control to the situation: a complex corporate authority question needs different expertise from an internationalized-domain identity check, and a payment-redirection concern needs a different response from an unsupported traffic claim.

Use a four-column decision record

For each material issue, record the claim, the evidence, the remaining uncertainty, and the required action. For example: the seller claims to act for a company; the evidence is an independently verified authorization and contract signature; the remaining uncertainty concerns a recent corporate restructuring; the required action is legal confirmation of the correct selling entity. This record is more useful than a row marked “seller checked” with no explanation.

Another row might concern delivery. The claim is that the buyer can receive the domain at a specified registrar. The evidence is confirmation from the receiving provider and the current domain status. The uncertainty is whether a planned contact change will affect the timetable. The required action is to agree the sequence with the registrar and escrow provider before funding. A risk map should turn uncertainty into a next step rather than merely cataloguing anxiety.

Do not average away critical gaps. A deal with excellent pricing, a respected broker, and a beautiful contract can still be unacceptable if the beneficiary account is unverified. Some conditions are gates, not weighted preferences. The absence of one essential fact cannot be compensated for by several unrelated positive signals. This is the practical meaning of a stop rule.

Worked example: the cheap domain with expensive dependencies

A hypothetical manufacturer plans to buy a domain for $9,000. The purchasing team calls it a small transaction and proposes a direct payment. The marketing team, however, has already ordered packaging bearing the name, and the technical team intends to use it for supplier communications. The legal team has not reviewed the seller’s authority or the intended brand use. The risk map reveals that the commercial dependencies are larger than the purchase order suggests.

The company does not need to turn the acquisition into an endless investigation. It needs to identify the few high-consequence uncertainties. Confirm the exact domain and seller authority, review the proposed brand use with counsel, use an authenticated transaction process, and plan account control and email setup. A qualified broker may be worthwhile if the seller is difficult to verify or the negotiation needs coordinated management. The decision should reflect the actual risk, not a reflexive percentage of price.

Now consider an investor buying an unused name for $300 through a familiar platform with clear delivery and payment rules. The same corporate process may be disproportionate. The investor still needs to verify the listing, understand the platform, and secure the received account, but a bespoke team may not add enough value. Proportionality means preserving essential controls while avoiding unnecessary complexity.

Make the map useful at the moment of action

Assign an owner to every unresolved issue. “Legal will look at it” is not a usable instruction unless someone knows who, by when, and what decision is needed. “The broker is handling everything” is equally vague. A broker can coordinate the map, but the bank authenticates its own payment process, the registrar explains its own transfer rules, and counsel advises on legal questions within the engagement.

Review the map when the deal changes. A new seller entity, revised payment route, installment proposal, or substitute domain can invalidate earlier checks. Verification is tied to facts, not permanently attached to a conversation. If the facts change, the relevant approval should be renewed. This prevents a legitimate opening exchange from becoming a vehicle for an unsafe closing instruction.

A completed risk map should leave both sides able to explain why the next step is justified. The buyer knows what will be received and how it will be checked. The seller knows what funding condition supports delivery and how completion will be evidenced. That shared clarity is one of the strongest practical arguments for using an experienced broker on consequential deals: someone is responsible for coordinating the whole transaction without pretending that coordination replaces each specialist’s independent verification.

Back to the contents

Chapter 7: Registrars, Registries, Brokers, Escrow Providers, and Lawyers

One of the easiest ways to misunderstand a domain transaction is to assume that every professional involved provides the same protection. A registrar may execute an account operation without negotiating the sale. A broker may coordinate a deal without holding funds. An escrow provider may administer payment conditions without issuing a legal opinion on title. A lawyer may advise on the agreement without controlling the technical transfer. The transaction becomes safer when these boundaries are explicit.

Think of the participants as answering different questions. Who maintains the registration? Who operates the relevant extension? Who represents a party commercially? Who administers money or custody? Who advises on legal rights and remedies? A person or company may perform more than one role, but that combination should be documented rather than assumed. A respected name in one role is not evidence that every other role has been covered.

The registrar and the registry

The registrar is the service through which a registrant manages the registration relationship. The registry operates the registration system for the relevant extension. In practice, your immediate account, renewal, and transfer questions usually begin with the registrar or the reseller through which you contracted. ICANN maintains a list of accredited registrars for the part of the domain system within that accreditation framework. An accreditation listing is not a general endorsement of every separate service a company might offer. ^{[5] [19]}

A reseller can add another layer. The company that bills you may not be the registrar of record. Record both identities in your domain inventory so that an emergency does not begin with uncertainty about who can act. For an extension with its own local rules, identify the relevant registry and policy source rather than assuming that a familiar .com procedure applies unchanged. The correct escalation route depends on the actual registration structure.

Do not expect the registrar to decide every commercial disagreement. If a buyer says the price was misrepresented or a seller says the agreement included an additional payment, that may be outside ordinary account support. Conversely, an unauthorized account change is not merely a pricing disagreement. Ask the provider what it can investigate, what it can preserve, and what formal process applies. Specific questions are more productive than a broad demand to “fix the deal.”

The broker as commercial representative and coordinator

A domain broker can help identify opportunities, reach counterparties, assess commercial positioning, negotiate terms, and coordinate execution. The exact scope depends on the engagement. A buyer’s broker and a seller’s broker do not necessarily owe the same duties to the same people. Before sharing a budget or reservation price, establish whom the broker represents, how they are paid, and what information they will disclose to the other side.

A broker’s coordination role can be especially valuable because domain deals combine commercial and technical details that do not always sit comfortably within one department. Someone needs to notice that the negotiated deadline conflicts with the transfer plan, that the seller entity differs across documents, or that a new payment instruction has not been authenticated. A capable coordinator makes those gaps visible and sends them to the appropriate specialist.

That role has limits. Do not assume the broker guarantees that the seller’s title is unassailable, that no trademark claim can arise, or that funds can always be recovered. Ask what due diligence the broker actually performs and what evidence the client will receive. A strong professional should be comfortable explaining the boundaries of the service. Vague assurances of complete safety are less useful than a clear description of responsibility.

The escrow provider and the custody question

Escrow is an arrangement governed by the selected provider’s terms and the transaction instructions. The label alone does not tell you whether the service holds money, controls the domain, verifies identity, checks contractual deliverables, or handles a particular type of dispute. Compare the actual service with the risks you need addressed. A genuine provider can still be the wrong fit for a transaction that falls outside its supported scope.

For example, Escrow.com describes a Domain Concierge Service in which its team receives the domain into a controlled registrar account and manages delivery to the buyer. That differs from assuming every ordinary payment arrangement includes domain custody. A buyer and seller should select the service deliberately and confirm its applicability to their registrar, domain, and transaction structure. ^[20]

Ask about the consequences of a dispute before there is one. What records does the provider rely on? What happens when the inspection period ends? Can the provider freeze a release while a documented issue is investigated? Which matters require agreement between the parties or legal process? The answers should come from the provider’s current terms and verified support, not from the counterparty’s summary of what “escrow always does.”

The lawyer’s role is distinct

Counsel can advise on the sale agreement, seller authority, legal suitability of the intended use, disputes, and remedies within the relevant engagement. The useful question is not whether a lawyer has glanced at the transaction, but what they were asked to review. A narrow review of an NDA does not establish that a domain’s ownership history or trademark implications have been assessed.

Provide counsel with the real facts, including inconvenient ones. A recent change of ownership, an existing complaint, a seller company that has been dissolved, or a request to route payment through an unrelated entity can affect the analysis. Do not withhold details because you fear they will delay the deal. Legal advice based on an incomplete picture may not address the problem that later becomes important.

Likewise, do not treat legal review as technical acceptance. A signed agreement does not confirm that the correct domain arrived in the buyer’s account. The technical reviewer and transaction provider must perform their own roles. Good coordination does not eliminate specialization; it ensures that specialists receive the information they need and that their conclusions are incorporated into the closing decision.

Worked example: the responsibility gap

A hypothetical company agrees to buy a premium domain through a broker. The buyer assumes the lawyer will verify ownership. The lawyer was retained only to review the purchase agreement. The broker assumes the escrow provider will investigate the seller’s history. The provider administers funding and delivery under its terms. Everyone is competent within a narrow role, yet nobody has been assigned the specific task the buyer thought was covered.

The remedy is a responsibility meeting before funding. The buyer identifies the unresolved ownership question, asks which professional can investigate it, and documents the scope and result. The broker coordinates the timeline, the lawyer advises on authority and contractual protections, the provider explains its verification process, and the registrar confirms the technical route. The client remains the decision maker rather than assuming that a collection of professionals automatically produces a complete review.

This example shows why adding names to a transaction is not the same as adding controls. A deal can be crowded and still have a gap. Conversely, a small transaction can be well protected with a simple structure if the necessary tasks are clearly assigned. The objective is coverage of material risks, not the largest possible team.

Build a contact and authority sheet

Before closing, record each participant’s organization, role, verified contact route, authority, and backup contact. Distinguish people who may negotiate from people who may approve price, payment, transfer, and acceptance. Keep sensitive account identifiers in an appropriately protected location. The sheet should make it possible to authenticate an unexpected instruction without relying on the message that introduced it.

Include a rule for changes. A new participant should not inherit authority merely by being copied into a thread. A replacement escrow officer should be verified through the provider. A new seller representative should have documented authorization. A new buyer entity may require revised documents and compliance checks. The larger the change, the less appropriate it is to treat it as a clerical update.

The best broker-led transactions make this structure feel straightforward. The broker does not need to pretend to be the registrar, bank, or lawyer. Instead, the broker helps the client obtain the right answer from the right party at the right stage. That is a substantial form of value: reducing confusion at precisely the points where scammers and ordinary mistakes can otherwise exploit it.

Back to the contents

Chapter 8: Secure Your Accounts Before Starting a Transaction

A carefully negotiated sale can still fail if the account used to conduct it is compromised. Before sending inquiries or listing a valuable domain, review the accounts that control the name, its email, and the transaction. This is not an unrelated cybersecurity exercise. Those accounts are the channels through which ownership evidence, payment instructions, transfer approvals, and recovery requests will pass. Weakness in one can undermine confidence in the others.

Begin by drawing a simple access map. Identify the registrar account, the email address used for recovery, the DNS provider, any marketplace accounts, and the devices from which you manage them. Note who has access and what recovery methods exist. The map often reveals forgotten dependencies: an old employee’s phone, a shared mailbox, a contractor’s account, or a recovery email hosted on the very domain being transferred.

Protect the recovery path, not only the login

Use a unique strong password for each sensitive account and a reputable password manager under your control. Enable the strongest practical multi-factor authentication the service supports, with a preference for phishing-resistant methods where available. CISA identifies FIDO/WebAuthn as phishing-resistant authentication and encourages organizations to move toward it. This is a technical protection against particular login attacks, not a guarantee that every account or transaction is safe. ^[21]

Review backup methods as carefully as the primary method. A security key offers less practical protection if a weak recovery route can bypass it. Check recovery email addresses, telephone numbers, backup codes, authorized devices, and support-recovery arrangements. Store recovery material securely and ensure an authorized person can access it when genuinely needed. Security that locks out the legitimate owner during an emergency can create a different operational risk.

Do not share one-time codes, recovery codes, or approval prompts with someone claiming to verify a sale. A buyer does not need your login credentials to purchase a domain. A broker should explain any access request and use an appropriately limited method where access is truly necessary. When in doubt, ask the provider through its genuine support channel what information the proposed operation actually requires.

Separate access according to responsibility

Use individual accounts and delegated permissions where supported instead of circulating a master password. A marketing colleague may need to edit website content without being able to transfer the domain. A contractor may need limited DNS access without the ability to change registrant details. A finance employee may need transaction records without authority to approve delivery. The practical principle is to provide the minimum access needed for the assigned task.

Inventory integrations and API keys as well as human users. An old automation or marketplace connection can remain relevant after the person who installed it has left. Review what each integration can do, whether it is still needed, and how it can be revoked. Before a sale, determine whether any existing authorization could affect the domain or its listing during negotiation. Remove obsolete access through the provider’s supported process.

For a business, document who can authorize a domain sale and who can execute it. Those may be different people. If the same person performs both roles, consider a second approval for high-value assets. The purpose is not to distrust staff. It is to prevent an impersonated instruction, misunderstood request, or compromised account from being enough to dispose of a business-critical asset.

Use a clean environment for critical actions

Perform payment and transfer steps from a trusted, maintained device rather than a public computer or a device you suspect is compromised. Avoid installing unfamiliar remote-support software because a counterparty says it is necessary for closing. A legitimate transaction should not require a buyer to inspect your whole computer or a seller to watch you log into banking. Screen sharing, when genuinely useful, should be limited and should not reveal secrets.

Keep the browser and operating system updated through their normal supported channels. Review extensions that can read pages or modify content. Do not assume that a website is authentic merely because the page looks familiar. The destination, session, and specific transaction should all be checked. A secure connection protects transport to a site; it does not by itself establish that the site is the organization you intended to reach.

When a device or account may already be compromised, stop using it for high-consequence instructions until an appropriate security review is complete. Switching from email to chat on the same compromised device is not necessarily an independent channel. For a business, involve the security team and preserve relevant logs. For an individual, use verified provider support and qualified technical assistance rather than following advice from the suspicious sender.

Plan for the domain that carries your own email

A domain may support the mailbox used to manage its registrar account or receive closing instructions. Selling or changing that domain can therefore affect the very communications needed to complete the transaction. Before delivery, establish an authorized contact route that will remain available. Update it carefully, with attention to any provider consequences, rather than making last-minute changes without understanding the sequence.

The buyer also needs a clean receiving identity. Create the receiving account under the buyer’s own organization or personal control, using secure recovery methods. Do not casually accept an entire seller account because it appears faster. That account may contain unrelated assets, historical access, or recovery dependencies. An account push or transfer into a properly established receiving account is a different arrangement from inheriting someone else’s login.

Coordinate these changes with the transfer plan. Security improvements are valuable, but poorly timed contact changes can complicate a closing. Ask the registrar how a proposed change affects the applicable operation and document the answer. The goal is to arrive at closing with secure accounts and an understood timeline, not to discover halfway through that a well-intended update changed the available delivery route.

Worked example: the forgotten contractor

A hypothetical consultancy prepares to sell a domain it no longer uses. The founder controls the registrar password and assumes access is exclusive. During the pre-sale review, the team discovers that a former contractor still has delegated access to the DNS provider and that an old marketplace integration remains active. There is no evidence of wrongdoing, but the ownership handover would be incomplete if those paths were ignored.

The consultancy removes unnecessary permissions through the relevant providers, records the authorized remaining users, and confirms which services are included in the sale. It creates a closing checklist that distinguishes registration delivery from DNS migration. The buyer establishes its own account and recovery routes. The transaction can now proceed without relying on the former contractor’s cooperation after the domain changes hands.

The lesson is not that every contractor is a threat. It is that access outlives memory unless someone maintains it. A pre-sale review is a useful opportunity to reconcile the organization’s actual control with what its decision makers believe they control. That reconciliation can prevent both fraud and accidental disruption.

Establish a secure baseline you can recognize later

Record the domain’s current registrar, relevant account identifiers, authorized users, renewal settings, and important DNS configuration in a protected transaction file. Do not include passwords in the same widely shared closing checklist. The baseline should let you recognize an unexpected change and explain the last known authorized state to support personnel. It should also identify which changes are planned as part of the deal.

Enable useful alerts and decide who will receive them. An alert that goes to an abandoned mailbox does not help. A team should know how to escalate an unexpected transfer, recovery change, or payment instruction. A solo investor should know where the registrar’s genuine security contact can be found without searching in panic. Preparation reduces the number of decisions that must be improvised under stress.

Account security is the foundation beneath brokerage and escrow. A broker can organize a disciplined transaction, but an attacker who controls the client’s mailbox may still attempt to redirect instructions. A verified provider can administer payment, but the client must reach the real account. Secure the channels before trusting the messages they carry. That is the simplest way to ensure that the later layers of protection have something reliable to stand on.

Back to the contents

Chapter 9: Identify the Exact Domain Before Discussing Its Price

Before asking whether a domain is valuable, establish exactly which domain is being offered. A one-character difference, another extension, an added hyphen, or an internationalized lookalike can change the asset entirely. Sales language encourages readers to recognize a familiar word quickly. Transaction verification requires the opposite habit: slow down and inspect the precise string that will appear in the agreement and the receiving account.

This sounds elementary, which is why it is easy to skip. A buyer may spend hours discussing valuation while every participant silently assumes a different spelling. A broker may receive an attractive logo rather than an unambiguous domain. A portfolio spreadsheet may display a truncated cell. The first due-diligence task is to remove that ambiguity before it propagates into price, legal review, payment, and delivery instructions.

Record the domain as data, not as a picture

Request the name in plain text, including the full extension. Keep a canonical version in the transaction record and compare later documents against it. Do not rely on a logo, screenshot, stylized heading, or spoken description. A wordmark can conceal punctuation or make different characters look alike. The domain in the contract should not require interpretation from a design image.

For ordinary ASCII domain labels, capitalization is not a separate registration asset. Writing a name in CamelCase can improve readability, but it does not create a different domain from the corresponding lowercase spelling. The DNS case-insensitivity rules are explained in RFC 4343. Keep branding capitalization for presentation while using an exact normalized comparison for transaction checks. ^[22]

Be careful not to extend that rule to every part of a web address. A domain is only one component of a URL, and the path after the hostname may behave differently. For a domain purchase, isolate the registration being sold rather than copying an entire promotional link. The asset schedule should identify the domain itself and list any website or content rights separately.

Understand the boundary of the registered name

A subdomain is not necessarily an independently transferable registration. A seller offering a name beneath someone else’s domain may be offering a contractual right to use that subdomain rather than the parent domain itself. Ask who controls the parent, what rights are actually granted, whether the arrangement can be revoked, and whether it matches the buyer’s intended use. Do not value a revocable service as though it were the acquisition of the parent registration.

Multi-part extensions also require attention. Do not assume the final two labels always identify the registrable asset. The relevant registry’s structure and rules determine what can be registered and transferred. When a name uses an unfamiliar extension, confirm the exact registration unit through the registrar and registry rather than inferring it from visual similarity to .com.

A useful exercise is to ask the seller to state, in one sentence, what will appear in the buyer’s registrar account after completion. If the answer is a login to a website builder, a license under a parent domain, or a token representing something else, the transaction may still have legitimate value—but it is not necessarily the domain acquisition the buyer thought they were negotiating.

Internationalized names deserve exact representation

Internationalized domain names enable legitimate use of local languages and scripts. They are not inherently suspicious. ICANN distinguishes the Unicode form displayed to users from the encoded ASCII form used for IDN labels in the DNS. For a transaction involving an IDN, record the relevant Unicode and ASCII representations and have someone competent verify that they correspond to the intended name. ^[23]

The risk arises when visual similarity is used to substitute one asset for another or when participants do not understand the representation. A character that resembles a familiar Latin letter may belong to another script. A buyer should not assume that a browser’s display proves equivalence. Verification should occur in the actual registrar and transaction records, with the exact encoded form included where needed.

Do not condemn a seller merely because an IDN appears in the listing. Many valuable and useful names are internationalized. The question is whether the asset has been accurately described and whether the buyer understands its language, script, compatibility, and intended audience. A broker handling an unfamiliar script should obtain appropriate technical or linguistic assistance rather than treating appearance as expertise.

Compare every transaction surface

The same asset should appear in the offer, letter of intent where used, purchase agreement, escrow transaction, invoice, transfer instruction, and receiving account. A discrepancy is a reason to pause. It may be a typographical mistake, but it can also be a substitution. Correct the authoritative documents before funding or delivery instead of relying on an email saying that everyone knows what was meant.

For portfolios, compare the complete lists programmatically and review exceptions manually. Check duplicates, omitted names, added names, extension differences, and internationalized representations. A spreadsheet’s row count is not enough. Two lists can contain the same number of entries while containing different assets. Preserve the agreed version so that a later revision cannot quietly redefine the package.

When a name is long or visually ambiguous, use a read-back procedure. One participant reads the exact string while another compares it with the canonical record. This is particularly useful during phone-based coordination, but it should supplement written verification rather than replace it. The final approval should point to an exact asset schedule, not a memory of a conversation.

Worked example: a premium-looking substitute

A hypothetical founder wants a short English-language .com. A seller sends a polished presentation whose headline appears to match the target. The price is unexpectedly low. Before paying, the founder’s adviser requests the plain-text name and checks it against the transaction record. The offered asset includes a visually similar character rather than the ordinary spelling the founder intended to buy.

The founder does not proceed on the theory that the difference is minor. The intended branding, customer typing behavior, legal review, and valuation all concerned another asset. The parties must either renegotiate consciously around the actual name or end the discussion. A discount calculated against the wrong domain is not a discount on the desired purchase.

Now consider a different case in which the founder intentionally wants an IDN for a local-language project. The same verification method remains useful, but the conclusion may be positive. The adviser confirms the exact representations, the intended language, and the receiving registrar’s support. The control does not discriminate against a category of names; it ensures that the buyer receives the category and string they deliberately selected.

Treat substitution as a new decision

A seller may propose a different extension after negotiations begin, saying it is equivalent for the buyer’s purposes. That may be a legitimate alternative, but it is a new asset decision. Revisit valuation, legal suitability, technical support, and commercial fit. Do not carry over the original approval merely because most of the characters are the same. The buyer’s willingness to pay for one name does not authorize purchase of another.

Similarly, an offer to include extra variants should be recorded explicitly. Additional names can be useful, but they also create renewal costs and administrative obligations. Confirm whether they are registered, transferable, and included in the price. Avoid letting a bundle of loosely described extras distract from verification of the principal domain. A collection of minor assets does not repair a defect in the main one.

The discipline established here will recur throughout the book. Exact identity is the anchor for every later check. Ownership evidence must concern this domain. The contract must concern this domain. Funding and delivery must concern this domain. A broker can add substantial value by keeping that identity consistent across a complex deal, but the client should still be able to recognize the asset independently. Before the negotiation becomes a story about value, make sure everyone is discussing the same thing.

Back to the contents

Chapter 10: RDAP, WHOIS History, and the Limits of Public Registration Data

Public registration records are useful because they let you check parts of a domain’s story without accepting the seller’s account of events. They are dangerous when treated as a complete ownership certificate. A record can identify the registrar, show technical statuses, and provide dates while leaving the actual person behind the registration undisclosed. The sensible question is not whether a lookup looks reassuring. It is which specific claims the lookup can support.

Think of registration data as one layer in a larger evidence file. Use it to identify inconsistencies, direct questions to the right provider, and establish a dated baseline. Combine it with independent identity checks, authority documents where relevant, transaction records, and a properly controlled closing. A scammer benefits when buyers turn a convenient public tool into a verdict it was never designed to deliver.

Start with the current registration-data system

ICANN announced RDAP as the definitive source for generic top-level domain registration data from January 28, 2025. This does not mean that every historical WHOIS record disappeared or that all country-code extensions follow identical arrangements. For a current gTLD check, begin with an appropriate RDAP service, such as ICANN Lookup, and consult the relevant registry’s arrangements for other extensions. ^{[24] [25] [26]}

Record the time of your lookup and the exact domain searched. Save the relevant results through an ordinary, trustworthy method. Do not rely on a screenshot supplied by the seller when you can perform the same lookup yourself. If the displayed information differs between services, check their dates, coverage, and whether one is showing cached or historical data rather than assuming that either result proves misconduct.

You are looking for practical facts: which registrar currently sponsors the name, whether a transfer-related status needs explanation, and whether the basic timeline is consistent with the seller’s representations. Those facts help plan further checks. They do not authorize you to skip them. A registration record naming a company, for example, does not tell you whether the person emailing you may bind that company to a sale.

Read dates without inventing a biography

A creation date can provide context for the domain’s registration history, but it is not a certificate that the current seller has owned the name since that date. An updated date may reflect administrative or technical changes rather than a change of owner. An expiration date is not a promise that the domain will become available to the public at that moment. Interpret each field according to its purpose and the applicable registry’s behavior.

When a seller claims uninterrupted ownership for fifteen years, ask what evidence supports that claim beyond an old creation date. Historical invoices, earlier correspondence, archived contact details, and records obtained from the legitimate account holder may help. Each item still needs context. An old invoice can be genuine while the person presenting it lacks present authority, and an archive can reflect a former business rather than the current registrant.

Dates are most useful in combination. A recently changed contact route, a sudden registrar move, an unusually urgent discount, and a seller unwilling to explain the sequence create a question worth investigating. None of those details alone proves theft. The disciplined response is to pause and obtain a coherent, independently supported account rather than choosing either blind acceptance or an unsupported public accusation.

Privacy is an information limit, not a fraud verdict

Public data may omit personal details, and privacy or proxy arrangements can place an intermediary’s information in the public record. ICANN describes these services as distinct registration arrangements; their existence is not evidence that a registrant is dishonest. ^{[27] [28]} Buyers should therefore avoid using a visible personal name as the sole test of legitimacy or treating redaction as a reason to reject every transaction.

Instead, move sensitive verification to an appropriate private channel. A verified broker, legal adviser, or transaction provider may need to establish the contracting party’s identity under a suitable process. Ask what the provider actually verifies and what it is willing to confirm. “The provider knows someone’s identity” is not necessarily the same as “the provider has established that this person owns this asset and is authorized to sell it.”

Do not demand unnecessary publication of a seller’s personal information. The objective is a reliable transaction, not exposure. A buyer can insist on knowing who will be legally bound, where notices should go, and how authority has been established without insisting that a home address appear on a public landing page. Privacy and accountability can coexist when responsibilities are explicit.

Use historical records as leads

Historical registration services can help reconstruct earlier contact information or changes in registrar and nameservers. Their coverage may be incomplete, and access to a record does not authenticate every detail within it. Treat a historical entry as a lead for further inquiry rather than a definitive chain of title. A gap in the archive does not automatically mean the name was unregistered or stolen during that period.

If you contact a former owner, find a contact route independently and explain the narrow question you are asking. Avoid disclosing the entire confidential negotiation unnecessarily. A former owner might confirm a sale, deny having sold, or simply decline to discuss it. A denial creates an issue requiring careful investigation; silence is not confirmation of the current seller’s story.

Historical website content has similar limits. It may show that a business used the name, but it does not establish who controlled the registration contract. An agency could have operated the site. A domain might have been leased. A hosting account might have remained active after a sale. Separate evidence of use from evidence of registration rights instead of combining them into an attractive but unsupported narrative.

Worked example: an old domain with a new problem

A hypothetical buyer considers a domain whose public creation date is more than twenty years old. The seller calls it a long-held family asset and offers a substantial discount for immediate closing. Current data shows a recent update. Historical records suggest a different business used the name for years. None of this settles the question, but the story contains enough uncertainty to justify additional checks.

The buyer’s broker asks the seller to explain when and how the asset was acquired and to identify the contracting entity. The response supplies an old website screenshot but no transaction history. An independently located contact at the former business reports that its staff are investigating an unauthorized account change. The buyer suspends the deal, preserves the messages, and obtains appropriate advice rather than funding a race to completion.

In a legitimate alternative, the seller produces a consistent acquisition record, the former business confirms an authorized sale through an independently established channel, and the relevant parties’ identities align. The original date questions have then served their purpose: they directed a proportionate inquiry. The same method can clear an honest seller or expose a serious problem without pretending that one lookup could decide everything.

Turn findings into closing conditions

Put unresolved registration questions into the transaction file. Identify the issue, the evidence requested, the person responsible for reviewing it, and the action that must wait. “Check WHOIS” is too vague to be a useful control. “Confirm that the currently listed registrar can deliver this exact domain under the agreed process, and resolve the unexplained recent change before funding” is a decision-ready instruction.

Repeat relevant checks near closing, especially if the deal has taken time or the transfer path has changed. A clean baseline from several weeks earlier may no longer describe the asset. Rechecking is not an accusation against the seller. It is a way to ensure that the agreement, provider instructions, and current registration state still fit together when money and control are about to move.

A qualified domain broker can interpret these records in context and recognize when an unusual pattern deserves escalation. That assistance is valuable precisely because the records have limits. Good brokerage does not convert incomplete public data into certainty. It uses the available information to ask better questions, coordinate verification, and refuse to let an unresolved ownership issue disappear beneath the momentum of a promising negotiation.

Back to the contents

Chapter 11: Control Is Not Ownership: Verifying the Seller’s Right to Sell

A person who can change a domain’s settings has demonstrated an ability, not necessarily a legal entitlement. An employee, contractor, former partner, intruder, or unauthorized agent may have account access. A seller can therefore pass a technical control test and still lack the right to sell. This distinction matters most when a buyer is tempted to accept a quick demonstration as a substitute for investigating the person and the asset’s provenance.

Use three separate questions. Can this person exercise the relevant technical control? Who holds the registration rights or other rights being transferred? Who has authority to approve this particular transaction? The answers may involve different people. A company’s administrator may control the account, the company may hold the rights, and a designated officer may be the authorized signer. A safe closing respects that separation instead of forcing everything into the inbox of whoever replied first.

Design a non-disruptive control check

Where appropriate, an agreed technical challenge can show that someone can alter a specific aspect of the domain’s configuration. For example, a carefully planned temporary DNS record may demonstrate access to the relevant DNS controls. But DNS can be hosted separately from the registrar, so that demonstration may not establish an ability to transfer the registration. Decide what the test actually proves before treating it as evidence.

Do not ask for disruptive changes to a live business merely to satisfy curiosity. Replacing nameservers, interrupting email, moving the website, or disabling security settings can create damage unrelated to the sale. A legitimate seller is entitled to question an unnecessarily invasive request. Work with the provider or an experienced technical adviser to choose a proportionate method that does not expose the business or reveal sensitive credentials.

Never turn a verification exercise into delivery of the asset. A transfer authorization code is not an ordinary document to send to an unverified prospective buyer. ICANN describes AuthInfo codes as part of the inter-registrar transfer process. Their handling should follow the selected, authenticated transaction workflow, not a stranger’s assertion that a code is needed to prove ownership. ^[29]

Establish the person behind the access

Verify the seller through a route that does not depend entirely on the original sales message. The appropriate method depends on whether the seller is an individual, a company, an estate, or an authorized intermediary. A video call, identity document, company record, or existing professional relationship can contribute evidence, but no single item should silently substitute for the rest of the inquiry.

Ask whose name will appear as seller in the purchase agreement and who will receive the proceeds. Differences require explanation. A company selling an asset may legitimately use a regulated payment arrangement involving another entity, but the buyer should not infer legitimacy merely because a story has been offered. The relevant provider and advisers need to understand and approve the arrangement within their responsibilities.

A broker should be able to explain whether it represents the registrant, an authorized sales agent, or someone still trying to acquire the name. These are materially different positions. A person seeking to source a domain for a buyer may perform useful work, but should not describe an unowned asset as an existing exclusive listing. Clear status protects honest intermediaries as well as buyers.

Investigate provenance in proportion to the stakes

For a low-value, uncomplicated acquisition through a verified provider, the inquiry may be relatively modest. For a high-value premium domain or a name central to a company’s operations, examine the ownership story more closely. Ask how the seller obtained it, whether another party asserts rights, and whether the sale requires consent from anyone else. Escalate unusual answers rather than inventing a universal document checklist that every legitimate seller must satisfy.

Evidence can include acquisition agreements, company asset records, historical correspondence, and confirmations from independently verified parties. Such material may contain confidential information, so counsel can arrange limited disclosure or review where appropriate. The buyer’s objective is not to collect every private document. It is to obtain enough credible evidence to address the risks that would make the acquisition unsafe or unusable.

Do not assume that possession of an old purchase agreement proves an unbroken present right. The asset might later have been sold, pledged, disputed, or allocated through another binding arrangement. Equally, missing paperwork does not by itself prove fraud. Some long-held assets have informal histories. Missing evidence changes the risk assessment and may require stronger contractual protections, additional investigation, or a decision not to proceed.

Understand what warranties can and cannot do

A contract can require the seller to make representations about authority, ownership, disputes, and the ability to transfer. Those promises matter, but they are not an automatic cure for a defective sale. Their practical value depends partly on whether the signer is real, legally bound, reachable, and capable of satisfying an enforceable remedy. A promise from an unidentified or insolvent fraudster may offer little practical protection.

For that reason, verification and contractual allocation should work together. Counsel can advise which representations, disclosures, conditions, and remedies fit the transaction. The broker can help collect facts and keep the process organized. The buyer should resist the comforting but false choice between trusting documents and trusting people. A strong deal uses evidence about the people and documents that accurately reflect the facts.

A provider’s identity checks also have a defined scope. Confirming a customer’s identity for compliance purposes does not necessarily establish clean title to every asset that customer offers. Ask directly whether the provider investigates ownership claims or simply facilitates the agreed exchange. Understanding this boundary is more useful than relying on a provider’s general reputation as though it were a guarantee of everything outside its service.

Worked example: the helpful administrator

A hypothetical business buyer negotiates with someone who says they manage a valuable domain for a small software company. The person can edit the landing page and promptly completes a harmless control challenge. They propose signing personally and receiving the purchase money in a personal account, explaining that the company no longer needs the name. The technical demonstration is impressive, but the proposed legal arrangement does not match the ownership story.

The buyer’s adviser contacts the company through an independently established channel and requests confirmation of the proposed sale and the signer’s authority. The company explains that the administrator was retained to maintain its website, not to dispose of the domain. The buyer stops. No argument about how convincingly the administrator proved access can resolve the missing authorization.

Consider the legitimate version. The company confirms the sale, an authorized officer signs for the correct entity, and the administrator assists with delivery under documented instructions. The same person may still perform the technical transfer, but that person is no longer being mistaken for the seller. The transaction has become safer by matching each role to its actual authority rather than excluding a useful technical participant.

Make authority a gate, not a footnote

Before funding or authorizing delivery, identify any unresolved question about the seller’s right to sell. Do not bury it among minor administrative tasks. A missing website image can be dealt with later; an unverified seller may invalidate the entire premise of the purchase. The more irreversible the next step, the more important it is that this question has a deliberate, documented answer.

When uncertainty cannot be resolved, walking away is a commercially rational outcome. The buyer does not need to prove a crime before declining to acquire a disputed asset. Likewise, a seller need not expose passwords or unrelated confidential information to demonstrate good faith. A qualified broker can help negotiate a credible verification path, but should not pressure either party to replace evidence with enthusiasm. Access opens an account; authority makes a sale legitimate.

Back to the contents

Chapter 12: Corporate Sellers, Authorized Signers, and Beneficial Owners

A corporate domain transaction can fail even when everyone involved is a real person working for a real business. The wrong entity may be named as seller. A staff member may exceed their authority. A subsidiary may use an asset registered by its parent. A founder may assume that a company’s domain is personal property. Fraud can exploit these ambiguities, but ordinary disorganization can create the same dangerous gaps.

The solution is to identify the legal seller, the authorized decision-maker, and the people performing the technical work before closing. Do not ask a logo or job title to do the work of an authority check. A professional-looking email signature may establish how someone presents themselves, not which assets they are legally permitted to dispose of. When material rights are involved, the appropriate legal advice is part of the transaction rather than an optional decoration.

Name the actual contracting entity

Record the seller’s complete legal name and the jurisdiction in which the entity exists. Distinguish a trading name from the legal person behind it. A brand may be operated by one company while the domain is held by another. Similar names within a corporate group can conceal important differences in ownership, approvals, liabilities, and the destination of proceeds.

Use the relevant official company register or another appropriate authoritative source to check the entity’s existence and status. Register contents and their legal significance vary by jurisdiction. A listing is therefore a starting point, not proof that a particular email correspondent may sell the domain. Where the register reveals an unexpected status or a mismatch, ask counsel to assess the implications instead of relying on a generic online business profile.

Have the agreement identify the entity that is actually transferring the rights. If another group company must participate, describe its role accurately. Avoid a closing in which everyone agrees informally that the names are interchangeable. They may not be interchangeable when a dispute arises, a payment is reviewed, or a former stakeholder challenges the transaction.

Separate job title from signing authority

A chief executive, director, employee, or agent may have authority in one setting and need additional approvals in another. The answer depends on the entity, its governing arrangements, the transaction, and applicable law. Do not infer a universal rule from the seniority of the person on the call. Ask what approval is required for this sale and who can evidence that it has been obtained.

Where appropriate, counsel may request a board approval, written authorization, power of attorney, or other evidence. The document should match the entity, asset, transaction, and signer. A broad-looking letter that cannot be authenticated is not reassuring merely because it contains legal vocabulary. Verify its origin through an independent channel and consider whether its scope actually includes the proposed disposition.

Keep execution authority separate from operational access. The authorized signer may never log in to the registrar, while a technical employee performs the transfer. Document the instruction path between them. This protects the seller from an administrator acting independently and protects the buyer from assuming that an administrator’s willingness to cooperate is equivalent to corporate approval.

Understand beneficial-owner questions without oversharing

Transaction providers may require information about companies and the individuals behind them as part of their verification process. Escrow.com, for example, publishes company-verification requirements for its services. Requirements can depend on the entity and transaction, so use the provider’s current authenticated process rather than a checklist forwarded by an unknown intermediary. ^[30]

A genuine compliance request can involve sensitive information, but its legitimacy depends on the requesting organization, the purpose, and the submission channel. Confirm the request inside the verified provider account or through a known contact route. Do not email passports, corporate records, or personal financial information to a supposed buyer simply because they describe the request as mandatory compliance.

Ask how information will be used and who needs access. The broker may need enough information to coordinate the deal without receiving every identity document collected by the payment provider. The buyer may need contractual certainty about the seller without obtaining unrelated personal details about every stakeholder. Appropriate confidentiality is not an obstacle to verification; it is part of a well-designed verification process.

Investigate special situations before setting a deadline

Dissolved companies, insolvency proceedings, estates, divorces, partnership disputes, and reorganizations can complicate the right to sell. These situations are not automatically scams, but they should not be handled as routine personal sales. A person may sincerely believe they inherited or retained a domain while another party has a legally relevant interest. Obtain advice from someone competent in the applicable jurisdiction and circumstances.

The same caution applies to assets used under financing, licensing, or joint-venture arrangements. Ask whether any consent, release, or other condition is needed. The answer may affect the contract, the recipient of funds, and the order of closing steps. Discovering such a condition after the buyer has funded and the seller has announced completion creates avoidable pressure to improvise.

A broker can identify the issue and keep the commercial discussion moving, but should not give an unsupported legal conclusion about corporate capacity or succession. A useful broker knows when the transaction has moved beyond ordinary domain logistics. Bringing counsel in early can be more efficient than rebuilding a closing after the parties discover that the apparent seller was not the party entitled to complete it.

Align the beneficiary with the documented arrangement

Compare the seller named in the agreement with the payment beneficiary shown through the verified transaction process. A mismatch deserves explanation and review. It is not always fraud: legitimate structures can involve agents, assigned proceeds, or other arrangements. But the explanation must be documented and accepted by the relevant provider and advisers, not merely asserted by someone requesting a last-minute wire.

Do not allow a payment change to rewrite the deal silently. A request to pay a founder personally instead of the contracting company can raise authority, compliance, accounting, and fraud concerns. Pause and establish why the change is necessary, who approved it, and whether the written documents need revision. Independent verification matters especially when the request arrives late and appears to come from a familiar email thread.

For sellers, preparing this alignment in advance reduces friction. Use a verified account appropriate to the contracting entity, identify the authorized contacts, and anticipate reasonable verification questions. A buyer who asks for consistency is not necessarily being difficult. Clear corporate records make a legitimate seller easier to trust and prevent a real deal from resembling the patterns used in impersonation schemes.

Worked example: the group-company mismatch

A hypothetical buyer agrees to acquire a domain used by a regional trading brand. Negotiations occur with the brand’s commercial director. The draft contract names the operating subsidiary, but registrar records supplied privately indicate that a holding company maintains the registration. The director asks the buyer to ignore the difference because both entities belong to the same group.

The buyer’s broker flags the mismatch before funds move. Counsel confirms which company holds the relevant rights and what approvals are needed. The correct entity joins the agreement, the authorized signer is established, and the technical administrator receives documented instructions. The payment arrangement is then aligned with the approved structure. What looked like a minor naming issue becomes a manageable closing condition rather than a post-sale dispute.

In a fraudulent variant, the commercial director cannot obtain confirmation from the holding company and presses for payment to an unrelated account. The buyer does not need to determine whether the problem is impersonation, internal misconduct, or a misunderstanding before declining to proceed. The unresolved authority gap is enough. Corporate complexity is a reason to verify carefully, not a reason to suspend verification in the name of getting the deal done.

Back to the contents

Chapter 13: Privacy, Anonymous Buyers, and Legitimate Confidentiality

Confidentiality can be commercially sensible in a domain transaction. A company may not want to announce a new product before acquiring its preferred name. A seller may not want employees, competitors, or customers to know that an asset is being considered for sale. The presence of privacy does not make a deal suspicious. The danger is allowing confidentiality to become an excuse for eliminating accountability or preventing independent verification.

A useful distinction is between privacy from the public and anonymity from every responsible participant in the transaction. The first can be compatible with a well-controlled deal. The second may leave nobody able to identify the contracting party, confirm authority, or pursue a remedy. Design the process so that sensitive information reaches the people who genuinely need it through appropriate channels, even when it does not reach everyone involved in the negotiation.

Decide what is confidential and why

Identify the information that needs protection. It might be the buyer’s planned launch, the seller’s minimum price, the parties’ identities, the sale price, or operational information revealed during due diligence. These categories do not necessarily require identical treatment. A broker can shield a buyer’s commercial strategy while still ensuring that the final agreement and payment process identify the legally relevant parties appropriately.

Ask whether secrecy serves a legitimate business purpose or merely prevents someone from asking a necessary question. “Please do not announce our acquisition before closing” is different from “You must not contact the escrow provider independently.” “Our counsel will verify the corporate documents confidentially” is different from “Nobody is allowed to know who owns the domain.” The content of the restriction matters more than its formal label.

Document confidentiality obligations in a form suitable for the transaction. Avoid assuming that a sentence in an email resolves every disclosure issue. Counsel can help define permitted recipients, required disclosures, duration, and what happens if the deal does not proceed. A practical arrangement normally needs room for advisers, service providers, and legally required reporting rather than demanding absolute silence under all circumstances.

Use intermediaries to preserve privacy, not erase identity

A buyer’s broker can approach a domain owner without immediately revealing a client’s brand strategy. That can be useful when premature disclosure would disrupt negotiations or reveal a confidential project. The broker should accurately describe its role and avoid inventing an identity, authority, or existing ownership interest. Privacy is not a license to misrepresent material facts.

As the deal progresses, establish who will be bound by the purchase agreement and how the relevant transaction provider will verify participants. Some structures may involve an intermediary acting in its own capacity; others involve an agent for a disclosed or confidential principal. Those arrangements have different implications and should be understood by the parties and advisers. Do not let the phrase “confidential buyer” conceal uncertainty about who owes the purchase price.

For sellers, the same principle applies. A broker may handle inquiries and protect the owner’s personal contact information. But a buyer still needs an adequate basis for believing that the broker is authorized and that the eventual seller can transfer the rights. The broker’s reputation contributes confidence only when the person contacted is genuinely that broker and the specific engagement has been verified.

Protect information in stages

Match disclosure to the stage of the transaction. An initial inquiry usually does not require registrar credentials, identity documents, complete customer records, or private financial statements. A qualified buyer may later need more evidence, but disclosure should follow a defined purpose and an appropriate confidentiality arrangement. Giving everything away early does not make a seller more credible; it may simply increase exposure.

A staged process can begin with basic asset information and non-sensitive supporting material. After the parties establish a plausible transaction, more detailed evidence can be reviewed through a controlled channel. Highly sensitive documents may be shared with counsel or a verified provider rather than circulated through the entire negotiation group. Keep a record of what was shared, with whom, and for which purpose.

Apply the same discipline to the buyer. A seller may reasonably seek evidence that the buyer can complete the purchase, but that does not justify unrestricted access to the buyer’s bank account or internal strategy. Discuss a proportionate verification method with the relevant provider or adviser. A genuine funding check should not require sharing passwords, one-time codes, or unrelated commercial secrets.

Recognize confidentiality used as isolation

A scammer may present secrecy as a condition of receiving an extraordinary opportunity. The proposed buyer supposedly works for a famous company, but you must not contact that company. The supposed escrow officer claims that a private banking arrangement cannot be discussed with ordinary support. The alleged lawyer warns that asking your own counsel for advice will invalidate the deal. Each restriction targets a channel that might expose the impersonation.

Respond by stating the verification you require without debating the stranger’s authority. You can agree not to publicize a transaction while insisting on independent authentication of the service provider. You can protect a client’s identity while requiring a real, accountable contracting structure. A counterparty who rejects every reasonable confidential verification method is not offering privacy; they are asking you to accept an uncheckable claim.

Be especially cautious when confidentiality arrives together with a request for an irreversible act. Sending funds, disclosing transfer secrets, assigning rights, or deleting evidence should never become acceptable merely because a deal is described as sensitive. The higher the consequence of the action, the more important it is that an authorized participant can independently verify the instruction.

Worked example: the secret acquisition

A hypothetical startup engages a broker to acquire a name for an unreleased product. The broker initially contacts the owner without identifying the startup. The owner is willing to discuss a sale but worries about wasting time with an anonymous buyer. The broker explains the representation accurately, establishes its own identity independently, and proposes a staged process that protects the client’s launch plans while providing an accountable route to closing.

As terms become serious, the appropriate parties and provider complete the necessary verification. Counsel handles sensitive identity and authority questions under agreed confidentiality terms. The seller does not learn the startup’s entire business plan, and the buyer does not receive the seller’s registrar password. Both obtain the information needed for their responsibilities. The transaction remains private without becoming unverifiable.

Now change one fact. An unknown intermediary insists that no lawyer, provider support team, or company representative may be contacted and demands a private transfer fee to reveal the buyer’s identity. That is not equivalent to the brokered structure above. The seller should decline the payment and require independent verification. The word “confidential” cannot transform a stranger’s pay-to-proceed demand into a sound transaction process.

Plan what happens after the deal

Agree whether either party may announce the sale, disclose the price, name the other party, or use the transaction as a case study. A buyer may regard a launch date as sensitive; a seller or broker may want to report a completed sale. Resolve those expectations before publicity becomes a disagreement. Do not assume that a private negotiation automatically authorizes a public testimonial or that an undisclosed price may be published because someone considers it good marketing.

Consider document retention as well. Some records may need to be retained for legal, accounting, compliance, or dispute purposes. Other material may no longer be necessary. Establish sensible access controls and retention practices with the relevant advisers rather than promising universal deletion that a provider cannot lawfully perform. Confidentiality should remain workable after completion, not disappear when the money arrives.

The safest private transaction is not the one with the fewest identified people. It is the one in which each necessary participant is authenticated, each disclosure has a purpose, and each obligation has a responsible party. A skilled broker can make that balance easier, especially for a strategic acquisition. Privacy becomes a professional service when it protects the client’s interests without concealing the facts required to complete a legitimate deal.

Back to the contents

Chapter 14: Phishing Emails, Lookalike Addresses, and Hijacked Conversations

An email does not become trustworthy because it arrives during a real negotiation. In fact, a genuine transaction can provide the perfect cover for a fraudulent instruction. The message may mention the correct domain, price, people, and closing date. It may appear in an existing conversation. Those details can make the request feel familiar while doing nothing to establish that the person sending it is authorized to change the payment or transfer process.

The FBI describes spoofing and phishing as methods used to disguise a communication’s origin or lure a recipient into disclosing information or taking harmful action. Its business-email-compromise guidance emphasizes the risk of fraudulent financial instructions that appear to come from trusted parties. ^{[31] [8]}

For domain deals, the practical response is to authenticate consequential instructions independently rather than trusting presentation, timing, or thread continuity.

Inspect the address, but understand the limit

Look at the actual sender address rather than only the display name. Compare it with the verified address already recorded for the participant. Watch for an added word, altered extension, missing character, or subtle spelling difference. A familiar name above an unfamiliar address is a discrepancy worth investigating. Do not reply to the questionable message to ask whether it is genuine; that simply lets the sender reassure you.

Address inspection is only an initial check. A compromised legitimate mailbox can send from the expected address. A conversation may have been monitored, and a criminal may know exactly when the parties expect payment instructions. Therefore, even a perfect address match should not authorize a material bank-detail change or an unexpected request for a transfer secret.

Email authentication indicators can provide technical information, but they should not be treated as a verdict about the sender’s intentions or the legitimacy of the transaction. An attacker may operate a properly configured lookalike domain, or misuse a genuine account. Most buyers and sellers are better served by an established verification procedure than by trying to turn one technical header into a substitute for that procedure.

Remove links from the trust decision

When a message says that your escrow account, registrar account, or marketplace transaction needs attention, access the service through a route you established independently. Use a known bookmark or enter the verified address yourself. Then inspect the account for the claimed event. A link in a suspicious message should not be the mechanism by which you decide whether that same message is legitimate.

A polished login page, familiar logo, or secure-connection indicator does not establish that the site belongs to the expected organization. The important comparison is the actual destination and the independently known provider. If you cannot confidently establish it, contact the provider through a verified support route. Do not enter credentials to see what happens or assume that a failed login means your password was not captured.

Treat attachments and shared-document invitations with similar care. A purchase agreement may be delivered through a legitimate signing platform, but a message bearing that platform’s name is not self-authenticating. Confirm unexpected document requests through the agreed communication channel. Avoid installing software, enabling unusual document features, or granting account access simply to view what is supposedly an ordinary sales document.

Notice changes in the conversation’s behavior

A hijacked thread often asks you to do something different from the established plan. The bank account has changed. The escrow provider is suddenly unavailable. The seller wants a direct payment instead. The broker asks for a code that was previously supposed to go through a secure workflow. The explanation may be plausible, but the change itself should trigger a fresh approval process.

Watch for pressure to bypass other participants. A message may ask you to remove the lawyer from the thread, contact a new “private” address, or avoid calling because the sender is traveling. Any one of these circumstances can occur legitimately. The control is not to accuse everyone who travels; it is to refuse to let an explanation waive independent verification of a high-consequence request.

A sudden change in tone or grammar can be a useful clue, but a convincing writing style is not a safety guarantee. Fraudulent messages may be fluent and personalized. Do not build the process around catching awkward language. Build it around actions that require confirmation regardless of how well the request is written.

Respond according to what was exposed

If you merely received a suspicious message, preserve it and verify the underlying claim through the real provider. If you clicked a link but entered nothing, review the event with appropriate technical support rather than assuming either total compromise or complete safety. If you entered credentials, approved an authentication request, downloaded software, or disclosed a code, treat that as a more serious exposure and act promptly through trusted channels.

Account recovery should include the surrounding access environment, not just a password change. Ask the provider or your security team to review active sessions, recovery methods, forwarding arrangements, and delegated access where relevant. The correct steps depend on the service and the exposure. Do not accept remediation instructions from the same unverified contact who supplied the suspicious link.

If money or a domain has already moved, use the incident-response chapters rather than continuing the negotiation as normal. Contact the relevant financial institution or registrar promptly, preserve evidence, and alert the genuine transaction participants through independently verified routes. Explain exactly what occurred without waiting to determine every technical detail. Early containment and accurate information are more useful than a perfect theory delivered too late.

Worked example: the familiar thread with a new beneficiary

A hypothetical buyer is closing a premium-domain purchase. The price and agreement are settled. An email appears in the existing thread, apparently from the closing coordinator, stating that the original beneficiary account is under maintenance. It supplies new bank details and asks the buyer to send the funds before the seller’s local banking day ends. The message quotes the correct purchase price and includes the real agreement as an attachment.

The buyer follows the established protocol instead of the email’s urgency. They access the genuine transaction account and call the provider using the number recorded before the negotiation. The provider confirms that no approved payment change exists. The buyer does not wire the money, and the genuine participants investigate the compromised communication route. The criminal’s knowledge of the deal did not defeat the control because knowledge was never accepted as authority.

Had the buyer relied only on spelling, logos, or the attached contract, the instruction might have looked persuasive. The decisive question was whether the authenticated provider independently confirmed the change. This is why a second channel should be established early. A verification procedure invented after suspicious instructions arrive may itself be supplied or manipulated by the attacker.

Make suspicious messages useful evidence

Preserve the original message and associated details where possible rather than keeping only a cropped screenshot. Record the time received, the action requested, any links or account details, and what you actually did. Do not alter the evidence to make it look cleaner. Providers and investigators may need the original context to understand the event and distinguish the genuine participants from the impersonator.

Report through the real organization’s appropriate channel, and keep internal distribution proportionate. Forwarding a malicious attachment widely can create a new exposure. A concise warning that identifies the affected transaction and tells staff not to act on the disputed instruction is often more useful than circulating every suspicious file. Let qualified technical personnel decide how to inspect potentially harmful material.

A broker can help maintain a stable communication plan and recognize transaction-specific anomalies, but clients should not surrender their own verification responsibilities. The strongest arrangement gives every participant permission to pause a consequential change. In a legitimate deal, a short verification step protects everyone. In a fraudulent one, it may be the point at which an apparently ordinary email stops being an instruction and becomes evidence.

Back to the contents

Chapter 15: Phone Calls, Video Meetings, and AI-Assisted Impersonation

Hearing a familiar voice or seeing a convincing face can feel more reassuring than reading an email. That reassurance should not become a substitute for transaction controls. A caller can know details from earlier messages, imitate an expected role, or appear during a moment when the real participant is difficult to reach. The central issue is not whether the conversation feels human. It is whether the person is authenticated and authorized to request the action at hand.

Official FBI warnings have described malicious impersonation campaigns involving artificial-intelligence-generated voice messages and other communications. ^[32] That evidence supports caution about relying on voice alone; it does not justify assuming that every unusual call is synthetic. Whether an impersonation uses advanced software, a skilled human caller, or a compromised account, the same practical defense applies: verify material instructions through a route established independently.

A meeting is evidence of contact, not a complete identity check

A video meeting can help participants discuss a transaction, assess whether expectations align, and resolve ordinary misunderstandings. It may also contribute to an identity-verification process. But merely seeing someone on a screen does not establish their relationship to a company, their right to sell a domain, or the authenticity of the bank details they provide. Those claims require their own evidence.

Avoid relying on visual tests improvised during a high-value transaction. Asking someone to wave, turn their head, or repeat a phrase may create confidence without resolving the actual authority question. The buyer still needs to know whether the person is the authorized seller, and the seller still needs a verified funding process. Technical authenticity and legal authority are different problems.

Likewise, a call from a familiar-looking telephone number is not sufficient approval for a payment change. Record the number through a trusted source before the critical stage of the deal, and initiate the verification yourself. If a suspicious caller gives you a number to use for confirmation, that is still part of the caller’s information environment rather than an independent check.

Establish the callback route in advance

At the start of a serious negotiation, agree how the parties will verify consequential changes. Record an independently obtained contact route for the broker, provider, and relevant client representative. For a company, this may involve an established switchboard or a contact whose relationship has already been authenticated. The precise method varies, but it should not depend solely on details introduced with the disputed instruction.

When a call requests a change, end the decision-making portion of that call and use the agreed route. State that the process requires independent verification. You do not need to debate whether the caller sounds genuine. A legitimate participant can accommodate a control that was agreed in advance, and an honest urgent situation does not become less urgent because it is verified correctly.

Keep a record of the verification outcome and what was approved. “Spoke to the seller” is less useful than a note identifying the verified contact route, the exact change discussed, and the resulting instruction. For material amendments, obtain the appropriate written confirmation in the authoritative transaction record as well. A verbal discussion should not silently override the signed agreement or provider’s workflow.

Keep remote-access requests outside ordinary negotiation

A supposed broker or support representative may offer to complete the process by taking control of your computer. For an ordinary domain sale, an unexpected request to install remote-access software or share your screen while handling credentials deserves a stop. Do not let convenience erase the difference between explaining a procedure and acquiring access to the systems that control your assets and money.

There can be legitimate technical-support arrangements, but authenticate the provider, define the scope, and use your organization’s approved process. Avoid exposing passwords, recovery codes, banking screens, or unrelated accounts. A buyer does not need remote access to the seller’s registrar account to evaluate a name, and a seller does not need access to the buyer’s banking session to confirm payment.

Screen sharing can also reveal more than intended. Browser tabs, notifications, saved account names, documents, and internal messages may disclose useful information to an attacker. Prepare a limited environment for legitimate demonstrations and stop sharing before accessing sensitive systems. The safest demonstration shows the specific evidence required without creating a general view into the participant’s digital life.

Beware of staged authority and social pressure

A fraudulent call may include multiple supposed professionals: a broker, an escrow manager, a lawyer, and a technical specialist. Several voices agreeing with one another do not create independent evidence if the same attacker controls the setting. The performance can make a target reluctant to interrupt or appear inexperienced. Your process should permit a pause regardless of how many people are waiting on the call.

The same applies when a caller invokes a famous company or wealthy buyer. A prestigious name can explain why confidentiality matters, but it does not authenticate the caller. Verify the intermediary’s identity and representation through appropriate channels. Do not send money for an appraisal, compliance certificate, or supposed release requirement merely because the request was delivered in an impressive meeting.

A broker can help clients resist this social pressure by defining a rule that material changes are never approved live without the agreed checks. That rule removes the burden of making an accusation. The participant can say, accurately, that the transaction process requires confirmation. A well-run deal does not depend on one person being comfortable challenging a room full of apparent experts.

Worked example: the urgent voice message

A hypothetical seller receives a voice message that sounds like their broker. It names the domain and buyer, says the closing is nearly complete, and requests a transfer code immediately because the broker is boarding a flight. The message provides a new number for a temporary closing assistant. The seller recognizes the voice and is tempted to comply before the opportunity disappears.

Instead, the seller uses the broker’s previously verified contact route. The real broker confirms that no such instruction was issued and that the agreed service does not require sending the code to the new number. The seller preserves the message and alerts the relevant participants. Whether the voice was generated, edited, or impersonated by a person is important for investigation, but not necessary for the initial decision to stop.

In a legitimate variation, the broker really is traveling and confirms through the established route that a new coordinator has been appointed. The parties then verify that coordinator and update the documented process before any secret or asset is released. The control does not prohibit delegation. It makes delegation explicit and authenticated rather than allowing a hurried message to create authority by itself.

Train for the action, not the technology

Teams do not need to become experts in detecting every possible synthetic-media technique before they can protect a domain transaction. They need to recognize the actions that deserve independent approval: changing beneficiaries, releasing funds, disclosing transfer credentials, adding administrators, altering recovery details, and waiving closing conditions. These actions remain important even when the communication technology changes.

Practice a few realistic scenarios before a major closing. Ask who would receive an urgent call, which number they would use to verify it, and who could authorize an exception. Remove exceptions that depend only on seniority or pressure. An executive’s apparent voice should not be able to bypass a control designed to protect the executive’s own business.

The goal is not permanent suspicion of every conversation. Calls and meetings are useful tools for legitimate transactions. The goal is to give them the right evidentiary weight. Conversation can explain an instruction; it should not automatically authenticate it. A professional broker, supported by a clear client protocol, helps preserve that distinction so that a convincing performance cannot quietly become permission to move money or surrender a valuable domain.

Back to the contents

Chapter 16: Fake Screenshots, Forged Documents, and Misleading Proof

A screenshot can show what someone wants you to believe without showing what the underlying system actually says. A document can contain accurate names and impressive formatting while being unauthorized, altered, or unrelated to the transaction. In domain buying and selling, evidence should be evaluated by its origin, relevance, and independent verifiability—not by how official it looks on a screen.

The right response is not to reject all documents. Contracts, invoices, account records, and provider confirmations are essential parts of many legitimate deals. The task is to distinguish an authentic record obtained through a trustworthy route from an image supplied by someone whose claim is still being tested. Good verification asks where the evidence came from, what it proves, and what important questions it leaves unanswered.

Identify the proposition the document is meant to prove

A seller may send a registrar screenshot to prove control, an old invoice to prove ownership, and an identity document to prove who they are. Each item addresses a different proposition, and each may address it only partially. A screenshot of an account can be fabricated or outdated. An invoice may concern a prior registrant. An identity document may belong to someone other than the person conducting the negotiation.

Write the intended proposition in plain language. For example: “The named company currently authorizes this person to sell this exact domain.” Then ask whether the supplied evidence actually supports that statement. A company certificate showing that the entity exists does not answer the authority question. A working website does not answer it either. This exercise prevents a stack of impressive but irrelevant records from becoming a substitute for the missing proof.

Also distinguish authenticity from truth. A real email from a real employee can contain an unauthorized instruction. A genuine signed agreement can make a false representation. A true statement about past ownership can be misleading about present rights. Verification is therefore not complete merely because you establish that a document was not digitally edited.

Prefer direct access to the authoritative system

When a transaction provider reports that funds have arrived, confirm the status in your genuine account or through an authenticated support route. Do not release a domain because the buyer sends an image of a bank transfer or a supposed provider message. The buyer’s evidence may show that they initiated something, not that the required funds are available under the agreed transaction process.

When a seller supplies a public registration record, obtain a fresh record yourself. When a company document can be checked against an official register, use that source appropriately. When a broker claims an engagement or a provider confirms a case number, verify through the organization’s independently established channel. The closer the check is to the responsible system or party, the less you depend on the counterparty’s presentation.

Direct verification still has limits. A provider dashboard can accurately report a transaction status without guaranteeing clean title to the domain. An official register can accurately identify a company without establishing the signer’s authority. Use authoritative systems for the facts they are responsible for, then address the remaining questions separately.

Treat seals, signatures, and certificates proportionately

An electronic signature can be part of a legitimate contract process, but the presence of a signature image does not by itself authenticate the signer or resolve authority. Check the signing workflow, the identity of the parties, and the document version. For a material transaction, counsel can advise on execution requirements and evidence appropriate to the relevant jurisdictions.

Similarly, a stamp, notarization, or certificate may have a limited legal function. Do not assume that it guarantees the truth of every statement in the document or the legitimacy of the entire deal. A scammer may also invent a certificate that no real authority requires. Ask who issued it, under what process, what it actually certifies, and how its issuance can be independently confirmed.

Avoid paying for a document simply because a stranger says it will unlock a buyer’s money. A legitimate due-diligence expense should have a clear purpose, a known provider, and a defined place in the transaction. A required purchase from an obscure, counterparty-selected site is a different proposition. The appraisal and advance-fee chapters examine that pattern in detail.

Look for context that has been removed

A cropped screenshot may hide the account owner, the date, the exact domain, or a status qualifier. A revenue statement may omit refunds and costs. An email excerpt may omit the message that changed its meaning. A transaction receipt may show a pending event rather than a completed one. Ask for enough context to understand the claim without demanding unrelated confidential information.

For portfolios, pay particular attention to lists. A summary image may show a count of names without proving which names are included. A spreadsheet can contain hidden rows, duplicates, obsolete entries, or a mix of owned and merely proposed assets. Compare a complete, agreed plain-text schedule with the contract and delivery evidence. The value of the package depends on its actual contents, not the apparent size of the file.

Keep versions of important documents. If the domain list, beneficiary, seller entity, or acceptance terms change, record the change explicitly. A revised attachment can be legitimate, but it should not quietly supersede the approved version without review. The more consequential the change, the more important it is that all responsible participants know which version governs the next action.

Worked example: the impressive funding package

A hypothetical seller receives a message from a buyer containing a bank receipt, a photograph of an identification card, and a screenshot of an escrow dashboard. The buyer says the money is fully secured and asks for immediate delivery. The documents display the correct price and domain. The seller is tempted to conclude that three pieces of evidence must be better than one.

The seller instead accesses the genuine escrow account through the established route. No funded transaction matching the agreement appears. The provider confirms that the purported dashboard does not correspond to its record. The seller stops and preserves the material. The bank receipt and identity image do not compensate for the missing authoritative funding confirmation; they merely make the unsupported claim look more substantial.

In a legitimate alternative, the provider confirms that the transaction is funded under the agreed terms, while a pending technical step remains. The seller then follows the provider’s actual delivery instructions rather than the buyer’s improvised ones. Verification has resolved the specific funding question without assuming that it also settles ownership, inspection, or every other closing condition.

Preserve evidence without becoming an investigator by accident

Keep original files where possible and note when and how you received them. Avoid editing the only copy, stripping context, or repeatedly converting it between formats. If technical inspection is needed, involve someone qualified and use a safe environment. Do not open suspicious attachments on a sensitive device merely to satisfy curiosity about whether they are fake.

Do not publicly accuse a named party based solely on an odd-looking document. The apparent sender may be impersonated, and a formatting anomaly may have an innocent explanation. Describe the discrepancy accurately to the relevant provider or adviser: the claimed transaction is absent, the signer’s authority is unconfirmed, or the document names a different asset. Precise reporting helps investigation and avoids turning suspicion into an unsupported factual allegation.

A qualified broker can reduce the burden of document review by recognizing which records normally belong in the process and which questions deserve specialist attention. The broker’s role is not to pronounce every attractive PDF genuine. It is to connect each claim with a credible source and ensure that unresolved gaps remain visible. Evidence becomes useful when it changes a decision for a defensible reason, not when it merely makes the transaction folder look full.

Back to the contents

Chapter 17: Build a Communication Protocol That Cannot Be Changed Casually

Many domain scams succeed at the moment a transaction’s normal process is replaced by an exception. The parties have agreed to use escrow, but a message requests a direct wire. The seller has authorized a specific broker, but a new assistant asks for the transfer code. The buyer has approved one asset schedule, but a revised attachment substitutes a different name. A communication protocol makes these changes visible and gives everyone a legitimate reason to pause.

The protocol need not be elaborate. Its purpose is to identify the authoritative record, the authorized participants, and the actions requiring independent confirmation. A small deal may use a short written agreement and a verified provider account. A strategic acquisition may need a more formal closing plan. What matters is that the process exists before a suspicious message or urgent deadline invites the parties to improvise.

Create a transaction contact sheet

Record the exact domain or portfolio schedule, the contracting parties, the broker’s role, the legal advisers where engaged, and the selected transaction provider. For each participant, identify the verified communication route and the scope of their authority. A technical administrator may coordinate transfer steps without being authorized to change the sale price. A broker may negotiate terms without being permitted to receive client funds.

Establish contact information independently where appropriate. Do not build the entire sheet from one unverified email. A provider’s support route should come from its genuine site or an existing authenticated account. A corporate signer’s role should be confirmed through a suitable company channel. The contact sheet is only as reliable as the process used to create it.

Keep the sheet accessible to the people who must act during closing, but do not turn it into a repository of passwords or transfer secrets. It should tell participants whom to contact and what they may approve. Credentials belong in the relevant secure systems and should be handled through the authorized workflow. Mixing ordinary coordination details with sensitive secrets makes accidental disclosure more likely.

Choose an authoritative place for consequential instructions

Decide where funding status, agreed terms, delivery instructions, and acceptance will be recorded. The answer may involve more than one system, but the roles must be clear. The signed agreement defines legal obligations; the genuine provider account records the provider’s transaction status; the closing checklist coordinates operational tasks. A casual chat should not silently override all three.

If a participant sends a material instruction elsewhere, require it to be reconciled with the authoritative record before action. This does not mean every ordinary question needs a formal amendment. It means that changes affecting money, rights, identity, asset scope, or release conditions deserve a controlled update. A message saying “ignore the agreement for now” should create a stop, not a shortcut.

Avoid unnecessary parallel channels. Multiple email threads, messaging apps, shared documents, and private calls can make it difficult to know which version is current. Use the channels that genuinely serve the deal, and summarize material decisions in the agreed record. Confidential side discussions may be appropriate, but they should not create undisclosed instructions for the person responsible for releasing an asset or payment.

Define the changes that trigger re-verification

At minimum, treat a new beneficiary, a different payment route, a replacement escrow site, a new seller entity, a new authorized signer, an altered domain schedule, or a changed transfer destination as a material event. The precise list can be adapted to the deal. The key is that a change requires verification because of its consequence, not because someone happens to find the message suspicious.

Specify who may approve each change and how that approval will be obtained. For a company, consider whether two appropriately authorized people should review a significant payment instruction. For an individual, an independent callback and confirmation through the genuine provider may be more practical. Controls should fit the transaction without becoming ceremonial steps that everyone learns to bypass.

A new contact should not authenticate themselves by supplying their own verification route. Confirm the appointment with an existing verified participant, then establish the new contact’s details. Record whether the previous contact remains authorized. This is particularly important when a supposed assistant appears near closing and claims to be taking over because the usual person is unavailable.

Give everyone the right to stop

A control is ineffective if the person noticing a discrepancy feels unable to delay a senior colleague or a valuable buyer. State in advance that unresolved identity, payment, asset, or authority issues pause the relevant action. The pause should not require proving fraud. An inconsistency is enough to ask for clarification and independent confirmation.

Define an escalation route so that a pause leads somewhere useful. The person who spots a bank mismatch should know whether to contact the financial institution, provider, broker, or internal approver. The person who sees a transfer lock should know who will obtain the registrar’s explanation. Without an owner, a stop can become a stalemate; with an owner, it becomes a manageable issue.

Do not allow “the client is in a hurry” to become a blanket exception. A client can choose whether to proceed after receiving a clear risk explanation, but should not unknowingly waive controls because the team hides the problem beneath urgency. A competent broker helps distinguish a genuine commercial deadline from a pressure tactic that asks the client to act without the agreed evidence.

Worked example: the replacement coordinator

A hypothetical portfolio sale has a verified broker, a signed asset schedule, and a transaction-provider account. Two days before closing, a new email correspondent says the broker has appointed them to handle delivery. They request that the seller move the domains into a newly supplied registrar account and explain that the original coordinator is unavailable. The message uses the correct transaction reference.

The seller checks the contact sheet and finds no authorization for the new person. They contact the broker through the established route. The broker confirms that the appointment is genuine but that the requested destination was not approved and should not be used. The parties investigate whether the message was altered or the new coordinator made an error, then update the authoritative instructions after the issue is resolved.

The important outcome is that a legitimate delegation did not automatically validate every instruction attributed to the delegate. Identity, authority, and the requested action were checked separately. In a fraudulent version, the broker would deny the appointment entirely. The same protocol handles both situations without forcing the seller to decide from tone or appearance whether the message is malicious.

Close the communication loop after completion

When the transaction completes, record that fact through the agreed channels and identify any remaining obligations. Remove temporary access where appropriate, update contact responsibilities, and preserve the final versions of the agreement and asset schedule. A deal should not remain indefinitely open to messages claiming that one more undocumented payment or transfer is required.

Warn relevant participants about the possibility of follow-on impersonation. A scammer who knows a transaction occurred may send a fake refund, tax, release, or recovery request later. The same independent-verification rule should continue to apply. Completion changes the legitimate tasks, but it does not make an unexpected message from a familiar-looking sender automatically trustworthy.

A good communication protocol is a practical service to every honest participant. It reduces confusion, prevents accidental contradictions, and makes manipulation harder. For a valuable domain transaction, a qualified broker can organize this structure and keep it current. The best test is simple: if an attacker inserted one convincing message into the deal tomorrow, would that message alone be enough to move money or control? A sound protocol makes the answer no.

Back to the contents

Chapter 18: Fake Renewal Invoices and Domain Slamming

A domain renewal scam begins with a familiar business obligation: keeping a registration active. The attacker presents a payment demand that looks like the next routine bill. Sometimes the supposed renewal is entirely fictitious. Sometimes the notice is a solicitation for a transfer or unrelated service, designed to be mistaken for an invoice from the existing registrar. The risk is greatest when the recipient pays from appearance and urgency instead of checking the real account.

The FTC has brought enforcement actions concerning deceptive domain-registration solicitations, including a cross-border scheme described in a 2010 announcement. ^[13] The historical example establishes that the pattern is real; it does not mean every unfamiliar renewal offer is fraudulent. Your practical task is to identify the service being sold, the party entitled to provide it, and whether any action is actually required for your domain.

Know who currently manages the registration

Maintain an internal record of each important domain’s registrar, renewal date, authorized account holder, and payment responsibility. For a business, make this record accessible to the people who process invoices, not just the technical team. An accounts-payable employee cannot reliably reject an imitation bill if nobody has told them which provider legitimately handles the registration.

Check renewal status inside the genuine registrar account through a trusted route. Do not use the payment link or telephone number on the questionable notice as the sole verification method. If the domain is managed through a reseller or agency, establish that relationship in advance and know how to confirm an authentic charge. A reseller arrangement can be legitimate, but it should be documented rather than discovered under payment pressure.

Compare the exact domain, service period, provider name, and requested action. A notice may refer to a domain you once owned, a similar spelling you never registered, or a different extension. It may also quote a genuine expiration date obtained from public information. Accurate background details do not prove that the sender is your provider or that paying them will renew the registration.

Read the transaction hidden inside the notice

Ask whether the document is an invoice for an existing service, an offer to switch providers, an optional protection package, or a directory listing. Look beyond the heading. A document can say “domain notice” prominently while describing a different service in smaller text. The issue is what you would authorize by paying or signing, not simply whether the sender used the word renewal.

Domain slamming commonly refers to deceptive efforts to induce an unwanted provider change. A transfer can be a legitimate commercial choice when the registrant understands and authorizes it. It becomes problematic when the communication is designed to make the recipient believe the transfer is necessary to retain the domain or is merely payment to the existing registrar. Do not confuse the legitimacy of transfers generally with the honesty of a particular solicitation.

Watch for requests that go beyond payment. A supposed renewal notice may ask for an authorization code, registrar login, or approval of a transfer message. Ordinary renewal and inter-registrar transfer are different actions. If a notice combines them without a clear explanation, stop and verify with your current provider. A payment-processing employee should not be asked to release a transfer secret as part of routine invoice handling.

Build an invoice approval rule

Require domain-related invoices to be matched against the asset register and approved supplier record. If the supplier is new, route the document to the person responsible for domain administration before paying. If the service is optional, obtain explicit approval from the appropriate budget owner. The process should make it difficult for a solicitation to become an obligation merely because it resembles an invoice.

For a portfolio, reconcile renewal charges against the actual names and periods being renewed. A large list can hide a few unauthorized or obsolete entries. Check whether the provider’s account shows the expected renewal after payment. Keep the confirmation with the invoice so that accounting evidence and registration evidence remain connected. Paying a bill is not the same as verifying that the intended asset was renewed.

Set internal reminders independent of unsolicited notices. A business that knows its renewal calendar is less vulnerable to a stranger announcing an emergency. At the same time, do not ignore a genuine expiration problem because an earlier fake notice made the team suspicious of all messages. Use the real account as the source of truth and resolve actual renewal needs through the verified provider.

Respond when an employee has already paid

Determine what was purchased or authorized. Was money sent for a nonexistent renewal, an unwanted directory service, or a transfer that has begun? Contact the payment provider and the legitimate registrar promptly through trusted routes. Preserve the notice, payment details, and any approvals. The appropriate response depends on the event; a refund request alone may not address a transfer or credential exposure.

If login information or an authorization code was disclosed, treat that as a separate security incident. Secure the relevant accounts and ask the registrar to review the domain’s status. Do not assume that canceling a card payment also cancels every technical action. Likewise, a transfer that has not completed may still require attention under the provider’s procedures.

Avoid making promises about recovery. Payment remedies, transfer responses, and legal options depend on the facts and applicable rules. Record what the providers say and who owns each follow-up task. The immediate goal is to contain further harm and establish the current status of the domain, not to win an argument with the sender of the notice.

Worked example: the routine-looking annual bill

A hypothetical company receives a paper notice for a domain used by one of its product teams. The document prominently displays the name and a payment deadline. The accounts-payable clerk recognizes the domain and prepares to pay. Under the company’s approval rule, however, any domain invoice from an unlisted supplier is referred to the domain administrator.

The administrator accesses the genuine registrar account and confirms that the domain is already renewed. Reading the notice carefully reveals that the payment would purchase an unrelated promotional listing. The company does not pay and records the sender as an unapproved solicitation source. The control worked because the clerk checked the supplier and service, not because the document contained an obvious spelling error.

In another version, the domain really is approaching expiration. The administrator still renews through the verified provider rather than paying the unsolicited sender. A true deadline does not authenticate a false bill. The company resolves the real operational need while declining the misleading offer, demonstrating why independent account access is more reliable than trying to judge urgency from the notice alone.

Make the lesson part of acquisition and handover

When buying a domain, obtain a clear understanding of the receiving registrar’s renewal arrangements and any applicable premium or variable fees. Update the asset register immediately after closing. Otherwise, the first unfamiliar renewal message may reach a team that does not yet know the legitimate provider. A secure purchase can be undermined by an unorganized handover.

A broker handling a valuable acquisition can help ensure that responsibility for ongoing registration is explicitly assigned. This is not a reason to route every routine renewal through a broker; it is a reason to include renewal ownership in the closing checklist. The transaction is not operationally complete until someone knows where the domain lives, how it renews, and which provider is authorized to bill for it.

The durable defense against renewal scams is ordinary administrative clarity. Keep accurate records, verify through the real account, distinguish offers from obligations, and separate renewal from transfer authority. A domain should remain registered because your organization deliberately maintains it—not because whichever stranger sends the most convincing invoice gets paid first.

Back to the contents

Chapter 19: Fake ICANN Notices, Compliance Warnings, and Suspension Threats

An official-looking warning can turn an ordinary domain owner into a hurried problem-solver. The message says the registration is noncompliant, a certificate is missing, or suspension will occur unless a fee is paid immediately. It may display ICANN’s name, copy a registrar’s branding, and include the correct domain. The intended effect is to make the recipient obey an apparent authority before checking whether that authority issued the instruction.

ICANN explicitly warns that it does not process registrations, issue registrant certificates, or collect fees directly from registrants. It also cautions against messages using its identity to request credentials or financial information. ^[7] A historical ICANN alert describes fake renewal pages designed to capture payment and personal details. ^[33] These facts provide a useful boundary: a demand claiming to be a direct ICANN renewal or certificate charge requires rejection and independent verification, not hurried payment.

Separate a real obligation from a fake messenger

Registrars can send legitimate account, verification, renewal, and policy-related notices. A domain owner should not respond to scams by ignoring every message that mentions compliance. The safer approach is to access the genuine registrar account independently and check whether the claimed issue exists. Where the dashboard is unclear, contact the provider through a known support route.

Ask which organization is responsible for the requirement and where the requirement is documented. A genuine provider should be able to explain the relevant account issue and the authorized way to resolve it. An email that merely repeats “ICANN rules” without identifying the actual process is not enough. Do not accept a stranger’s paraphrase of a policy as a reason to disclose credentials or send money to an unrelated account.

Keep the proposed action specific. Updating inaccurate contact information, renewing an expiring registration, responding to a dispute, and purchasing a commercial certificate are different matters. A scam may blur them together so that a familiar duty appears to justify an unfamiliar payment. Resolve the real issue through the provider that actually manages it rather than accepting the bundle of actions proposed by the sender.

Recognize invented credentials and clearance documents

A supposed buyer may demand an “ICANN ownership certificate,” an international clearance document, or another official-sounding item before completing a purchase. The title alone proves nothing. Ask who issues the document, what rule requires it, whether the relevant registrar or transaction provider recognizes it, and whether an independent adviser can verify the requirement.

Do not confuse an invented sales requirement with genuine technical or legal documents. A website certificate, a corporate authorization, an identity-verification record, and a domain transfer code serve different purposes. The existence of one legitimate category does not validate every certificate offered by an unfamiliar site. A technical security product, for example, is not a general certificate of lawful ownership or a guarantee that a domain sale is safe.

If the requested document is available only from a site selected by the prospective buyer, examine the payment sequence carefully. Are you being asked to spend money before the buyer makes any verified commitment? Is the promised sale conditional on that purchase? Does the buyer reject reasonable independent alternatives? Those questions reveal the advance-fee structure beneath the official vocabulary.

Do not let a countdown replace authentication

A message may threaten suspension within hours, deletion that evening, or permanent loss of the name unless a link is used immediately. The possibility of a genuine operational deadline makes the threat effective. Your response should be prompt but independent: check the real account, contact the actual provider, and preserve the notice. Promptness does not require trusting the sender’s route.

For a business-critical domain, involve the person responsible for registration and technical operations. They can determine whether there is an actual status change, account restriction, or service interruption. Avoid having an accounts-payable employee or executive improvise technical changes based on a threatening email. The team should already know who handles such notices and how to reach them.

Do not assume that a working website proves the warning is false, or that a nonworking website proves it is true. A domain can have issues not yet visible to visitors, and a website outage can have unrelated causes. Verify the claimed account or registration event directly. The warning’s accuracy is a separate question from the website’s current appearance.

Check supposed support interactions too

After receiving a fake notice, a victim may be directed to a fake support chat or telephone line. The person answering then confirms the invented problem and explains the payment procedure. This is not independent verification; it is a second stage of the same communication. Use a support route obtained from the genuine provider or an established account, not from the disputed notice.

Be cautious if the supposed support agent asks for a password, authentication code, remote access, or payment outside the normal account process. Legitimate support can have identity-verification procedures, but you should understand what is being requested and why. Do not grant broad access simply because the caller claims to be fixing an urgent compliance problem.

Record any case number in the genuine provider’s system. A number printed in an email is not proof that a real case exists. If the provider cannot find the case, describe the message and ask for the appropriate reporting route. Preserve enough information to support investigation without continuing to interact with the suspicious site.

Worked example: the transfer-clearance certificate

A hypothetical seller agrees on a price with an apparent international buyer. Before opening the agreed transaction, the buyer says a new regulatory rule requires the seller to purchase a transfer-clearance certificate from a named website. The fee is modest compared with the sale price, and the website displays institutional logos. The buyer promises reimbursement at closing.

The seller asks the verified registrar and proposed transaction provider whether that certificate is required for the actual transfer. Neither recognizes the claimed requirement. The buyer cannot supply an independently verifiable rule and refuses to proceed without payment to the selected site. The seller ends the discussion and retains the correspondence. The apparent reimbursement promise never became a verified obligation from a genuine purchaser.

In a legitimate variation, the provider identifies a real account-verification step inside its authenticated system. The seller completes that step through the genuine channel without buying an unrelated certificate. The lesson is not that all verification requirements are suspicious. It is that a real requirement has an identifiable responsible provider, a verifiable purpose, and an authorized process that does not depend on trusting a stranger’s link.

Make official-looking notices manageable

Create an internal rule for messages claiming registrar, registry, ICANN, legal, or compliance authority. Route them to a designated owner, preserve the original, and verify through the appropriate institution. Staff should not need to memorize every possible fake notice. They need to know that a logo, deadline, and domain name are insufficient grounds for releasing money or credentials.

Keep genuine account information current and monitor the channels used for important notices. A business that misses real messages may become more vulnerable to a fake one that appears to explain an unexpected problem. Good administration reduces both risks: it helps resolve legitimate obligations and makes invented emergencies easier to detect.

An experienced broker can help identify when a claimed requirement does not fit the transaction, but the relevant provider or qualified adviser should confirm the actual rule. Authority should be traceable, not theatrical. When an official-sounding demand arrives, the safest question is not “How quickly can I satisfy this sender?” It is “Which real organization can independently confirm that this exact action is necessary?”

Back to the contents

Chapter 20: Overseas Registration Warnings and Brand-Protection Pressure

A common pressure message says that another company is about to register your brand under several foreign extensions. The sender claims to have noticed a conflict and offers you a brief opportunity to secure the names first. The message may sound like a courtesy from a registry or a mandatory step in international brand protection. The real objective may be to sell an expensive bundle, collect payment for nonexistent services, or draw you into a larger impersonation scheme.

The nationality or location of the sender is not the warning sign. Legitimate registrars and brand-protection specialists operate internationally, and foreign-market naming decisions can be important. The issue is an unverified claim of authority combined with pressure to buy through the sender. Evaluate the specific extension, rights, provider, and business need instead of treating geography as evidence for or against legitimacy.

Separate the warning from the sales offer

Ask what the sender actually knows. Have they identified a real registration application, a public registration that already exists, or merely a possibility that someone could register a name? Those are different claims. A statement that “another company is interested” may be impossible to verify and may not create any obligation for you. Do not let an unverifiable story become the foundation of a rushed purchase.

Then identify what is being sold. It may be a domain registration, a local-language variant, a monitoring service, a trademark-related service, or an undefined package called an internet keyword. The label should correspond to a specific asset or service with a clear provider, term, price, and renewal arrangement. If you cannot explain what you will receive, you are not ready to approve the payment.

A legitimate commercial offer can be declined or compared with alternatives. A sender who insists that only their firm can protect you, while refusing to identify the relevant registry process, is asking you to accept exclusivity without evidence. Verify the extension and provider independently before deciding whether there is any actual opportunity or threat to address.

Do not assume trademark rights require buying every variant

A business should develop a domain-protection strategy based on its markets, brand, customers, and legal position. That strategy is not the same as buying every name mentioned in an unsolicited message. Trademark rights and domain-registration rights are related but distinct, and their interaction depends on facts and applicable rules. Obtain qualified advice for a material conflict rather than accepting a salesperson’s universal claim about what your trademark requires.

A sender may say that failing to buy a bundle will cause you to lose your existing domain or worldwide rights. Such a sweeping claim deserves particular scrutiny. Ask your own adviser to identify the actual risk and available responses. A genuine legal concern should be evaluated on its merits, not resolved automatically by purchasing the sender’s package.

The reverse mistake is to assume that owning one trademark or one domain prevents every third party from registering any similar name anywhere. That is also too broad. The sensible approach is targeted analysis: which names matter, which uses would create confusion or other legal issues, and which preventive or enforcement measures are proportionate? A broker can assist with acquisition strategy, while counsel handles legal rights and remedies.

Verify the extension and eligibility rules

Some country-code namespaces have local eligibility or other registration conditions. Others differ in transfer procedures, registrant-change requirements, and dispute policies. Do not assume that the familiar process for a .com applies everywhere. Consult the actual registry and a legitimate registrar serving the extension before authorizing a purchase or relying on a promise that the name can later be transferred to you.

Australia provides a concrete example of why extension-specific checking matters: auDA publishes licensing and transfer rules for .au names. ^{[34] [35]} The point is not to memorize one country’s rules for every transaction. It is to recognize that a domain can be technically offered for sale while the proposed buyer still needs to satisfy the applicable conditions.

Ask whether the name will be registered in your organization’s correct name, whether a local presence or trustee arrangement is proposed, and what rights that arrangement actually gives you. Do not treat an intermediary’s account as equivalent to direct control without reviewing the structure. A service may be legitimate yet unsuitable if your business expects a level of independence the contract does not provide.

Build a deliberate defensive-registration plan

Start with the names and markets that matter to your customers. Consider the principal brand, obvious customer-facing variants, relevant local extensions, and the operational ability to maintain them. Set a budget and review schedule. A plan created before a threatening email arrives is less likely to be distorted by the sender’s preferred bundle.

Include ongoing costs and administration. Registering many names creates renewal responsibilities, account-management work, and potential confusion about which domains should be used publicly. A cheap first year can become an expensive recurring commitment. The right number of defensive registrations is a business decision informed by risk and cost, not a competition to own the largest possible list.

Use monitoring and escalation rules where appropriate. A newly registered similar name may deserve observation, a customer warning, legal review, or no action depending on its use and context. Not every similarity requires a purchase, and not every purchase solves the underlying risk. A qualified broker and legal adviser can help distinguish a valuable acquisition from an unnecessary reaction to a sales pitch.

Worked example: the urgent international bundle

A hypothetical manufacturer receives an email stating that a foreign company has applied for six versions of its brand. The sender offers a three-day priority period and a package price substantially above the company’s normal registration costs. The message implies that the manufacturer’s existing brand rights may be lost if it declines. No independently verifiable application record or rule is supplied.

The manufacturer forwards the message to its domain administrator and counsel rather than paying. They check the relevant registry arrangements, identify which proposed names are available, and assess whether those markets matter to the business. They decide that one domain has a genuine strategic use and acquire it through a verified provider under the correct entity. The remaining package is declined.

In another version, an actual conflicting registration is discovered. The company evaluates that specific name and use with counsel, rather than assuming that buying unrelated available variants will resolve the conflict. The original message may have prompted useful attention, but it did not earn authority over the response. Independent analysis determines the action, provider, and budget.

Recognize escalation after you decline

A sender may respond to hesitation with a message supposedly from the competing applicant, a senior registry official, or a legal department. The new correspondent may repeat the urgency and insist that the threat is real. Multiple messages do not create independent corroboration if they originate from the same unverified network. Authenticate each claimed role through a separate, trustworthy route.

Do not reveal confidential expansion plans merely to explain why you are declining. A brief response, or no response where appropriate, can preserve your position without supplying useful commercial intelligence. If you engage a broker for a genuine acquisition, provide the broker with the strategic context under a proper engagement rather than sharing it with the sender of the unsolicited warning.

International domain management deserves thoughtful investment, not panic buying. A strong broker can help prioritize acquisitions and negotiate with real owners; a qualified legal adviser can assess rights and disputes. Together, those services offer a more defensible approach than treating every overseas warning as a deadline imposed by an authority you have never independently verified.

Back to the contents

Chapter 21: Directory Listings, Search Submission Fees, and Unwanted Services

Not every domain-related bill sells a domain-related necessity. A notice may use your web address prominently while charging for a directory entry, a promotional listing, a search-submission package, or another optional service. The problem is not that all such services are illegitimate. It is that the presentation may encourage you to mistake an offer for an existing obligation or believe that payment is required to keep your domain or website functioning.

The FTC’s 2010 domain-registration enforcement announcement described invoices for website-address listings that recipients could mistake for registration charges, along with misleading search-optimization claims. ^[13] The enduring lesson is to identify the actual service and the actual relationship. Familiar domain details on a bill do not establish that you ordered the service, owe the money, or need it to preserve your registration.

Translate the offer into a plain-language purchase

Before approving a charge, write one sentence describing what the money buys. Does it renew a registration at your current registrar? Add a listing to a particular directory? Submit information to specified services? Provide ongoing marketing work? If the answer remains a vague promise to “activate visibility” or “maintain internet presence,” ask for a precise description before considering the expense.

Identify the deliverables, service period, cancellation terms, and recurring charges. An optional annual listing may have little value to your business even when it is genuinely delivered. A recurring subscription may continue after the initial invoice is forgotten. A service can therefore be a poor purchase without being a scam. Keep value assessment separate from the question of whether the seller is misrepresenting an obligation.

Check whether anyone in your organization actually ordered it. Large businesses can receive genuine invoices from unfamiliar vendors, but that possibility should trigger internal verification rather than automatic payment. Match the invoice to a purchase order, contract, or authorized request. A sender’s assertion that “your marketing team approved this” is a claim to check, not a substitute for the approval record.

Distinguish registration, hosting, and marketing

Domain registration maintains the relevant registration rights under the provider’s terms. Hosting supplies infrastructure for a website or related services. Marketing may help people discover the business. These functions can be bundled commercially, but they remain different services. A notice that blurs them can make an optional promotional product sound necessary to prevent domain deletion.

Ask which existing service would actually stop if the invoice were unpaid. Verify that claim with the provider responsible for the service, not merely with the sender. If your registrar account is current and your hosting agreement is separate, an unknown directory vendor should not be treated as the authority controlling either one. The answer should come from the real contractual relationships.

For a newly acquired domain, be especially careful. The buyer may receive unsolicited offers shortly after taking control and mistake them for unfinished closing tasks. Keep the acquisition file separate from new marketing solicitations. The broker or closing coordinator should identify any genuine remaining obligations so that a stranger cannot easily insert an extra “activation” payment into the process.

Examine search promises without buying certainty

A domain can be useful for branding without guaranteeing search visibility. A marketing vendor should explain what work it will perform, how results will be measured, and what assumptions underlie its claims. Be skeptical of statements that payment for a generic listing automatically secures a particular ranking or that an official-sounding fee is required to make a website eligible for ordinary search discovery.

Google’s guidance emphasizes helpful, people-first content and explicitly rejects the idea that there is a preferred word count that publishers should target merely for ranking. ^[36] That does not evaluate every marketing service, but it illustrates why simple formulas and guaranteed outcomes deserve scrutiny. A service should be judged by a credible scope and evidence, not by an invented shortcut to search-engine approval.

Ask whether the seller is promising an action they control or an outcome they do not. Creating a directory entry is a deliverable. Guaranteeing that customers will find and buy from your business is a much broader claim. A legitimate provider can discuss uncertainty and measurement. A seller who treats every question as a threat to an expiring discount is making the decision harder to evaluate, not easier.

Control recurring and bundled charges

Read whether the initial payment enrolls you in automatic renewal. Identify the cancellation method and any notice period before approving the service. For a business, record the subscription owner so that future charges are reviewed by someone who knows what was purchased. Otherwise, a low-attention expense can remain in the accounts long after its original purpose has disappeared.

For bundles, allocate value to the actual components. A package may include a cheap directory entry, an automated report, and a vaguely described monitoring service. The total price should not be justified by the dramatic language used to describe the bundle. Ask what each component does, whether you already receive it elsewhere, and whether a more direct service would better meet the need.

Do not accept a refund promise as a substitute for clarity. A guarantee can be difficult to use if the seller is unresponsive, the conditions are unclear, or the entity is difficult to identify. Establish the contracting party and terms before paying. The possibility of a later dispute is not a reason to skip the decision that would prevent the dispute.

Worked example: the launch activation notice

A hypothetical startup buys a domain and prepares to launch its website. Soon afterward, it receives a notice saying that an annual search-registration payment is required to activate the address internationally. The notice includes the domain, a barcode, and a deadline. The founder assumes it may be a final step related to the acquisition and asks the finance team to pay.

The finance team checks the closing record. The registrar and hosting services are already active, and no such payment is listed. The startup’s technical adviser confirms that the notice is an unsolicited offer for a directory service rather than an activation requirement. The founder declines it and records the legitimate providers for future invoice checks. The company does not need to prove that the directory itself is nonexistent to reject a falsely presented obligation.

In a legitimate alternative, the startup intentionally buys a listing in a relevant industry directory after evaluating its audience and terms. The invoice then corresponds to an authorized marketing purchase, not a supposed requirement imposed by the domain system. The same service category can be acceptable when sold honestly and unsuitable when disguised as something mandatory.

Reply without creating a new obligation

When a response is appropriate, keep it narrow. State that you have no record of ordering the service and request the alleged authorization or cancel the unsolicited offer as applicable. Avoid language that accidentally acknowledges a debt you have not verified. For a disputed charge, obtain advice suited to the jurisdiction and facts rather than relying on a universal template as a legal defense.

Preserve the notice and any terms shown at the time of purchase. If deception or unauthorized charging is suspected, contact the relevant payment provider and consumer-protection or enforcement channel as appropriate. Do not continue paying merely because the sender threatens escalation in generic language. At the same time, do not ignore a genuine legal document; authenticate it and obtain qualified advice.

A broker is most useful here when the solicitation is tied to a domain acquisition or sale and appears to be an extra closing requirement. The broker can clarify what the transaction actually requires and direct the client to the responsible provider. Beyond that, sound purchasing controls do the everyday work: know what you ordered, know who supplies it, and never let the presence of your domain name turn an unfamiliar advertisement into an invoice you automatically owe.

Back to the contents

Chapter 22: The Domain Appraisal Scam

The domain appraisal scam turns a seller’s hope of a valuable sale into a smaller, immediate payment. A supposed buyer offers an attractive price but says the seller must first purchase an appraisal from a particular service. The fee appears minor beside the promised proceeds. Once the seller pays, the buyer disappears, invents another requirement, or never completes a genuine purchase. The domain was the bait; the appraisal payment was the objective.

DigiCert’s domain-scam guidance describes this buyer-led, specified-appraisal pattern. ^[6] The warning should not be distorted into a claim that all paid appraisals are fraudulent. Independent valuation work can serve a legitimate purpose. The crucial questions are who needs the appraisal, who selected the provider, whether the provider is genuine, and why the seller must pay an unverified third party before the buyer makes a credible commitment.

Understand the economic asymmetry

The seller is being asked to exchange a certain payment for an uncertain future sale. The promised purchase price can be increased almost without cost to the scammer because the scammer does not intend to pay it. A very generous offer therefore does not make the appraisal requirement safer. It may simply make the fee feel too small to question.

Imagine a hypothetical offer of $28,000 with a required $195 appraisal. The seller may think the fee is less than one percent of the proceeds and therefore a reasonable risk. But that comparison assumes the proceeds are real. The relevant comparison is between a verified sale opportunity and an unverified story. Without a genuine buyer and transaction, the percentage calculation provides no protection.

A reimbursement promise does not change the structure unless it is part of a credible, enforceable arrangement with an authenticated counterparty. “I will add the fee to the purchase price” costs a fake buyer nothing to say. The seller should not treat a future reimbursement as existing money or allow it to waive provider verification.

Examine why that exact appraiser is mandatory

A legitimate buyer may seek information to support a purchase decision. They may have internal approval requirements or want an independent opinion. Those circumstances deserve discussion, not automatic accusation. Ask what question the appraisal is intended to answer and whether the buyer can commission it directly from a reputable service under their own arrangements.

A warning pattern emerges when the buyer rejects every alternative and insists on one obscure website, often reached through a supplied link. The seller’s existing appraisal is dismissed. A recognized provider is declared unacceptable without a clear reason. The requested fee becomes the only route to the promised purchase. This rigidity can reveal that the payment destination, not valuation quality, is the real point of the conversation.

Do not assume that a detailed report makes the arrangement legitimate. A site can produce a long document containing automated scores, generic comparisons, and a flattering estimate while still being part of a deceptive scheme. The report’s existence proves that something was delivered; it does not prove that the buyer was real, the valuation was meaningful, or the fee was necessary for a genuine sale.

Keep valuation separate from buyer qualification

An appraisal does not establish that a buyer has funds, authority, or a real intention to purchase. A high estimate cannot authenticate an email address. It cannot verify a company representative or replace an agreed payment process. If the buyer is unverified before the report, the buyer remains unverified afterward.

Likewise, a valuation estimate is not a guaranteed sale price. Domains can have different strategic value to different purchasers, and the seller’s time horizon matters. A professional valuation discussion should explain assumptions, relevant comparisons, limitations, and the distinction between an asking price and a completed transaction. A single number displayed with confidence is not the same as a binding offer from a qualified buyer.

A broker can help the seller assess whether the proposed price and behavior fit a plausible transaction. That does not mean a broker should reject an unusually high offer merely because it is unusual. It means the broker should qualify the opportunity through identity, authority, funding, and process checks rather than allowing an appealing number to dominate every other consideration.

Use a response that preserves legitimate opportunities

A practical reply can state that you do not purchase buyer-selected third-party reports as a condition of an unverified offer, but are willing to proceed through an authenticated broker or agreed transaction provider. The buyer may commission any independent advice they need at their own expense, subject to reasonable information access and confidentiality. This keeps the door open to a real purchaser without funding the suspicious prerequisite.

Do not spend hours arguing about whether the appraisal site is fraudulent. A scammer may provide testimonials, supposed professional endorsements, or another person who confirms the requirement. Your refusal can rest on the transaction structure. You are not obliged to finance a stranger’s chosen service simply because they promise to buy your asset afterward.

Avoid supplying additional personal or account information to demonstrate seriousness. A fake buyer may use the appraisal discussion to collect identity documents, registrar details, or other portfolio information. Share only what is appropriate to the stage of a genuine transaction. The seller’s wish to appear cooperative should not become an invitation to widen the exposure.

Worked example: the escalating report requirement

A hypothetical domain investor receives an offer far above the name’s asking price. The buyer claims to represent a technology fund and requires a certified valuation from a specified site. The investor pays the fee and receives a report. The buyer then says the report must be translated, insured, and registered with another service before funds can be released.

At this point, the investor should stop rather than trying to rescue the first payment with a second. They independently verify the supposed fund and discover that it has no record of the representative or transaction. The original report does not create a legitimate sale, and the new fees do not solve the missing buyer. The investor preserves the correspondence and contacts the relevant payment provider about the suspected fraud.

The better outcome occurs earlier: the investor declines the mandatory report, offers a verified transaction route, and asks the buyer to arrange its own valuation. A genuine buyer can explain its process and establish its identity. A fake buyer often loses interest when the seller refuses the only action that would produce immediate revenue for the scheme.

Respond constructively after paying

Do not let embarrassment delay containment. Save the invoice, report, correspondence, website details, and payment record. Contact the payment provider promptly to explain the suspected deception and ask what options apply. If credentials or identity information were also supplied, address those exposures separately. A charge dispute does not automatically secure an account or prevent misuse of disclosed documents.

Be cautious about follow-on messages offering to recover the appraisal fee or complete the original sale for another payment. The same contact information can support a second approach under a new identity. A supposed investigator who knows the amount you lost may simply have obtained that information from the original scheme. Verify any recovery assistance independently, as discussed in Chapter 70.

The strongest long-term rule is not “never buy an appraisal.” It is “never confuse a paid report with a verified purchaser.” Commission professional advice when it serves your own defined purpose, through a provider you have evaluated. For a meaningful sale, a qualified broker can help assess value and qualify buyers within one coherent process. That is a more useful investment than paying a stranger’s chosen website to unlock money that has never been shown to exist.

Back to the contents

Chapter 23: Verification Fees, Certificates, and Advance-Fee Variations

The appraisal scam is one member of a larger family: pay something now to unlock a promised domain purchase or sale later. The required payment may be called verification, insurance, compliance, account activation, currency conversion, release authorization, anti-fraud certification, or a refundable security deposit. The label changes, but the underlying question remains the same: what independently verified obligation justifies sending money before the promised transaction becomes real?

Some legitimate transactions do involve upfront expenses. Lawyers may require retainers, brokers may charge agreed engagement fees, and providers may require verified payment of their published charges. The presence of a fee alone is not proof of fraud. The danger lies in an unverified counterparty inventing a prerequisite, directing payment to a controlled destination, and using an attractive future outcome to discourage scrutiny of the immediate expense.

Identify who benefits from the prerequisite

Map the money flow. Who receives the fee? Are they the provider actually responsible for the service? Who selected them? What contract governs the payment? What happens if the sale does not close? A vague answer such as “the international department requires it” is not enough. Every real payment should have an identifiable recipient, purpose, and authorization.

Ask whether the supposed buyer or seller has made any credible commitment of their own. A large promised price is not a commitment if no authenticated transaction exists. A fabricated funding screenshot is not a commitment either. If your payment is the first irreversible step while the other party contributes only assurances, the arrangement deserves particular caution.

Do not let a small fee escape review merely because the potential transaction is large. The attacker may intentionally keep the first demand modest. Once you pay, a second requirement can appear, accompanied by the argument that stopping now would waste what you have already spent. Evaluate each new payment on its own merits rather than treating previous expenditure as evidence that the process must continue.

Verify the rule with the responsible institution

If the demand cites a registrar, ask that registrar through a genuine support channel. If it cites an escrow provider, inspect the real transaction and ask the provider. If it cites a tax, court, or regulatory obligation, obtain qualified advice and verify the relevant authority. Do not use the sender’s chosen contact as the only source of confirmation.

A legitimate requirement should fit the actual transaction. A company-verification process concerns the identity and documents required by the relevant provider. A domain transfer process concerns the applicable registrar and registry rules. A legal clearance question concerns the rights and circumstances being reviewed. Combining those subjects into one impressive-sounding certificate does not make the certificate necessary.

Look for a documented fee schedule or engagement term where appropriate. Charges can change and may depend on the deal, so do not rely on a fixed amount quoted in an old article. The important point is that the fee is confirmed through the provider’s authentic process and agreed by the responsible party. A stranger’s invoice should not become official merely because it resembles a plausible service charge.

Treat refundable deposits as real exposure

A payment described as refundable is still money leaving your control. The practical value of the refund promise depends on the recipient’s identity, the contract, the payment method, and the ability to enforce the obligation. A scammer can call any payment refundable without intending to return it. Do not classify it as risk-free because the word appears in the email.

For a genuine deposit, establish where it will be held, under what conditions it may be released, and what happens if either party withdraws. Those terms should be consistent with the purchase agreement and the selected provider’s actual service. A deposit sent directly to an unverified counterparty is not equivalent to funds held under a verified neutral arrangement.

Be wary of deposits requested solely to prove that you are serious. There may be legitimate commercial reasons for a deposit in a particular deal, but the structure should be negotiated and documented. A demand for payment to a personal account before the domain or representative has been verified reverses the sensible order of the process.

Distinguish professional fees from manufactured obstacles

A legitimate professional engagement describes the work to be performed, the client, the fee basis, and the provider’s responsibilities. You can evaluate whether the service is worth buying even if the domain transaction ultimately fails. An appraisal commissioned for your own planning, a lawyer’s contract review, or a broker’s agreed acquisition work can have a defined independent purpose.

A manufactured obstacle exists primarily because the supposed counterparty says the deal cannot proceed without it. The provider may be obscure, the requirement may keep changing, and no authoritative institution confirms it. The seller of the prerequisite and the promised purchaser may be connected in ways they do not disclose. Your investigation should focus on that structure rather than on whether the invoice contains the word professional.

A qualified broker can help identify reasonable transaction costs and challenge invented ones. The broker’s own charges should receive the same clarity: who pays, when payment is due, what services are included, and whether any referral or third-party arrangement exists. Trustworthy brokerage makes costs easier to understand; it does not ask the client to stop asking questions about them.

Worked example: the insured-payment release

A hypothetical buyer agrees to purchase a domain from an apparent overseas owner. The seller says the agreed payment service has received the purchase funds but requires a separate insurance payment before releasing the domain. A supposed service representative confirms this in a new email and supplies a cryptocurrency address. The buyer cannot see the requirement in the genuine account.

The buyer contacts the real provider through the established route. The provider confirms that the message is not part of the transaction and that no such payment is required. The buyer stops, preserves the messages, and checks whether any credentials were exposed. The presence of two apparently separate correspondents did not provide independent confirmation because neither had been authenticated.

In a legitimate alternative, the provider identifies a real, previously disclosed service charge inside the authenticated transaction. The parties confirm who agreed to pay it and use the provider’s authorized payment process. The distinction is not whether a fee exists. It is whether the fee belongs to a real service under the actual agreement and is payable through a verified channel.

Stop the escalation without negotiating with the fiction

Once the central requirement cannot be verified, do not keep asking how to make the fee smaller or faster. That accepts the premise that payment is necessary. State that you will proceed only through the agreed authenticated process and will not pay unverified prerequisites. A genuine counterparty can work within a legitimate structure or explain a verifiable alternative.

Preserve the sequence of demands. Escalating fees, changing recipients, and repeated promises of final release can be important evidence. If money has already been sent, contact the relevant provider promptly and report the facts accurately. Avoid telling yourself that one last payment is the only way to recover the earlier ones. The next demand may simply extend the same loss.

Advance-fee resistance is a discipline of sequencing. Verify the people, define the service, authenticate the provider, and understand the obligation before paying. A valuable domain opportunity does not require abandoning that order. The more attractive the promised outcome, the more important it is to remember that a future sale is not money in hand and an official-sounding prerequisite is not a rule until the responsible authority confirms it.

Back to the contents

Chapter 24: Fake Buyers, Overpayments, and Refund Traps

A fake buyer does not always try to steal the domain directly. Sometimes the objective is to make the seller send money, refund an apparent overpayment, or pay an invented intermediary. The proposed purchase provides the story that explains why funds are moving. The seller may believe they are correcting an innocent accounting mistake when they are actually making the only genuine payment in the transaction.

The FTC warns that fake-check schemes can involve an overpayment followed by a request to return part of the money. It also explains that funds appearing in an account do not necessarily establish that the deposited check is genuine; a later reversal can leave the recipient responsible. ^[37] For domain sellers, the practical lesson is to avoid acting as a refund or forwarding service for an unverified buyer.

Recognize the overpayment structure

The buyer claims to have sent more than the agreed price and asks you to return the difference. The explanation may involve an assistant’s error, combined payment for several purchases, an urgent supplier bill, or a commission that must be forwarded to another person. The story turns an unexpected credit into a duty to make a separate outbound payment.

Do not treat the amount displayed in an account or on a receipt as sufficient proof that the transaction is settled on the terms you need. Payment instruments have different risks, and the applicable provider should explain the actual status. There is no universal number of waiting days that makes every unfamiliar payment safe. The right response is to contact your financial institution or transaction provider and follow its authenticated guidance.

A genuine mistake should be resolved through the original payment channel under the provider’s procedures, not by sending new money to an unrelated destination supplied by the buyer. Avoid making a separate wire, cryptocurrency transfer, gift-card payment, or other irreversible reimbursement while the original payment remains uncertain. You should not become the mechanism that converts a questionable incoming payment into a clean outgoing one.

Separate payment claims from delivery authority

A buyer may send a screenshot stating that the full purchase price has been paid and argue that delaying transfer would be dishonest. The seller should check the genuine transaction account and the agreed funding condition. A payment claim from the buyer is not the provider’s confirmation that the seller may deliver under the contract.

Do not allow moral pressure to reverse the burden of verification. An honest seller can be responsive and professional while refusing to release a domain on unverified evidence. Explain that delivery follows the agreed process, not a screenshot or a request to trust the buyer personally. A legitimate purchaser benefits from a clear record of payment and delivery just as the seller does.

If funds arrive outside the agreed route, pause rather than improvising. Determine who sent them, why the route changed, and whether the original agreement and provider can accommodate the payment. Unexpected money can create compliance, accounting, and fraud concerns. It should not automatically trigger a transfer merely because the seller sees a balance increase.

Beware of third-party recipients and intermediaries

A fake buyer may ask you to pay a broker, translator, shipping agent, tax office, or closing assistant from the purchase proceeds. A domain transaction generally should not require the seller to forward unexplained portions of an unverified payment to strangers. If a legitimate third-party fee exists, identify it in the agreement and use the appropriate provider’s approved process.

The same caution applies when the buyer says another person will pay on their behalf. Third-party funding may be legitimate in some structures, but it needs disclosure and acceptance by the relevant provider. The payer, contracting buyer, and recipient of the domain should not become disconnected without explanation. A broker can help coordinate the questions, while the provider determines whether the proposed funding arrangement is acceptable.

Do not assume that a professional title makes the recipient safe. A supposed lawyer or accountant may be impersonated. Verify the person and their role independently. If the buyer resists any attempt to confirm who is receiving the money, the seller has a sufficient reason to stop without first proving the entire scheme.

Qualify buyers without demanding unnecessary exposure

Buyer qualification should establish a credible person or entity, authority to purchase, a realistic process, and the ability to fund through the agreed service. It should not become an excuse to collect passwords or unrestricted banking information. An experienced broker can help choose a proportionate method, especially for a valuable asset or a buyer using a corporate structure.

Look for behavior consistent with the proposed deal. A buyer who asks sensible questions, accepts an authenticated process, and provides appropriate information is easier to evaluate than one who offers an extraordinary price but focuses entirely on refunds and fees. Still, behavior is not proof. The final controls must work even when a dishonest buyer is polite, patient, and well informed.

Avoid treating every failed negotiation as a fake buyer. Genuine purchasers can change priorities, fail to obtain approval, or decide the price is too high. Those outcomes are frustrating but not necessarily fraudulent. The relevant warning is an attempt to induce a harmful action through a false payment or identity claim, not merely the absence of a completed sale.

Worked example: the accidental excess

A hypothetical seller agrees to a $7,500 domain sale. The buyer sends what appears to be a $10,000 payment and says an assistant included a separate vendor expense by mistake. The buyer asks the seller to return $2,500 to a different account immediately, promising that the domain transfer can happen afterward. The seller sees a provisional credit and feels responsible for correcting the error.

Instead of sending the refund, the seller contacts the financial institution through a known route and explains the entire situation. The institution advises on the payment’s status and the appropriate handling of any return. The seller also checks the agreed transaction process and does not transfer the domain. The buyer’s urgency does not create authority to direct a separate payment.

If the incoming payment later proves fraudulent, the seller has avoided turning the apparent excess into an actual loss. If it is a genuine error, the provider can guide a proper correction through the appropriate channel. The same control protects both possibilities. It is not an accusation to require a payment mistake to be resolved by the institution responsible for the payment.

Handle a completed mistake as an incident

If you have already returned money or transferred the domain, act promptly. Contact the relevant financial institution, payment provider, registrar, and transaction service as applicable. Explain both the incoming and outgoing transactions, including amounts, times, beneficiaries, and the claimed reason for the refund. Preserve messages and receipts. Do not wait for the buyer to admit that anything is wrong.

Be alert to a second demand. The buyer may claim the refund failed, request another route, or say an additional fee will restore the original payment. Verify each claim with the real provider rather than continuing the exchange. Once a payment irregularity is suspected, the transaction should move into a controlled incident process rather than remain a casual negotiation.

A seller’s safest position is straightforward: accept the agreed consideration through a verified process, deliver under the agreed conditions, and do not forward unexplained money on a stranger’s instructions. A qualified broker can screen inquiries and coordinate closing, but neither the broker nor the seller should treat an apparent overpayment as a windfall or a personal obligation to send money elsewhere. A genuine sale pays you for the domain; it does not recruit you as the buyer’s emergency payments department.

Back to the contents

Chapter 25: Fake Brokers and Unauthorized Representatives

A broker’s name can make a domain transaction feel safer, which is precisely why impersonating a broker can be effective. A stranger may copy an established firm’s branding, claim to represent a wealthy buyer, or say they have an exclusive mandate from a domain owner. Another person may be real but exaggerate their authority. Before relying on brokerage, verify both the professional’s identity and their role in this particular transaction.

The distinction matters because a genuine industry reputation belongs to the actual professional, not to anyone who uses the same name in an email signature. A known broker can also be impersonated through a lookalike address or compromised communication channel. Verification should therefore be transaction-specific and independent. Recognizing a logo is not the same as establishing that the firm has accepted the engagement described to you.

Confirm the person through the real firm

Locate the brokerage’s official contact route independently, rather than relying exclusively on links or numbers in the initial message. Ask whether the named individual works with the firm and whether the firm is handling the domain or client relationship in question. Confidentiality may limit what the firm can disclose, but it should be possible to establish an appropriate authenticated channel without revealing the client’s entire strategy.

Compare the exact email domain and communication details with those confirmed through the firm. Record the verified route for later use. If a supposed broker moves the conversation to a new personal address or messaging account, treat that as a change requiring confirmation. A real professional may use several channels, but the authority of a new one should not be assumed merely because it arrives with familiar branding.

Do not use a search advertisement or a social profile as the sole source of truth. They may help locate a business, but the actual identity check should reach the genuine organization through a credible route. If you are uncertain, slow the transaction down before sharing confidential information, paying a fee, or authorizing any change to the domain.

Ask whom the broker represents

A broker may represent the buyer, the seller, act under a disclosed arrangement involving both sides, or provide only a limited introduction or transaction service. Those roles affect duties, confidentiality, negotiation expectations, and compensation. Ask for a clear explanation instead of assuming that every intermediary is a neutral adviser acting exclusively for you.

A seller’s broker should have appropriate authority to market or negotiate the asset within the engagement. A buyer’s broker may be seeking a name the owner has not yet agreed to sell. That is legitimate when described accurately. The problem arises when an intermediary claims an exclusive listing, a firm offer, or ownership that has not been established.

For a valuable deal, obtain a written engagement or other suitable documentation of the broker’s role. The document should identify the client, scope, fee arrangement, and limits of authority. It should also explain who may approve price changes, binding terms, and closing instructions. A vague statement that the broker will “handle everything” creates room for both misunderstanding and abuse.

Treat access and money requests separately

A broker may need information about the domain and the client’s objectives. That does not automatically justify access to the entire registrar account or permission to receive sale proceeds personally. Ask why each access request is necessary and whether a narrower method would serve the purpose. Technical delivery should follow the verified transaction arrangement, not an improvised request from a purported representative.

Likewise, a fee request should match the engagement. Legitimate brokers may use different compensation models, including agreed upfront or success-based charges. The test is not whether the fee is paid before or after closing in every case. It is whether the real firm has agreed to the service, the terms are clear, and the payment route is authenticated.

Be cautious when a supposed broker’s main activity is directing you to buy an appraisal, certificate, or release service from a particular third party. Ask whether the broker has a financial relationship with that provider and why the expense is necessary. A genuine advisory relationship should make those interests and costs understandable rather than hiding them behind a promised buyer.

Evaluate evidence of experience without borrowing certainty

A broker may cite completed transactions, references, interviews, or industry awards. Verify material claims through appropriate sources and understand what they establish. A public award can demonstrate recognition under specified criteria; it does not guarantee that every person claiming the firm’s identity is genuine or that every proposed deal is safe.

Confidential transactions can limit public detail. That is not automatically suspicious. A professional may be able to offer references with permission, explain relevant experience without naming a client, or describe the process used for comparable situations. The aim is a credible basis for selecting the broker, not a demand that they breach prior confidentiality obligations to impress a new prospect.

Do not equate a long social-media history with current authority. Accounts can change hands or be compromised, and an individual may leave a firm. Confirm the present relationship through the organization before relying on it. The more important the instruction, the less appropriate it is to infer authority from an old post or a familiar profile photograph.

Worked example: the exclusive listing that was not

A hypothetical buyer receives an offer from someone claiming to be the exclusive broker for a desirable domain. The intermediary uses the name of an established brokerage and supplies a polished presentation. They ask for a refundable reservation payment to hold the name while the purchase agreement is prepared. The buyer has not yet communicated with the genuine firm.

The buyer contacts the brokerage through an independently located official route. The firm confirms that the individual is not authorized to represent it and that it has no such listing. The buyer does not pay and provides the relevant messages to the impersonated firm. The apparent exclusivity and reservation deadline were claims without a verified principal behind them.

In a legitimate variation, the firm confirms the representative and explains that it is acting for a buyer seeking to acquire the name, not for the owner. The buyer then recognizes that the proposed service is acquisition assistance rather than purchase of an existing exclusive listing. That distinction may still lead to a useful engagement, but only after the role and fee structure are accurately understood.

Protect legitimate brokers from impersonation too

When you verify a broker, keep the confirmed details and use them consistently. Alert the real firm if you receive a message that appears to misuse its identity. Provide factual information rather than publicly accusing the firm of conduct that may belong to an impersonator. A prompt, precise report can help the firm warn other affected participants and clarify the legitimate transaction channel.

During closing, do not assume that verified identity at the beginning authenticates every later instruction. A real broker’s email account can become a target, and a fraudulent message may arrive inside an established thread. Material payment or transfer changes should still follow the communication protocol in Chapter 17. Verification is an ongoing control, not a one-time badge attached to a name.

The answer to fake brokers is not to avoid professional brokerage. It is to distinguish real, accountable brokerage from its imitation. A qualified domain broker can be one of the most valuable participants in a significant purchase or sale, especially when they qualify counterparties and coordinate execution. That value begins with confirming that you are dealing with the actual professional, under a clear engagement, with authority that matches the work they propose to perform.

Back to the contents

Chapter 26: Fake Escrow Websites and Cloned Marketplaces

The word escrow can create a false sense of safety when the service itself has not been authenticated. A fraudulent buyer or seller may agree enthusiastically to use escrow, then direct the other party to a convincing imitation site. The page displays a transaction number, account balance, support chat, and instructions. Nothing about that presentation establishes that a real independent provider is holding funds or controlling delivery.

A cloned marketplace creates a similar problem. The victim may believe they are acting inside a familiar platform while interacting with a lookalike domain or fabricated interface. The protective value of a genuine provider does not extend automatically to a website that copies its name. Before relying on escrow or a marketplace, establish the provider’s real identity, the applicable service, and the authenticity of your particular transaction.

Begin outside the counterparty’s link

Find the provider through a route independent of the proposed deal. Use an established bookmark, a known official address, or another reliable method to reach the actual organization. Do not allow the person asking for your money to define both the escrow service and the only route by which you can verify it. A supplied link may be convenient, but convenience is not authentication.

Inspect the exact hostname before entering credentials or payment information. A familiar brand name can appear in a subdomain, path, or longer unrelated address. A secure connection does not establish that the site belongs to the brand you intended to use. When uncertain, stop and contact the provider through its independently verified support channel rather than testing the site with your real login.

Create or access your account through the genuine service and locate the transaction there. Confirm the exact domain, parties, price, currency, fees, and delivery arrangement. A transaction visible only through a special link that ordinary support cannot verify is not a sound basis for sending money or releasing an asset.

Verify the legal entity and regulatory claims

A provider may publish licensing or registration information relevant to its services and jurisdictions. Escrow.com, for example, publishes a licenses-and-complaints page identifying its operating entities and regulatory information. ^[38] Use such information as a starting point for appropriate independent checks, not as a decorative seal that can be copied onto any website.

Where a license is claimed, confirm the actual entity, scope, and current status through the relevant regulator or official register when available. Requirements vary, so do not assume that every service using the word escrow is governed by one universal licensing system. A real license for one entity or activity does not automatically cover a different site, affiliated company, or transaction structure.

Check whether the service supports the asset, parties, countries, currency, and payment method involved. A genuine provider may decline a particular transaction or require additional verification. Those limits are not defects to work around secretly. A counterparty who says to disguise the nature of the transaction to gain access to the service is proposing a new risk, not a clever closing shortcut.

Read what the service actually does

Money holding, domain transfer assistance, neutral custody, inspection administration, and long-term installment holding are distinct functions. A provider may offer some through one service and others through another. Do not infer that all are included merely because the brand is familiar. Confirm the selected product and the responsibilities each participant retains.

Ask how the provider confirms funding, how delivery is recorded, what starts the inspection period, and when funds may be released. Review cancellation and dispute procedures before entering an irreversible stage. The contract between buyer and seller should fit the provider’s actual workflow rather than requiring the provider to perform checks or hold conditions it has not agreed to administer.

A genuine escrow arrangement is not automatically legal-title insurance, a valuation opinion, or a guarantee against every type of fraud. It can substantially improve the exchange process within its scope, but it does not replace verification of the seller’s authority or the buyer’s intended use. Understanding those boundaries prevents a real service from being relied on for protections it does not provide.

Authenticate every consequential instruction

Payment details should come through the genuine provider’s process and be independently confirmed when a material change occurs. Do not wire money to an account supplied only in a forwarded email, even if the message appears to come from the provider. Compare the beneficiary and reference with the authenticated transaction instructions and resolve discrepancies before sending funds.

For sellers, the equivalent risk is a fake funded-status notice followed by a request to transfer. Check the genuine account and, where needed, contact the provider. Do not deliver to a buyer or supposed concierge account solely because someone supplies a screenshot saying the money is secure. The exact delivery destination and timing must match the verified service.

If a support representative asks you to leave the platform, use cryptocurrency unexpectedly, or pay a separate release charge to an unrelated account, pause. The request may be fraudulent or may reflect a misunderstanding that requires clarification. Either way, it should be resolved through the real provider, not accepted because the representative appears within a convincing chat window.

Worked example: the private escrow portal

A hypothetical seller agrees to use escrow with an unfamiliar buyer. The buyer sends a link to a site whose name resembles a recognized provider and says it is a private portal for premium-domain transactions. The site shows the agreed price as funded and supplies a destination account for the domain. The seller is instructed not to use ordinary customer support because the transaction is confidential.

The seller independently reaches the genuine provider and asks whether the portal and transaction are valid. The provider cannot verify either. The seller does not transfer the domain and preserves the site details and messages. Confidentiality did not justify excluding the very institution supposedly responsible for holding the money.

In a legitimate alternative, the genuine provider confirms a specialized service and supplies instructions through the authenticated account. The seller then checks that the destination and conditions match the agreed workflow. The lesson is not that specialized portals cannot exist. It is that a specialized arrangement must be verified by the real organization rather than authenticated solely by the counterparty who introduced it.

Respond quickly to exposure

If you entered credentials into a suspected clone, secure the genuine account and any other account using the same password through trusted routes. Review active access with the relevant provider. If you sent money, contact the financial institution immediately and explain the suspected fraud. If you transferred a domain, contact the registrar and genuine transaction participants promptly. Each exposure needs its own containment response.

Preserve the exact web address, transaction references, payment instructions, emails, and timing. Report the impersonation to the real provider and the appropriate authorities or abuse channels. Do not continue interacting with the clone in an attempt to obtain a refund without considering the risk of further manipulation. A fake support team may respond to your concern by inventing another fee.

A qualified broker can help select an appropriate genuine provider and coordinate the parties’ use of it. The client should still know how to access the actual transaction independently. The safest escrow arrangement is not the one with the most reassuring branding. It is the one whose identity, legal entity, service scope, instructions, and transaction status have all been verified outside the counterparty’s control.

Back to the contents

Chapter 27: Selling Domains That Are Not Owned: Bait, Substitution, and Speculation

A person can discuss selling a domain without owning it, but the nature of that discussion must be clear. A buyer’s broker may offer to approach the owner. An intermediary may have a disclosed option or contingent arrangement. A marketplace listing may be outdated. Fraud arises when someone falsely claims ownership or authority, takes payment on that basis, or substitutes a different asset after the buyer has committed.

The key question is what the seller can legitimately promise now. Are they transferring an asset they own, acting for an authorized owner, or offering a service to try to acquire it? Those are different transactions with different risks. A buyer should not pay the price of a completed acquisition while unknowingly receiving only an unverified intermediary’s hope of obtaining the name later.

Clarify the seller’s present position

Ask directly whether the person owns the domain, represents the owner, holds a relevant contractual right, or is proposing acquisition assistance. A credible answer should match the agreement and payment structure. “We can get it” is not equivalent to “we are authorized to sell it.” The distinction becomes especially important when a deposit or nonrefundable fee is requested before the owner has been contacted.

If the person claims representation, verify the mandate through an appropriate independent process. If they claim a contractual right, have qualified counsel review the relevant evidence where the stakes justify it. The buyer does not need every confidential detail of the intermediary’s business, but does need to understand the right on which delivery depends and what happens if that right cannot be exercised.

A legitimate acquisition broker can be valuable precisely because the target is not yet for sale. The broker’s work is to locate the owner, assess willingness, negotiate, and coordinate a potential purchase. The engagement should describe that service honestly, including uncertainty. It should not disguise an acquisition attempt as a guaranteed sale from inventory.

Do not treat a listing as proof of authority

A name appearing on a landing page, marketplace, spreadsheet, or broker presentation does not by itself establish that the person offering it currently has the right to sell. Listings can be stale, duplicated, mistaken, or unauthorized. Verify the actual seller and current status before relying on the advertised price or availability.

For a marketplace transaction, use the platform’s genuine process and ask how ownership or delivery is checked under the specific listing type. Do not assume that every listing mechanism provides identical verification. If the domain cannot be delivered, understand the platform’s actual cancellation and refund terms rather than relying on a general impression of the brand.

A buyer may discover different prices for the same domain in different places. That discrepancy does not automatically prove fraud; it may reflect outdated listings or different commercial arrangements. But it should be resolved before purchase. Confirm which seller and price are authoritative and whether another binding commitment already exists.

Recognize bait-and-switch behavior

A seller may advertise a desirable name at an unusually attractive price, then say it has just sold and offer a weaker alternative. Sometimes inventory genuinely changes. The concern is a pattern in which the original asset was never available or was used to collect payments, personal information, or attention under false pretenses. Evaluate the alternative as a new purchase, not as the automatic continuation of the original bargain.

Substitution can also occur in the contract or delivery schedule. A different extension, plural form, hyphenated version, or internationalized lookalike may be presented as equivalent. It is not the same asset. Return to the exact-domain verification in Chapter 9 and require the written agreement, provider transaction, and receiving account to identify the intended name consistently.

Do not accept a bundle of minor domains as compensation for failure to deliver the principal asset without a deliberate new agreement. The original price may have been justified almost entirely by that one name. A larger count of weaker assets does not necessarily preserve the value or purpose of the transaction. Reassess the economics and legal terms rather than allowing momentum to make the decision.

Structure contingent acquisition honestly

A contingent arrangement can be legitimate when the buyer understands that delivery depends on acquiring the domain from a third party. The agreement should identify the service, conditions, deadlines, fees, and treatment of funds if the acquisition fails. Counsel and the selected provider should confirm whether the proposed structure is workable within their responsibilities.

Do not assume that a standard escrow transaction can administer every contingent or multi-party arrangement. Explain the actual sequence to the provider and obtain confirmation that it supports the process. Concealing the intermediary’s lack of current ownership can create a mismatch between the contract, verification, and delivery expectations. Transparency with the responsible professionals is more valuable than forcing the deal into an unsuitable template.

For the intermediary, accuracy protects reputation. State what you control, what remains subject to another party’s consent, and which promises you are authorized to make. Do not collect the full sale price under a claim of ownership that is not true. A professional can market sourcing expertise without pretending that every target domain is already an owned asset.

Worked example: the bargain that required a deposit

A hypothetical founder receives an offer for a domain central to a planned rebrand. The quoted price is far below the price shown on the domain’s established sales page. The intermediary says they have a special relationship with the owner and requires a nonrefundable reservation payment. They will not identify whether they represent the owner or are merely trying to negotiate an acquisition.

The founder’s broker contacts the legitimate owner through an independently established route and confirms that no such sale or representation has been authorized. The founder declines the reservation payment. The intermediary’s confidence and low price did not create delivery authority. The buyer avoided paying for a promise whose essential premise could not be verified.

In a legitimate version, the intermediary clearly offers a buyer-representation service, discloses the fee terms, and makes no claim that the owner has agreed to sell. The founder can then evaluate whether to hire that service. The commercial opportunity is different, but not inherently improper. Honest description allows the buyer to price the uncertainty rather than discovering it after payment.

Keep failed delivery from becoming a second negotiation under pressure

If the promised domain cannot be delivered, follow the agreed cancellation or dispute process. Do not let the seller hold the buyer’s funds hostage to acceptance of another asset unless the buyer freely enters a valid new arrangement with appropriate advice. Preserve the original offer, agreement, asset schedule, and explanation of the failure.

Ask whether any partial transfer has occurred and what obligations remain. A portfolio may require a more complex unwind than a single-domain purchase. The provider’s actual procedures and the contract should guide the response. Avoid unilateral technical retaliation or attempts to seize unrelated assets; those actions can create additional legal and operational problems.

A qualified domain broker adds value by establishing what is genuinely available, who can authorize a sale, and which acquisition path is realistic. That work is especially important when the target is not openly for sale or the market contains conflicting listings. The safest buyer does not insist that every intermediary own every name they discuss. The safest buyer insists that the intermediary describe their position truthfully and that payment obligations match the rights and services actually being offered.

Back to the contents

Chapter 28: Stolen Domains and the Risks of Resale Chains

A buyer can pay a real seller, receive a domain into a real account, and still face a serious ownership problem. The seller may have acquired the name through an unauthorized transfer, or an earlier transaction in the chain may be disputed. Technical delivery does not automatically resolve the rights of prior parties. This is why a safe acquisition asks not only whether the domain can be transferred, but whether the seller has a credible right to transfer it.

ICANN recognizes unauthorized transfers and domain hijacking as problems that may involve compromised accounts or other illegal activity, while distinguishing its contractual role from criminal investigation. ^[4] For a purchaser, the practical consequence is to take provenance seriously and obtain qualified legal advice when a material concern appears. Do not assume that using a reputable payment service guarantees clean title or immunizes the buyer from every earlier defect.

Understand why a resale can obscure the problem

An unauthorized holder may try to sell quickly, perhaps at a discount, before the original registrant detects or resolves the incident. The name may pass through more than one account or intermediary. Each additional transaction can make the story harder to reconstruct and create more parties who believe they acted legitimately. A recent purchaser’s sincere belief is not a complete answer to an earlier owner’s claim.

Do not turn this possibility into a rule that recently acquired domains are unsafe. Investors legitimately buy and resell assets, sometimes quickly. The question is whether the timing, price, identity, and documentation form a coherent account. A short holding period accompanied by clear acquisition evidence is different from a rushed sale whose seller refuses to explain how they obtained the name.

Look at the whole pattern. Unexplained registrar changes, abrupt contact changes, inconsistent seller identities, pressure to use a different payment route, and a price justified only by urgency deserve investigation. No single indicator proves theft. Their value is to identify the questions that must be resolved before the buyer accepts an irreversible exposure.

Build a provenance file appropriate to the asset

For a valuable domain, ask the seller how and when it was acquired and whether any previous owner or other party has asserted a claim. Request relevant supporting evidence through a confidentiality-conscious process. Counsel may review acquisition documents or disclosures without requiring every private detail to circulate among all participants. The investigation should target the risk, not maximize the volume of collected paperwork.

Where appropriate, seek confirmation from a previous owner through an independently established route. Do not use only a contact supplied by the current seller. A previous owner’s response may help clarify the chain, but its identity and meaning still need assessment. A former employee may not speak for the company, and a person who once used the website may never have controlled the registration rights.

Preserve the evidence used for the decision. If a later dispute arises, the buyer should be able to show what was represented, what was checked, and when. This is not a promise that documentation will determine the legal outcome. It is a practical way to avoid losing the facts needed by providers, counsel, or investigators when the transaction’s history becomes contested.

Do not confuse security changes with proof of legitimacy

A domain appearing in your account, protected by your password and authentication settings, establishes current operational control under the provider’s system. It does not necessarily settle every legal claim. Likewise, a successful inter-registrar transfer does not certify that all earlier transfers were authorized. Security and title review solve different problems and should both receive attention.

A seller may argue that the registrar would have blocked the transaction if anything were wrong. That assumption overstates the registrar’s role. The provider may not know about a dispute or may not adjudicate competing ownership claims through an ordinary transfer workflow. Ask the provider what it actually verifies rather than treating successful processing as a legal opinion.

The same caution applies to escrow. A genuine provider can administer the agreed exchange and still leave ownership representations to the parties. Unless a specific protection is expressly provided and understood, do not infer that the service insures against a prior theft claim. A broker should explain this boundary clearly rather than presenting escrow as a universal cure for provenance concerns.

Pause when a credible claim appears

If a former owner contacts you during due diligence and alleges an unauthorized transfer, authenticate the contact and preserve the claim. Notify the appropriate transaction participants and obtain advice before moving further. Do not automatically accept the allegation, but do not dismiss it because the seller offers a discount for closing before the issue is examined.

Avoid helping the seller move the domain through additional accounts or jurisdictions to make the claim harder to pursue. A request framed as “protecting the deal” may actually increase your exposure. The appropriate response is a transparent, advised process that addresses the dispute, not a race to complete technical delivery before another party can act.

A buyer can decline to proceed without proving the seller committed a crime. Unresolved material ownership uncertainty is a sufficient commercial reason to stop. The seller may consider that unfair, but the buyer is not obliged to finance a disputed asset merely because the seller needs liquidity or insists that the claim is baseless.

Worked example: the second innocent purchaser

A hypothetical investor is offered a short domain by someone who says they bought it from another investor a week earlier. The price leaves room for a profitable resale. The current seller supplies a genuine receipt for their purchase but little information about the prior owner. Historical evidence shows a longstanding corporate use, followed by sudden changes and a rapid sequence of offers.

The prospective buyer’s broker asks for a clearer chain and contacts the former business through an independently found route. The business reports an active unauthorized-transfer investigation. The current seller may also be a victim, but that does not resolve the proposed buyer’s risk. The buyer suspends the purchase and directs the parties toward the relevant providers and legal advice rather than becoming the next link in the chain.

In a legitimate alternative, the corporation confirms an authorized disposal and the acquisition documents align with the current seller’s account. The short holding period then has a reasonable explanation. The buyer can continue under appropriate terms. The method does not reject resale activity; it refuses to let a recent receipt answer a different question about earlier authority.

Respond responsibly after buying a disputed name

If a credible claim emerges after closing, preserve the domain and transaction records and obtain qualified advice promptly. Do not delete correspondence, fabricate a history, or transfer the asset again to make the problem disappear. Inform the relevant provider through an authenticated channel and understand any restrictions or procedures that apply. Your response should protect evidence and avoid creating further harm.

Do not publicly label every prior participant a thief. Some may have been deceived, and the facts may be incomplete. Use precise language about the allegation and the evidence. Counsel can help determine what communications are appropriate, which parties should receive notice, and what contractual or legal remedies may be available.

A skilled broker can recognize provenance concerns before purchase and coordinate the right investigation, which is a significant reason to use one for a valuable acquisition. But the broker should not promise immunity from all title disputes. The defensible goal is a well-supported purchase from an authenticated, authorized seller, with clear disclosures and a documented process. A domain’s ability to move is only one part of whether it is safe to buy.

Back to the contents

Chapter 29: Typos, Homographs, Internationalized Names, and Asset Substitution

A domain transaction can be redirected by a difference too small to notice during a hurried glance. A missing letter, added hyphen, different extension, or visually similar character can change the asset or the destination of a payment instruction. These risks affect both what you are buying and where you conduct the transaction. The same careful reading that protects the domain schedule also protects access to registrars, brokers, and escrow providers.

Internationalized domain names are legitimate tools for representing languages and scripts beyond basic ASCII. ICANN explains their Unicode and encoded ASCII forms, while Unicode’s security standard describes mechanisms for detecting visually confusable identifiers. ^{[23] [39]} The lesson is not to distrust non-English names. It is to verify the exact representation deliberately, especially when a deal depends on a familiar-looking word.

Distinguish spelling errors from visual substitutions

An ordinary typo may involve an omitted character, a transposition, a plural ending, or a different extension. A visual substitution may use a character or sequence that resembles another in the displayed font. Both can matter commercially, but they need not have the same technical cause. Do not assume that every confusing name is an IDN or that every IDN is designed to confuse.

Request the domain as plain text and compare it with the canonical asset record. For an IDN, obtain the relevant encoded representation and have it checked by someone competent where necessary. Avoid relying on a logo, a screenshot, or a browser display that may render the name differently from the registrar’s underlying record. The contract must identify the asset unambiguously.

For language-specific purchases, involve someone who understands the intended language and audience. A name may be technically valid but linguistically awkward, misleading, or commercially unsuitable. That is a valuation and usability issue rather than necessarily a scam. A broker should distinguish those questions from the separate problem of whether the seller accurately described the asset.

Protect the transaction’s own addresses

A buyer may carefully inspect the domain being purchased while overlooking a lookalike escrow address. A seller may verify the asset schedule but send a transfer code to a near-match broker email. Apply exact-address checking to every consequential service and communication route, not only to the item for sale.

Do not infer the organization from a familiar word appearing somewhere in a URL. Identify the actual hostname and reach the service through an independently verified route. A link can display reassuring text while pointing elsewhere. When an email requests action, access the known provider directly instead of using the message’s link as both the instruction and the authentication mechanism.

Be careful with copied payment details too. The relevant issue is not only character appearance but whether the destination came from the genuine provider’s current instructions. A perfectly copied fraudulent account remains fraudulent. Exact comparison and independent authentication are complementary controls: one ensures you copied the instruction correctly; the other establishes that it is the instruction you should follow.

Compare lists systematically without over-normalizing

For a portfolio, use a consistent machine-readable asset schedule. Normalize ordinary ASCII capitalization for comparison, but do not strip meaningful characters or collapse distinct names merely because they look similar. Removing hyphens, ignoring extensions, or converting visually similar characters indiscriminately can turn a verification tool into a source of errors.

Flag duplicates and near-matches for review rather than automatically treating them as interchangeable. A portfolio may intentionally contain several variants, but each should be identified and priced appropriately. Count exact unique registrations, not rows that happen to look different in a spreadsheet. Keep the agreed version with the contract and compare delivery against that same version.

When a list includes unfamiliar scripts or complex extension structures, obtain suitable technical assistance. A general spreadsheet cleanup rule may not understand registry-specific registration units or IDN handling. The safest automation is explicit about what it changes and preserves the original values for review. Convenience should not erase the evidence needed to identify the asset.

Treat corrections as controlled amendments

A seller may say a different spelling in the contract is just a harmless typo. It may be, but correct the document and provider transaction before funding or delivery. A verbal assurance that everyone understands the intended name leaves unnecessary room for dispute. The cost of correcting a clear asset identifier before closing is usually small compared with the consequences of receiving the wrong asset.

The same rule applies when the buyer changes their mind about an extension or variant. That is a new commercial choice, not a clerical adjustment. Revisit price, intended use, legal review, renewal costs, and transfer support. Do not carry over an approval based on one name to another simply because the difference occupies only a few characters.

If the counterparty resists putting the correct name into the authoritative documents, stop. An honest seller should want the contract to match the asset they intend to deliver. Persistent reliance on images, abbreviations, or “you know what we mean” is not an adequate basis for a valuable purchase.

Worked example: the two nearly identical schedules

A hypothetical company agrees to buy a portfolio containing one principal brand domain and several defensive variants. The initial schedule is accurate. A later version changes one character in the principal name while preserving the row count and most of the formatting. The closing team could easily overlook the change if it checks only the total number of domains.

The buyer’s broker compares the exact strings in the approved and revised schedules and flags the difference. The seller explains that an assistant made a data-entry error. Whether the explanation is true or not, the team requires a corrected schedule and verifies the actual registration before proceeding. The buyer does not accept the near-match as equivalent or allow the error to survive into the provider’s transaction record.

In a more deceptive version, the seller insists the alternate character is merely a display convention and refuses to provide a matching encoded representation. The buyer declines the deal. The protective step is the same in both cases: resolve the exact asset identity before money moves, rather than attempting to interpret intention after delivery.

Build a final read-back into closing

Immediately before funding and delivery, have the responsible participants compare the canonical domain schedule with the agreement and provider account. For a single ambiguous name, a deliberate character-by-character review may be appropriate. For a large portfolio, combine exact automated comparison with manual review of exceptions. Do not rely on memory from an earlier negotiation.

After receipt, verify the exact names inside the receiving account and confirm that the intended registrant or account arrangement is in place. A website redirect or landing page may show the expected brand while the actual registration differs. Acceptance should be based on the delivered assets and agreed conditions, not merely on the visual appearance of a page.

A qualified broker can make these checks routine, particularly when a transaction spans multiple providers, languages, or portfolios. The client should still understand the principal name they are acquiring. Precision is not pedantry in a domain sale. A single character can separate the intended asset from a different one, and a familiar-looking service address can separate a genuine closing from an imitation built to capture the money.

Back to the contents

Chapter 30: Auction Manipulation, Shill Bidding, and Suspicious Competition

An auction can make price discovery feel objective because competing bids are visible. That appearance does not remove the need for judgment. Artificial bidding, false claims about rival buyers, or misleading post-auction messages can pressure a purchaser into paying more or using an unsafe route. At the same time, genuine competition can look frustrating or unexpected. A careful bidder distinguishes suspicious evidence from the ordinary disappointment of being outbid.

GoDaddy has publicly discussed shill-bidding risks and its efforts to address auction fraud. ^[40] That acknowledgment does not establish that a particular auction is manipulated, nor does any platform’s controls guarantee perfect prevention. Your own safeguards should include understanding the current auction terms, setting an independent maximum price, using the genuine platform, and reporting concrete anomalies through its appropriate channels.

Define your maximum before the bidding pressure begins

Decide what the domain is worth to your strategy before watching competitors’ activity. Include the acquisition price, applicable fees, renewal obligations, and any additional work needed to use or resell the name. A maximum based solely on the latest bid can drift upward without a corresponding increase in the asset’s usefulness or expected return.

For an end user, consider alternatives and the cost of changing the naming plan. For an investor, consider holding costs, uncertainty, and the difference between a plausible retail asking price and a completed sale. These are your assumptions, not facts proved by other bidders. An auction can reveal willingness to bid, but it does not guarantee that your own resale or business case is sound.

Record the maximum and the conditions under which it could be revised. New verified information about the asset may justify reconsideration. The mere existence of another bid usually does not. A broker or trusted adviser can help keep the decision anchored to the original objective rather than the emotional desire to win.

Understand the actual auction mechanism

Read the platform’s current rules for bidding, extensions, reserves, payment, delivery, and cancellation. Auction formats differ, and provider terms can change. GoDaddy’s Auctions Membership Agreement is one example of an authoritative place to check the applicable contractual framework rather than relying on an old forum explanation. ^[41]

Do not assume that a last-minute extension, proxy bid, or hidden reserve is evidence of manipulation. Those features may be part of the disclosed format. Conversely, a familiar format does not excuse conduct that violates the rules. Know the mechanism well enough to distinguish normal operation from a specific issue worth reporting.

For expired-domain auctions, understand whether delivery remains subject to the former registrant’s rights or other conditions under the platform’s process. Winning an auction and receiving the domain may be separate events. Do not announce a completed acquisition or build irreversible plans around the name until the actual delivery conditions have been satisfied.

Evaluate suspicious activity without overclaiming

A pattern of unusual bids may deserve attention, but outsiders often lack the account and payment information needed to determine what happened. Avoid publicly declaring that a bidder is a shill based only on aggressive behavior or a new account. Preserve the auction identifiers, timestamps, and observable pattern, then report the facts to the platform.

Ask the platform to review the issue under its rules. It may not be able to disclose another user’s private information, but it can explain relevant procedures or take action within its responsibilities. Keep your own decision separate: you can stop bidding when the price exceeds your limit even if the platform has not concluded an investigation.

Do not attempt to investigate by creating deceptive accounts, placing bids you do not intend to honor, or coordinating improper bidding with others. Those actions can breach terms, create legal risk, and make the original issue harder to assess. A legitimate complaint is stronger when your own conduct remains consistent with the platform’s rules.

Watch for off-platform second-chance offers

After an auction, a message may claim that the winning bidder failed to pay and offer you the domain at your last bid or a discount. Such an event can occur legitimately under some processes, but the message must be verified inside the genuine platform or through its authenticated support. An attacker can use public auction information to make an imitation offer seem timely and specific.

Do not send payment to a new private account or transfer service merely because the sender knows the auction number and your apparent interest. Confirm who currently owns or controls the domain, whether the platform recognizes the offer, and which terms apply. A second-chance opportunity should not erase the identity and payment checks required for the original purchase.

The same caution applies to a seller receiving a supposed winning-bid confirmation. Check the real account and funding status before delivery. A fraudulent email can imitate the platform’s language and claim that payment is secured while directing the seller to transfer outside the genuine process.

Worked example: the price that kept moving

A hypothetical investor values a domain at a maximum acquisition cost of $4,200 under their own resale assumptions. During the auction, repeated bids push the price higher. The investor becomes convinced that the competing bidder must know something valuable and considers raising the limit to $6,000. No new information about the domain has appeared.

The investor’s adviser separates two questions. First, is there observable activity worth reporting to the platform? Second, does the investor’s own valuation justify another bid? The investor records the unusual pattern for review but stops at the original limit. Whether the competition was genuine or manipulated, the investor avoids paying a price unsupported by their own plan.

Later, an email offers the domain privately for $4,000 because the winner supposedly defaulted. The investor verifies through the actual platform and finds no authorized offer. The earlier auction interest had become material for a new impersonation attempt. A disciplined bidding limit protected the price decision; independent platform verification protected the later payment decision.

Apply the same discipline to private negotiations

A seller or broker may say another buyer is ready to pay more. That can be true, but the buyer should not treat every claimed rival offer as independently verified market evidence. Ask how the statement affects the deadline and terms, then decide based on your own value and alternatives. You need not demand confidential details of another negotiation to maintain a rational limit.

A legitimate seller can choose among offers, and a buyer can decline to compete. The existence of a deadline is not itself fraud. The concern is a false representation used to induce action, especially when coupled with a demand to bypass verification or pay outside the agreed process. A qualified broker can help interpret the commercial context without pretending to know every hidden bidder’s intentions.

Auction safety is partly technical and partly behavioral. Use the genuine platform, understand its rules, preserve evidence of specific concerns, and keep your maximum grounded in the asset’s value to you. Winning is not the same as buying well. The best outcome may be acquiring the domain through a controlled process—or declining to become the person whose judgment was replaced by the excitement of the next bid.

Back to the contents

Chapter 31: Expired Domains, Redemption, and Drop-Catching Misunderstandings

An expired domain is not necessarily available to register, and a name offered in an expiry-related auction is not necessarily ready for immediate delivery. Different stages, provider practices, and registrant rights can intervene. Scammers exploit these misunderstandings by inventing recovery fees, promising guaranteed access, or presenting an uncertain acquisition as a completed sale. Honest buyers and sellers can also create disputes by assuming that everyone understands the same timeline.

ICANN’s renewal guidance emphasizes that renewal options, fees, and terms vary by registrar, while its Expired Registration Recovery Policy addresses specified obligations for covered registrations. ^{[42] [43]} Treat those sources as a framework and then verify the actual extension and provider. A single lifecycle diagram should not be applied indiscriminately to every domain, country-code namespace, or auction product.

Identify the present state before discussing recovery or purchase

Start with the exact domain and the current registrar or registry information. Determine whether the name is still within an existing registration arrangement, has entered a restoration-related status, is pending deletion, or has already been acquired by another registrant. The relevant provider can explain what actions are available in that state. Do not infer the answer merely from a website being offline.

For the former registrant, distinguish renewal or restoration from buying the name from a new holder. These are different processes with different parties and costs. If the original registrar can still restore the registration under the applicable rules, a stranger offering to “recover” it may be unnecessary. If the domain has genuinely passed to another registrant, the original renewal price may no longer describe the available commercial options.

For a prospective buyer, distinguish an opportunity to bid or place a backorder from a guarantee of acquisition. Read what the provider promises and what happens if it does not obtain the domain. A service may legitimately charge under a particular model, but the buyer should understand that model before paying. The word backorder should not be treated as a certificate that the domain is yours.

Understand restoration without inventing a universal clock

Covered gTLD processes can include a redemption grace period after deletion, during which the former registrant may be able to restore the domain through the relevant registrar. The precise applicability, fees, and current status matter. ICANN’s policy and registrar guidance should be checked together rather than turning a general statement about a restoration period into a promise for every extension. ^{[43] [42]}

Do not wait until the end of an assumed window. If the domain is important and has expired unexpectedly, contact the genuine registrar immediately. Ask what action is available now, what it costs, and what deadline applies to this particular registration. Save the response and assign someone to follow through. A calendar based on an old blog post is a poor substitute for current provider confirmation.

A restoration charge can be legitimate and higher than an ordinary renewal. That does not make every recovery invoice genuine. Authenticate the provider and the actual account event. A scammer may use a real concept, such as redemption, to justify a payment to an unrelated account. The existence of a legitimate fee category does not authenticate the sender requesting it.

Read auction and drop-catching conditions carefully

Expiry-related auctions may be governed by conditions that differ from an ordinary owner-listed sale. A prior registrant’s rights, provider processing, or other circumstances may affect final delivery. Before bidding, determine when the winner becomes entitled to receive the domain, which charges apply, and what happens if the name cannot be delivered under the service’s terms.

Drop-catching services attempt to obtain names when they become available under the relevant system. Their coverage, charging arrangements, and allocation methods can differ. Do not assume that placing an order with one service prevents others from competing or that paying a fee guarantees success. Evaluate the actual contract and provider record rather than a claim of secret access to every expiring name.

Be especially cautious when an unknown intermediary promises guaranteed delivery before the current holder has lost its rights or agreed to sell. Ask what right the intermediary presently controls. A legitimate acquisition service can explain uncertainty. An unsupported guarantee may be a way to collect a deposit for an asset the intermediary has no authority to deliver.

Distinguish a recovery problem from a valuation disagreement

A former owner who discovers that another party has lawfully acquired an expired name may feel that the new asking price is unfair. That frustration is understandable, but a high resale price alone does not establish theft or fraud. The relevant questions include whether the loss and subsequent acquisition were authorized under the applicable arrangements and whether any separate legal rights are implicated.

If you believe the expiration or transfer resulted from a provider failure, unauthorized action, or other wrongdoing, preserve the evidence and obtain appropriate advice. Do not assume that a trademark complaint is a universal recovery tool for every expired domain. The legal and administrative route depends on the facts. A broker can help negotiate a purchase, while counsel assesses claims and remedies.

Avoid threats designed merely to force a discount. They can damage a legitimate negotiation and create additional risk. A professional approach separates commercial acquisition from legal review. You can investigate your rights while keeping communications factual and allowing qualified advisers to handle issues that require legal judgment.

Worked example: the supposedly guaranteed backorder

A hypothetical entrepreneur notices that a desired domain has expired and receives an offer from a stranger who claims to control its release. The stranger requests a deposit to reserve the name and guarantees delivery within a week. The entrepreneur assumes that the displayed expiration date means the current owner can no longer retain it.

Before paying, the entrepreneur checks the genuine provider’s process and learns that the name’s status does not support the promised immediate delivery. The stranger cannot identify any ownership, authorization, or contractual right that would guarantee the acquisition. The entrepreneur declines the deposit and evaluates legitimate acquisition options under their actual terms. The central problem was not that expiry-related services are illegitimate; it was a guarantee unsupported by present rights.

In another scenario, a business loses track of its own renewal and receives a frightening recovery invoice. It contacts the original registrar directly and finds an available restoration route within the real account. The business resolves the issue there rather than paying the unsolicited sender. It then fixes the administrative failure that allowed the expiration, because recovery without better renewal ownership leaves the same vulnerability in place.

Plan for the domain’s next year, not just the acquisition day

After obtaining an expired domain, verify the renewal date and applicable charges in the receiving account. Do not assume that the auction price includes every future obligation. Some names or extensions can have renewal arrangements that differ materially from the buyer’s expectations. Ask for current provider information before bidding and confirm it after delivery.

Review the domain’s previous use, reputation, and possible legal issues separately. Expiration does not cleanse a name of every historical association, nor does age guarantee valuable traffic or search performance. The next chapters examine those claims in detail. A successful technical acquisition can still be a poor business purchase if the buyer relies on an untested story about the name’s past.

A qualified broker can help when the desired asset is strategically important, the route to acquisition is unclear, or the former owner needs a negotiated repurchase. For routine low-value expiry purchases, a well-understood provider process may be sufficient. In every case, the essential discipline is the same: identify the current state, understand the actual rights and terms, and refuse to turn an expiration date into a promise that the domain is available, recoverable, or deliverable on a stranger’s schedule.

Back to the contents

Chapter 32: Bulk Portfolios, Duplicate Listings, and Hidden Renewal Costs

A portfolio purchase can hide weak verification behind scale. Hundreds or thousands of names create an impression of substance, while the buyer may focus on a few attractive examples and assume the rest are as described. Duplicate entries, unowned names, inconsistent prices, renewal surprises, and active automated listings can then become expensive problems. The solution is to treat the portfolio as an exact inventory with defined rights and obligations, not as a persuasive headline number.

Bulk deals can be entirely legitimate and commercially efficient. They can also combine several risk types that are easy to manage individually but difficult to notice in a large spreadsheet. A strong process separates asset identity, ownership, cost, listing status, and delivery. Each category needs its own reconciliation so that a clean total in one column does not conceal a defect in another.

Establish the authoritative inventory

Obtain the complete list in a machine-readable format and preserve the original version. Normalize ordinary ASCII capitalization for comparison, retain meaningful characters, and identify exact duplicates. Check extensions, internationalized representations, and any entries that are URLs or subdomains rather than the registrations being sold. The number of spreadsheet rows should never substitute for the number of unique transferable assets.

Assign a stable identifier to the agreed schedule or otherwise control its version. If names are added or removed during negotiation, record the changes explicitly. A portfolio can retain the same row count while substituting weaker names for stronger ones. Compare exact strings between versions and review exceptions manually, especially for the assets responsible for most of the purchase price.

Ask whether every listed name is currently owned or authorized for sale by the contracting seller. A list may combine owned inventory, brokered listings, pending acquisitions, and names already sold elsewhere. Those categories should not be presented as interchangeable. The buyer needs to know which assets can actually be delivered and which conditions remain unresolved.

Reconcile ownership and account locations

Map each domain to its current registrar and relevant account or administrative arrangement. A portfolio spread across many providers may require multiple transfer paths and different timing. Grouping the names operationally can make the closing manageable, but do not let grouping hide an ownership exception. A single disputed premium name may matter more than hundreds of routine assets.

For a corporate seller, confirm that the same entity has authority over all included names or document the participation of other owners. Acquisitions, partnerships, and employee-held registrations can create mixed provenance inside one portfolio. Counsel should address material authority issues, while the broker coordinates the asset schedule and provider information.

Consider whether the seller’s accounts contain unrelated assets, personal information, or operational services. Buying a portfolio does not automatically justify taking over entire accounts. Use provider-supported transfers or an appropriately structured arrangement. An account-level shortcut can expose both parties to assets and data that were never part of the sale.

Calculate carrying costs before accepting the headline discount

Obtain current renewal information for the included names, especially unfamiliar extensions or names with premium renewal arrangements. Distinguish the purchase price from annual carrying cost. A portfolio that appears inexpensive per domain may require substantial ongoing expenditure to retain. The buyer’s investment case should include those costs rather than treating renewal as a minor administrative detail.

Use a realistic retention plan. Which names would you renew, develop, market, or deliberately let expire? Which are valuable only as part of a bundle? Do not assume every domain deserves indefinite renewal because it arrived in the purchase. A large portfolio can consume cash through many small obligations even when no individual charge looks significant.

Build a hypothetical sensitivity analysis rather than relying on a promised sell-through rate. For example, compare outcomes under lower sales volume, longer holding periods, and higher carrying costs. Label your assumptions clearly. The purpose is not to predict the market precisely; it is to see whether the purchase remains tolerable when the seller’s optimistic scenario does not occur.

Remove stale and automated sales exposure

Domains may remain listed on several marketplaces, sometimes with different prices or automated transfer arrangements. Afternic describes Fast Transfer as a mechanism for eligible names to transfer through its network under the program’s conditions. ^[17] A buyer and seller should therefore identify active authorizations and understand how existing listings will be removed or updated as part of closing.

Do not assume that changing the registrar account automatically clears every marketplace listing. Verify the relevant platforms’ procedures and document who is responsible for cleanup. An obsolete buy-now price can create a serious problem if the asset is still available through an authorized sales channel. A seller should not leave the same domain exposed to conflicting commitments while negotiating a portfolio sale.

After acquisition, establish the buyer’s own listing controls. Record approved prices, currencies, commission assumptions, and automated-sale settings. Limit who can change them. A portfolio owner who carefully negotiates a purchase but later permits uncontrolled bulk price updates has moved the risk from acquisition to administration rather than eliminating it.

Define partial delivery and exceptions

A large transaction may require staged delivery. Decide whether funds are released in tranches, whether individual values are allocated, and what happens if some names cannot be transferred. The selected provider must support the actual arrangement. Do not assume that a generic transaction description gives the provider enough information to administer a complex partial closing.

Identify indispensable assets. If the buyer’s rationale depends on a small core group, the agreement should address the consequences if one of those names fails delivery. A simple average price per domain may be misleading. Losing a principal asset is not necessarily compensated by receiving more low-value inventory.

Create an exception log with the domain, issue, responsible person, evidence required, and deadline. Examples include an unresolved lock, an ownership mismatch, an unexpected renewal charge, or a missing authorization. Keep exceptions visible until they are resolved or deliberately excluded. A portfolio should not be declared complete merely because most names have arrived.

Worked example: the thousand-name bargain

A hypothetical investor considers a package advertised as 1,000 domains for a low average price. Initial review highlights ten appealing names. Exact reconciliation reveals duplicate rows, several names no longer owned by the seller, and a group with renewal costs much higher than expected. One of the ten principal assets remains listed elsewhere at a conflicting buy-now price.

The investor’s broker rebuilds the schedule around verified unique assets, obtains current renewal information, and requires the conflicting listing issue to be resolved. Counsel and the provider define how exceptions affect price and closing. The resulting package may still be attractive, but it is a different proposition from the original headline. The buyer negotiates on the verified inventory rather than paying for the advertised count.

The investor also models the cost of retaining the portfolio for several years without assuming rapid sales. That analysis leads to a smaller purchase focused on names that fit the investor’s strategy. No accusation is needed to justify the change. Due diligence has converted an impressive-looking bundle into a decision based on actual assets, costs, and delivery conditions.

Finish with a portfolio-level audit

After closing, reconcile the delivered names against the final schedule, verify renewal settings, secure accounts, and confirm listing cleanup. Retain evidence for each delivery group and unresolved item. Assign ongoing ownership of the portfolio register so that the information remains useful after the transaction team moves on.

A qualified broker is particularly valuable when scale creates coordination risk: many names, multiple registrars, mixed ownership records, or staged delivery. The broker should help make the transaction more explicit, not encourage the buyer to skip review because the package is large. In bulk domain investing, the safest discount is the one calculated on an accurate inventory. A thousand rows are not a thousand verified assets until the work has been done.

Back to the contents

Chapter 33: Fabricated Traffic, Revenue, and Buyer Demand

A domain’s value can be presented through numbers that look more objective than they are. A seller may show traffic charts, advertising income, inquiry counts, or a list of supposed interested buyers. Those figures can be genuine, misleadingly selected, or fabricated. Even accurate historical data may not describe what the buyer will receive after the transaction. Verification therefore needs to address both authenticity and transferability of the claimed benefit.

Begin by identifying what is actually for sale. A domain-only acquisition is different from purchasing a website, content library, customer relationships, advertising accounts, or an operating business. Traffic generated by a seller’s marketing campaign may not follow the domain after closing. Revenue earned through a personal account may not transfer at all. Do not pay for an earnings story until the assets and dependencies behind that story are clearly defined.

Define the metric before judging the number

Ask what the seller means by traffic. The figure may refer to visits, users, page views, requests, redirects, or another measure. It may include automated activity, internal testing, paid campaigns, or traffic to multiple properties. Without a definition, a large number can be impressive while remaining commercially meaningless. Require the reporting period, source, filters, and relevant property to be identified.

For revenue, distinguish gross receipts from net profit and cash received from amounts merely recorded. Ask about refunds, advertising costs, commissions, taxes where relevant, operating expenses, and one-time events. A seller may accurately report gross income while leaving the buyer with a false impression of sustainable profit. That can be a disclosure problem even without a forged screenshot.

For buyer demand, distinguish casual inquiries, automated messages, broker approaches, nonbinding offers, and completed purchases. Ten people asking for a price does not equal ten qualified buyers at the asking price. A genuine inquiry can still be too low, unauthorized, or contingent to support the seller’s valuation. Treat the demand narrative as a claim requiring context, not as a guarantee of future liquidity.

Obtain evidence through a proportionate process

Where appropriate, review data through a secure, limited-access method or an independent professional rather than relying only on screenshots. The exact method depends on the platform and the sensitivity of the information. Do not demand passwords or broad account control merely to inspect a report. The seller should be able to protect unrelated data while providing credible evidence for material claims.

Compare more than one relevant source when practical. Traffic reports, server-side information, advertising statements, payment records, and financial summaries can illuminate different parts of the story. Agreement among them can improve confidence, while discrepancies should be explained. None should be treated as automatically definitive outside its scope. A payment receipt may confirm money received without proving that the income will recur.

Use a period long enough to evaluate the claim being made. A single strong week may not support an annualized earnings assertion. Ask whether seasonality, publicity, paid promotion, or an unusual event affected the results. A legitimate seller can explain these factors. The buyer’s task is to understand the business mechanism rather than mechanically multiply the most attractive short period.

Test whether the benefit survives the sale

Identify what generates the traffic or revenue. Is it direct navigation to the domain, search visibility tied to content, paid advertising, a social audience, an email list, or referrals from another property? Which of those assets and arrangements are included? Which depend on the seller’s identity, account, relationships, or continued spending? The acquisition should be valued according to what the buyer can actually retain and operate.

Ask what will change at closing. A new website, removed content, different hosting, discontinued advertising, or a changed business model may alter performance. The seller’s historical numbers can still be useful, but they should not be presented as a forecast unaffected by the buyer’s choices. A broker and specialist adviser can help separate the domain’s standalone value from the value of a larger operation.

For revenue-producing properties, define the transition obligations. Will the seller assist with permitted account transfers, provide documentation, or maintain certain services temporarily? Confirm that third-party terms allow the proposed arrangement. Do not assume that possession of the domain transfers every account, contract, license, or audience associated with the website.

Look for selective presentation and invented comparables

A report may exclude weak months, show only one successful page, or combine several domains into one total. Ask for the boundaries of the dataset. If the asset schedule contains one domain, the supporting performance should relate to that asset or clearly explain any shared infrastructure. A portfolio-level number should not be silently assigned to the most attractive name.

Comparable sales deserve similar scrutiny. Verify that a cited transaction actually occurred where evidence is available, identify whether the price included other assets, and consider how comparable the name and buyer circumstances really are. An asking price is not a completed sale. A seller’s anecdote about an undisclosed offer should not receive the same weight as independently documented transaction evidence.

Avoid pretending that every uncertainty can be solved with a precise discount. Some missing evidence makes the underlying claim unusable rather than merely worth ten percent less. When the price depends heavily on unverified revenue or demand, the buyer may need stronger evidence, a different structure, or a decision not to proceed. A numerical valuation should not conceal a foundational information gap.

Worked example: the profitable domain that was a campaign

A hypothetical buyer is offered a domain with a claimed monthly advertising income of $2,000. The seller supplies a chart showing substantial visits and several payment receipts. The buyer initially values the asset as though those receipts will continue after a simple domain transfer. Further review reveals that most visits came from a paid campaign and that the reported figure is gross revenue before campaign costs.

The buyer’s adviser asks for the relevant expense records and identifies which accounts and content would be included. The campaign is not part of the sale, and the seller’s personal advertising account cannot simply be handed over under the proposed arrangement. The buyer reassesses the domain on a standalone basis and either negotiates a different purchase or declines. The receipts may be genuine, but the original interpretation was not supported.

In a fraudulent variation, independent review also shows that the screenshots do not match the underlying account records. The buyer stops and preserves the evidence. The same due-diligence process can reveal a misunderstanding, selective disclosure, or outright fabrication without assuming in advance which explanation is correct.

Put material claims into the agreement

If traffic, revenue, or other performance is central to the price, have counsel address the relevant representations, disclosures, records, and remedies. Avoid relying on informal sales language that disappears from the final contract. The agreement should accurately describe what is being sold and which statements the parties are prepared to stand behind.

A verified escrow provider can administer agreed payment and delivery conditions within its service, but should not be assumed to audit earnings or guarantee future performance. Those tasks may require separate expertise. Align the inspection period with the actual evidence and asset package rather than expecting a brief domain-receipt check to resolve an operating-business valuation.

A qualified broker can help challenge inflated claims, identify relevant comparables, and bring in specialist review when needed. The client should still understand the economic mechanism behind the purchase. Numbers are useful when they describe a verified, transferable benefit. They are dangerous when they serve as decoration around a promise that the domain will somehow continue earning money after the very systems producing that money have been left behind.

Back to the contents

Chapter 34: Backlink Claims, Expired-Domain SEO, and Ranking Guarantees

A domain offered for its search-engine value often comes with a persuasive collection of numbers: backlinks, referring sites, authority scores, historical traffic, and keyword positions. These can be useful research inputs, but they are not a transferable guarantee of rankings. A buyer needs to understand what the measurements describe, whether they are authentic, and how the proposed use differs from the use that produced the historical results.

Google’s spam policies identify expired-domain abuse as repurposing an expired domain primarily to manipulate rankings while providing little or no value to users. The policy does not declare every purchase or legitimate reuse of an expired domain abusive. ^[44] That distinction is important. The safe commercial question is whether the acquisition supports a useful, lawful project—not whether an old domain can be treated as a machine that automatically manufactures search visibility.

Separate the name from the website’s past performance

A domain may have hosted a respected publication, a small business, a parked page, or several unrelated projects. Historical rankings may have depended on content, expertise, links, user demand, and other circumstances that will not continue after purchase. Ask which elements are included in the transaction and which the buyer would need to recreate or replace legitimately.

An attractive domain can still be worthwhile for branding even when its historical search performance is uncertain. Conversely, a domain with impressive historical charts may be unsuitable for the buyer’s business. Do not let a search metric obscure spelling, audience fit, legal suitability, renewal costs, or the ability to obtain the actual asset from an authorized seller.

A broker who specializes in premium names may help assess branding and market value, while a qualified search specialist evaluates technical and historical claims. Those are complementary skills. Do not assume that expertise in negotiating domain sales automatically includes a forensic audit of a website’s backlink profile or search history.

Ask what each metric measures

Third-party tools use their own methods and data coverage. A score from one service is not a promise from a search engine, and scores from different services may not be directly comparable. Record the tool, date, property, and relevant settings. A screenshot showing a high number without context should not carry the same weight as a review of the underlying evidence.

Examine the links themselves where they are material to the purchase. Are they relevant to the intended project? Do they point to pages that still exist or to content not included in the sale? Are they concentrated in a small number of sources? Could they disappear when a relationship or campaign ends? The objective is not to count every link manually, but to understand the mechanism behind the seller’s claim of value.

Distinguish historical presence from current usefulness. A report may include links that no longer function or traffic from a period before the site changed. A seller may select the most favorable tool or date. Ask for a consistent analysis and explanations for discrepancies rather than accepting whichever metric produces the largest valuation.

Review available search and security evidence

Where the seller controls a relevant Search Console property and appropriate access can be arranged, review available information through a secure, limited process. Google distinguishes its Manual Actions report from its Security Issues report: they address different categories of problems. ^[45] Neither should be treated as a universal certificate that the domain is free of every historical or future search risk.

A clean report at one moment does not guarantee future ranking performance. It also does not replace review of the actual website, content rights, or business model. Conversely, the absence of access to historical data may reflect a domain-only sale rather than deliberate concealment. The buyer should recognize the resulting uncertainty and avoid paying a premium based on claims that cannot be substantiated.

If a material issue appears, obtain specialist advice before deciding whether remediation is practical. Do not accept a seller’s promise that a transfer automatically removes every problem. Ask what work would be required, what evidence supports the proposed remedy, and what uncertainty remains. A purchase agreement can allocate responsibilities, but it cannot force a search engine to deliver a particular result.

Reject guaranteed-ranking shortcuts

A seller or consultant may promise a first-page position merely because the domain is old, contains a keyword, or has a high third-party score. Such a promise should be examined critically. Ask which outcome is actually guaranteed, under what conditions, and what remedy is offered if it does not occur. A guarantee that refunds a small service fee may not compensate for an expensive domain purchase or failed business launch.

Do not confuse a forecast with evidence. A projection may be useful when its assumptions are explicit, but it should not be presented as a fact about the future. Require a distinction between verified historical results, professional judgment, and speculative upside. This makes it possible to assess the deal without either dismissing all expertise or accepting certainty that nobody can substantiate.

Be cautious when the proposed strategy depends on deceptive or policy-violating practices. A short-term claim of advantage may create a long-term business problem. The buyer should understand the applicable platform rules and build a project that remains useful without relying on manipulation. A domain acquisition should strengthen the business, not make its visibility dependent on an undisclosed shortcut.

Worked example: the authority score that drove the price

A hypothetical buyer is offered an expired domain at a substantial premium because a third-party tool assigns it a strong authority score. The seller says the buyer can publish unrelated commercial content and immediately inherit the former site’s rankings. The buyer’s initial valuation assumes that the score will translate directly into profitable search traffic.

A specialist review finds that the historical links largely concern a former nonprofit project, several important pages are not included, and the available traffic data predates major changes. The buyer also reviews the proposed use against current search policies. The domain may still have some branding value, but the claimed automatic ranking benefit is not supported. The buyer either reduces the valuation to a defensible basis or declines.

In a legitimate alternative, the buyer acquires relevant rights and develops a useful project with a clear audience, while treating historical signals as uncertain context rather than guaranteed income. The acquisition is then evaluated as part of a real publishing or business plan. The difference is not simply whether the name expired; it is whether the purchase is built around verified assets and a credible use.

Put search claims in the right part of the decision

Create a separate due-diligence section for search-related evidence. Record what was reviewed, what could not be verified, and which assumptions affect the price. Do not mix this with the basic delivery checklist. Receiving the correct domain proves one thing; receiving the economic benefit implied by a search-sales pitch is another.

When a website is included, define the content, redirects, accounts, documentation, and transition work that matter to the buyer. Confirm that the seller has the rights to transfer them. A technically successful domain transfer can leave the buyer without the material that supported the old site’s audience. That gap should be discovered before acceptance, not explained away afterward as a normal part of SEO.

A qualified broker can help prevent the acquisition process from being dominated by a glossy metrics report, especially when the client’s real objective is a durable brand asset. Bring specialist review into the deal when search performance materially affects the price. The strongest purchase is one whose value remains understandable after the most flattering score and the most optimistic ranking promise have been removed from the presentation.

Back to the contents

Chapter 35: Buying a Website Is Not the Same as Buying a Domain

A domain is an address-related asset; an operating website may include content, software, databases, accounts, contracts, intellectual property, customer information, and ongoing obligations. A seller who uses the word website loosely can leave a buyer expecting a business while delivering only a domain. Fraud can exploit that ambiguity, but even honest parties can disagree when the asset package was never defined precisely.

Escrow.com separately describes transactions involving a domain with website content, illustrating that the delivery scope can extend beyond registration control. ^[46] The important lesson is not that one provider solves every website acquisition. It is that the parties must identify the actual assets and choose a process capable of handling them. A domain-transfer confirmation alone cannot establish delivery of everything needed to operate a website.

Build an asset schedule that describes the business reality

List the domain separately from the other components. Identify the website files, source code, content, images, databases, documentation, trademarks or other rights where included, and any accounts intended to transfer. Avoid phrases such as “all related assets” as the only description of a complex package. They can conceal disagreements about what exists, what is owned, and what may legally be transferred.

Identify exclusions just as clearly. The seller may retain a company name, personal social account, unrelated content, customer contracts, or a software license that cannot be assigned. The buyer needs to know those limits before valuing the package. An exclusion is not necessarily unfair, but an undisclosed dependency can make the purchased website unusable or materially less valuable.

For a business acquisition, involve appropriate legal and financial advisers. The transaction may raise issues far beyond domain registration, including liabilities, taxes, employment, contracts, and data protection. A domain broker can coordinate the naming asset and commercial negotiation within its competence, but should not be treated as a substitute for specialists reviewing an operating business.

Verify rights in content and software

Ask whether the seller created or properly acquired the rights to the content and code being transferred. A website can display images, articles, plugins, themes, or software under licenses that do not automatically pass to a buyer. The fact that the seller can copy the files does not establish the right to sell every component. Counsel or a qualified technical reviewer should assess material dependencies.

Identify third-party subscriptions and services. Hosting, analytics, payment processing, advertising, email delivery, and software tools may each have their own account and assignment rules. Do not assume that changing a password is a permitted transfer. Confirm the provider-supported method and plan for new accounts where needed.

Record what the seller will deliver as evidence of rights and configuration. This may include license records, repository access, deployment instructions, and documentation of custom work. The goal is not merely to receive a folder of files. It is to obtain a package the buyer can lawfully operate, maintain, and secure under the agreed scope.

Treat customer data as a separate responsibility

A database may contain personal information, credentials, payment-related records, or sensitive communications. Its transfer can raise legal and security obligations that differ from those governing the domain itself. Do not assume that a website sale automatically authorizes unrestricted disclosure of all user data to every prospective buyer.

Use staged due diligence and minimize unnecessary exposure. Aggregated or limited information may be sufficient for an initial evaluation. More detailed access should follow a defined purpose, appropriate safeguards, and qualified advice about the applicable rules. The ICO’s data-minimisation guidance is a useful example of the principle that personal data should be relevant and limited to what is necessary in the applicable context. ^[47]

Plan the post-closing handling of data as well. Who will retain historical records, respond to users, manage access, and delete material when appropriate? What notices or consents may be required under the relevant circumstances? These questions should be resolved with competent advice, not left to a technical administrator who assumes that transferring a database is equivalent to transferring a domain.

Test operations before defining acceptance

Identify the functions the buyer needs to verify: account login, content display, forms, order processing, integrations, administrative access, and backups where included. Define a suitable test environment and avoid exposing live customer data unnecessarily. A screenshot of a working homepage is not evidence that every important function or dependency will work under the buyer’s control.

Specify the seller’s transition assistance. Will they explain deployment, help migrate services, answer technical questions, or correct agreed defects? For how long, and under what limits? A promise to “help after closing” is less useful than a defined obligation with a responsible contact. The buyer should not depend indefinitely on the seller’s goodwill to perform basic operations.

Align the inspection period with the asset package and provider service. A brief check that a domain appears in an account may be suitable for one transaction but inadequate for a complex website migration. The provider must understand the agreed deliverables and any conditions it is expected to administer. Do not assume that every commercial promise can be enforced through a generic acceptance button.

Worked example: the website without the machinery

A hypothetical buyer agrees to purchase a small content website, including its domain, because the seller reports recurring affiliate income. At closing, the buyer receives the domain and a backup of the visible pages. The seller then explains that the affiliate account, email list, custom software license, and original image rights were not included. Those exclusions were never clearly addressed in the negotiation.

A better pre-closing process would have separated each component, verified transferability, and valued the package accordingly. The buyer’s broker could coordinate the asset list, while counsel and technical advisers reviewed rights and dependencies. The agreement could then specify what must be delivered and what the buyer must replace independently. The sale might still proceed, but the price and transition plan would reflect the real package.

In a deliberately deceptive version, the seller knew that the revenue depended on nontransferable arrangements and concealed that fact. The buyer’s remedy would depend on the contract, evidence, parties, and applicable law. That uncertainty is precisely why clear scope and verification are preferable to discovering the missing machinery after funds have been released.

Secure the acquired environment

After delivery, review administrative users, recovery methods, API credentials, integrations, and access granted to contractors. Rotate appropriate secrets and establish the buyer’s own recovery controls under the providers’ supported processes. Do not assume that receiving the seller’s old password removes every route by which the seller or another person can still access the system.

Verify backups and the ability to restore the acquired site in an appropriate environment. Document the infrastructure and renewal responsibilities. A website can continue working temporarily while depending on a seller-controlled subscription that will soon expire. The handover should identify those dependencies before they become an outage or a leverage point in a dispute.

Keep the domain itself under clear ownership and security arrangements even when the broader migration is complex. It may be sensible to separate registration custody from hosting operations so that a website contractor does not automatically control the naming asset. The exact architecture depends on the business, but authority should be explicit rather than inherited accidentally from whichever account was easiest to use.

Choose professionals for the actual transaction

A domain-only purchase may need a broker and a suitable transfer or escrow process. A website or business acquisition may additionally need technical, legal, accounting, and data-protection expertise. Select support according to the assets and risks, not the label used in the listing. Calling a deal a domain sale does not make the other components disappear.

A qualified broker can add substantial value by forcing the parties to define what is being negotiated and bringing the right specialists into the conversation. That is more useful than treating a successful registrar transfer as proof that a complex digital business has been delivered. Buy the package you have actually verified, document the package you have agreed, and inspect the package you receive before declaring the transaction complete.

Back to the contents

Chapter 36: Leases, Installments, Options, and Lease-to-Own Traps

Not every domain deal ends with an immediate exchange of full payment for full control. A lease may grant temporary use. An installment arrangement may spread the price over time. An option may create a right to buy under defined conditions. A lease-to-own structure may combine use with a future transfer. These arrangements can be useful, but they introduce questions that a simple one-time sale does not answer.

Escrow.com distinguishes ordinary domain transactions from its domain-name holding service, which addresses longer-term payment arrangements under the service’s terms. ^[48] That distinction illustrates why the exact structure matters. Do not assume that a familiar payment brand automatically supplies every custody, default, renewal, or operational protection needed for a multi-year agreement. The parties, counsel, and provider must understand the same arrangement.

Define the rights at every stage

Ask what the user may do before the final payment. Can they operate a website, configure email, change nameservers, create subdomains, or license the name to others? Who remains the registrant or otherwise holds the relevant rights? Who controls the registrar account? A buyer making installments should not assume that early access equals completed ownership, and a seller should not assume that retaining account control resolves every legal issue.

For an option, identify the exercise process, price, deadline, and any conditions. Paying for an option is not the same as paying for the domain itself. The holder should know exactly what action is required to exercise it and what happens if the deadline passes. Counsel should draft or review material arrangements rather than relying on a casual phrase such as “first chance to buy.”

For a lease, clarify whether payments contribute to a future purchase or simply compensate for use. The term lease-to-own can conceal different economics. The agreement should show the total payments, any final amount, fees, and circumstances in which prior payments are retained or credited. A low monthly figure should not distract from the total commitment and the consequences of default.

Establish neutral custody and operational control

Where a holding service is used, verify the provider and the exact custody arrangement. Ask who can authorize transfer, what events permit release, and how disputes or missed payments are handled. The provider should confirm that it supports the proposed terms. Do not assume that a standard account at the provider can administer a bespoke agreement simply because the parties mention it in an email.

Decide who controls DNS and other operational settings during the term. A user may need to run a business without being able to transfer the registration away. The seller may need protection against misuse while avoiding arbitrary interference with legitimate operations. These competing interests should be addressed explicitly, with a process for authorized changes and emergency issues.

Do not use password sharing as a substitute for a custody design. If both sides know the same credentials, either may be able to alter recovery methods or lock out the other. Provider-supported permissions and a clear legal structure are preferable. The technical arrangement should implement the agreement rather than undermine it through uncontrolled shared access.

Allocate renewals, fees, and compliance obligations

A multi-year deal needs a named party responsible for renewals and a method to verify they occur. Missing a renewal can damage both the owner’s asset and the user’s business. Identify who pays ordinary and any applicable premium renewal charges, who receives notices, and what happens if costs change under the relevant provider’s terms.

Address provider fees, currency issues, late payments, and other expenses. Do not let the advertised monthly payment conceal charges necessary to keep the arrangement functioning. Ask whether the provider’s fee schedule can change and how the agreement allocates that possibility. The appropriate treatment depends on the deal and should be understood before the user builds a business around the name.

Clarify who must maintain eligibility for an extension with registrant restrictions and who responds to legitimate legal or abuse notices. A long-term arrangement should not depend on an assumption that no one will ever question the domain’s use. Counsel and the relevant provider can help identify obligations that cannot simply be delegated by private agreement.

Plan default and exit before they occur

Define what counts as a missed payment or other breach, what notice is required, whether there is a cure opportunity, and what happens next. The agreement should address both the domain and the business services operating on it. An abrupt loss of email or website access can have consequences far beyond the remaining payment balance.

Avoid assuming that every default entitles one party to seize data, impersonate the other, or take unrelated accounts. Rights and remedies depend on the agreement and applicable law. Obtain legal advice for material arrangements and use provider-supported procedures. A dispute should not be resolved through technical self-help that creates new legal or security problems.

Plan voluntary termination, early payoff, assignment, and the final transfer as well. The user should know what evidence confirms completion and how custody ends. The seller should know when obligations are satisfied and whether any transition duties remain. A multi-year deal should have a defined finish line, not a final payment followed by another round of uncertainty about who must authorize delivery.

Worked example: the affordable name with an unsafe default clause

A hypothetical startup cannot afford the full price of its preferred domain and considers a thirty-six-month arrangement. The monthly payment appears manageable. The draft, however, allows immediate loss of use after a minor payment delay, does not specify who renews the registration, and leaves the domain in an account whose recovery email belongs to an unverified intermediary.

The startup’s broker identifies the commercial appeal but does not recommend signing the arrangement as written. Counsel clarifies default and notice provisions, the parties select an authenticated holding process, and renewal responsibility is documented. The provider confirms what it can administer. The startup can then evaluate the total cost and operational exposure rather than judging the deal solely by the monthly figure.

In a deceptive variation, the intermediary refuses neutral custody and claims that a separate release fee will be determined only after the last installment. The startup declines. An installment plan is not safe merely because no single payment equals the full purchase price. Repeated payments and dependence on the name can create a substantial exposure long before the promised final transfer.

Evaluate the business dependence created by early use

A user who builds a brand, email system, and customer base on a leased domain becomes increasingly dependent on the arrangement. That dependence may strengthen the owner’s negotiating position if the contract is unclear. Before launching, consider whether the rights and exit provisions are robust enough for the intended scale of use. A cheap initial term can become expensive if the business cannot leave without disruption.

For the owner, consider reputational and legal risks associated with the permitted use. A domain returned after a failed arrangement may have acquired unwanted associations or operational complications. Appropriate use restrictions, monitoring rights, and remedies need careful drafting and proportionate implementation. They should not become an excuse for arbitrary access to the user’s unrelated business data.

A qualified broker can help structure commercial terms and identify a suitable transaction path, while counsel and the provider address their respective responsibilities. Long-term domain arrangements reward clarity more than optimism. The right question is not only whether both parties trust one another today. It is whether the agreement and custody process still work when a payment is late, a business changes direction, a provider needs action, or the relationship is no longer friendly.

Back to the contents

Chapter 37: Tokenized Names, Blockchain Naming, and Fractional-Ownership Claims

A digital token associated with a name is not automatically the same asset as a conventional domain registration. A blockchain naming service may operate under different rules, a token may represent a contractual interest, or a platform may claim to connect token ownership with a DNS domain held elsewhere. Before buying, identify exactly which rights exist, which system records them, and what you can actually do with the asset after the transaction.

ENS’s own explanations distinguish its naming arrangements and their development from conventional DNS while discussing connections between the systems. ^{[49] [50]} That illustrates why broad labels such as blockchain domain or tokenized domain are insufficient. The buyer needs to evaluate the specific implementation and legal arrangement rather than assuming that every product bearing a familiar name has the same ownership, renewal, transfer, or resolution characteristics.

Identify the asset and the namespace

Ask whether the purchase concerns a conventional DNS registration, a blockchain-native name, a token connected to a conventional domain, a subname, or a share in an entity or contract. Write the answer into the transaction record. The visible word may look like a domain, but the rights can differ substantially. A naming asset that works in one application may not behave like a conventional address across ordinary internet services.

Determine which network, registry, contract, or platform governs the asset. Avoid relying on the seller’s screenshot of a wallet or marketplace listing. Verify the relevant records through appropriate trustworthy tools and technical expertise. The exact identifier matters, just as the exact spelling matters in a DNS-domain sale. A similarly named token on another network may be a different asset entirely.

Ask what the buyer expects to use the name for. Website access, wallet-address resolution, identity, investment, and brand protection are different objectives. A technically genuine asset can still fail the buyer’s intended purpose. The transaction should be evaluated against actual compatibility and rights, not a general promise that the technology will replace everything familiar.

Examine the link between token and conventional domain

If a token is said to represent a DNS domain, determine who is the registrant and who controls the registrar account. What legally obliges that party to honor the token holder’s instructions? How is a redemption or transfer requested? What happens if the platform stops operating, the domain expires, or a dispute arises? A blockchain entry does not answer those off-chain questions by itself.

Review whether the connection can be changed, revoked, or administered by another party. The seller may describe the system as decentralized while an intermediary retains important powers over the actual registration or user interface. That does not necessarily make the service fraudulent, but the retained powers should be understood and reflected in the valuation and risk assessment.

Obtain qualified legal and technical advice when the asset is valuable or the structure is unfamiliar. The lawyer evaluates enforceable rights and obligations; the technical specialist evaluates the actual implementation and control path. A domain broker’s experience can help with the conventional-domain component, but should not be treated as automatic expertise in every token contract or digital-asset arrangement.

Understand wallet and contract exposure

A purchase process may request a wallet connection, signature, or approval. Do not approve an action you do not understand merely because the website calls it verification. The displayed label may not fully describe the authority granted. Use appropriate technical review and a transaction environment designed for the risk. Never disclose a wallet recovery phrase or private key to a purported broker, support agent, buyer, or seller.

Keep the naming purchase separate from unrelated assets where practical. An account or wallet containing substantial unrelated value should not be exposed casually to an unfamiliar transaction interface. The appropriate setup depends on the technology and should be designed with competent assistance. The principle is to limit the consequences of a mistaken approval rather than assuming that recognizing the name of a marketplace makes every request safe.

Do not accept a successful small transaction as proof that all later actions are safe. A test can verify a narrow technical path, but it does not establish legal rights, future liquidity, or the legitimacy of a larger payment. Scams can include genuine-looking preliminary steps. Evaluate the actual high-consequence action independently.

Treat fractional interests as a different purchase

A fractional-ownership offer may promise a share of future domain-sale proceeds rather than direct control of the domain. Identify the legal instrument, the entity or person responsible, voting or sale rights, fees, distribution rules, and exit options. Owning a fraction of a claim is not the same as owning a fraction that you can independently use as a domain.

Ask who decides when to sell, how the sale price is established, and whether related-party transactions are possible. What records will investors receive? Who holds the domain and the money? What happens if expenses exceed revenue or the manager becomes unavailable? These questions concern governance and financial risk, not merely technical transferability.

Such structures can raise regulatory and legal issues depending on their design and jurisdiction. Obtain qualified advice rather than accepting a promoter’s statement that tokenization removes all regulation. A technical wrapper does not automatically eliminate obligations that would otherwise apply to an investment or contractual arrangement. Do not invest money needed for essential obligations on the strength of a claim that an unfamiliar structure is risk-free.

Worked example: the token that did not convey the domain

A hypothetical buyer sees a token advertised as ownership of a premium .com. The marketplace shows a polished image of the name and a history of token transfers. The seller says that receiving the token gives the buyer complete control of the domain. The buyer’s intended use is a conventional business website and email system.

Before paying, the buyer asks who holds the DNS registration and how the token holder can compel transfer. The documentation reveals that the token provides only a revocable platform benefit and no clear right to receive the underlying registration. The registrar account remains controlled by an unrelated entity. The buyer declines because the offered rights do not match the intended acquisition, even if the token itself is technically genuine.

In a more robust arrangement, the legal documents, custody process, and technical controls may establish a meaningful connection between the token and domain. The buyer would still need to verify those elements and assess the platform’s risks. The label tokenized does not decide the answer in either direction; the actual rights and control path do.

Reject liquidity and permanence slogans

A promoter may say that tokenization guarantees instant resale, permanent ownership, or universal acceptance. Ask for the precise meaning of each claim. A token being transferable does not guarantee that a buyer exists at the desired price. A naming system’s rules may include renewal or other conditions. A service working in selected applications does not establish universal compatibility.

Evaluate fees, custody, recovery, and operational continuity. What happens if you lose access, approve a harmful action, or encounter a disputed transfer? Who can help, and what can they actually do? Avoid assuming that either a conventional registrar or a blockchain community will reverse an event simply because the buyer made a mistake. Recovery possibilities depend on the system and facts.

For conventional premium-domain objectives, an experienced broker and a familiar, verified transfer structure may provide a clearer route than an opaque token wrapper. For a genuinely appropriate blockchain naming use, specialist advice remains essential. The safest decision begins by stripping away the promotional vocabulary and asking a plain question: after payment, which enforceable rights and technical capabilities will belong to you, and which will still depend on someone else?

Back to the contents

Chapter 38: Valuation Hype, Guaranteed Flips, and Domain Investment Schemes

A domain can be a useful business asset or a speculative investment without being a guaranteed source of profit. Scams exploit the gap between those ideas. A promoter may sell a package of names, a training program, a managed portfolio, or access to supposed buyers while promising rapid, low-risk returns. The names may even be real. The deception can lie in the claimed demand, earnings, expertise, or certainty of resale.

The FTC’s investment-scam guidance warns about promises of high returns with little risk and training schemes built around misleading success claims. ^[51] Applied to domains, the lesson is to evaluate the actual assets, costs, operator, and revenue mechanism. A compelling story about digital real estate is not a substitute for evidence that the proposed purchase or service fits your resources and risk tolerance.

Separate an asking price from realizable proceeds

A seller can list a domain at almost any asking price. That figure does not establish what a qualified buyer will pay or when a sale will occur. An automated estimate likewise does not create a purchaser. When evaluating an investment pitch, ask whether the cited values are completed transactions, current offers, appraisals, or merely the promoter’s preferred prices.

Comparable sales require context. A name acquired by a strategically motivated end user may not be comparable to a portfolio name with a different spelling, extension, audience, or legal position. A public sale price may also omit terms relevant to comparison. Use evidence carefully and acknowledge uncertainty rather than treating the highest reported transaction as a universal benchmark.

A domain broker can contribute market judgment, negotiation experience, and access to relevant commercial conversations. That does not mean the broker can guarantee a buyer for every name. A professional who explains why an asset may be difficult to sell can provide more value than a promoter who validates every purchase with a large theoretical price.

Calculate cash flow, not just headline multiples

Include acquisition costs, renewals, marketplace or brokerage charges, professional expenses, and the time required to manage the portfolio. Distinguish cash received from unsold inventory values. A portfolio can contain names listed at impressive prices while still requiring ongoing cash to maintain. The ability to continue holding matters when sales are uncertain.

Consider a purely hypothetical example, not a market forecast. An investor buys 100 domains for $40 each, spending $4,000. Assume all 100 incur a $15 renewal during the modeled year before any sales, adding $1,500. Two names sell for $2,000 each, producing $4,000 gross. Assume transaction and selling charges equal 20 percent of those sales, or $800; this is an illustrative assumption, not a quoted industry or brokerage fee.

Under those assumptions, the year’s cash inflow after selling charges is $3,200, against $5,500 in acquisition and renewal outflow. The net cash movement is negative $2,300 before taxes and other expenses. The investor still holds 98 domains, so this is not a complete accounting valuation of the portfolio. It does show why two attractive sales do not automatically mean the overall activity produced positive cash flow.

Test the assumptions the promoter avoids

Ask what happens if no domains sell during the first year, if sales take longer, or if renewal costs are higher than expected. A useful model should show those possibilities rather than only the optimistic case. Do not borrow money or commit essential savings because a spreadsheet assumes that a fixed percentage of names will sell at a fixed price every year.

Examine how the promoter selected the portfolio. Are the names commercially plausible, legally suitable, and genuinely owned? Do they fit a defined end-user market, or are they a random collection justified by automated valuations? A large quantity can create the impression of diversification while repeating the same underlying weakness across many assets.

Ask whether the operator earns primarily from selling domains to end users or from selling inventory, subscriptions, coaching, and upgrades to new participants. The second model is not automatically fraudulent, but it changes the incentives and the evidence you need. A provider may profit even when the client never resells a single name. That conflict should be visible in the decision.

Scrutinize buyback and guaranteed-buyer promises

A promoter may promise to repurchase unsold domains at a profit or say a network of buyers is waiting. Identify the actual contractual obligation, the entity making it, the conditions, and the financial ability to perform. A guarantee from an unverified or undercapitalized entity may offer little practical protection. The word guaranteed should increase scrutiny, not reduce it.

Read exclusions carefully. A buyback promise may apply only after expensive additional services, require impossible conditions, or offer credit for more inventory rather than cash. A buyer network may consist of other participants rather than independent end users. The economic mechanism should remain understandable after the marketing language is removed.

Do not pay an extra release, tax, verification, or upgrade fee merely to withdraw supposed profits shown on a dashboard. Verify the underlying transactions and contact the relevant financial institution or adviser when fraud is suspected. A displayed balance can be fictional, and paying to unlock it may simply extend the scheme.

Evaluate education and managed services on their own merits

A course can be legitimate even if students do not earn money, provided it is honestly described and delivers the promised instruction. Assess the curriculum, instructor’s verifiable experience, total cost, refund terms, and the distinction between education and investment results. Avoid treating testimonials as representative evidence without understanding how they were selected and whether the claims can be substantiated.

A managed-portfolio service requires additional questions about custody, authority, reporting, fees, conflicts, and termination. Who owns the domains? Who can sell or transfer them? Are proceeds held separately under an appropriate arrangement? Can you obtain an exact inventory and independently confirm it? A manager’s dashboard should not be your only evidence that the assets exist and belong to you.

For material commitments, obtain independent advice suited to the arrangement. Do not rely only on the professional selected by the promoter, especially if that person is paid to validate the offering. Independence means having someone whose task is to evaluate your interests and the evidence, not merely to help complete the sale of the program.

Worked example: the guaranteed-flip package

A hypothetical beginner is offered fifty domains for a package price, with a promise that several will resell quickly for enough to cover the entire investment. The promoter shows automated valuations and selected success stories. After purchase, the beginner is told that access to serious buyers requires a paid premium membership, then a marketing upgrade, then individual appraisal certificates.

A careful pre-purchase review would have asked for the exact inventory, current renewal costs, verifiable completed-sale evidence, the operator’s role, and the full fee structure. It would also have distinguished a genuine brokerage engagement from a series of products sold to the investor. The repeated upgrades are not evidence that profitability is near; they may be the promoter’s actual business model.

The beginner should stop evaluating new fees as a way to justify earlier spending. Each expense needs an independent purpose and credible provider. A qualified broker may review a genuinely marketable premium asset, but should not be expected to turn a weak portfolio into guaranteed liquidity. Honest advice may include declining further purchases and reassessing the names already held.

Prefer a defensible thesis to a promise of certainty

A sound domain-investment decision explains why particular end users might value the name, what the investor can afford to hold, and what evidence would change the plan. It recognizes that acquisition quality, pricing, outreach, timing, and luck can affect outcomes. It does not need a guarantee to be rational, but it does need uncertainty to be visible.

Professional brokerage can be a valuable part of that strategy for suitable assets, especially when it improves buyer qualification and transaction execution. It is not a replacement for disciplined portfolio economics. The safest investor is not the one who never takes commercial risk. It is the one who knows which risks are being taken deliberately and refuses to confuse an attractive hypothetical resale price with money that a real end user has agreed to pay.

Back to the contents

Chapter 39: Choose and Verify the Right Escrow Arrangement

Escrow is most useful when it is selected for the actual transaction rather than invoked as a reassuring word. A buyer wants protection against paying without receiving the agreed asset. A seller wants protection against delivering without receiving the agreed consideration. A genuine provider can coordinate parts of that exchange under defined terms, but the parties still need to know what the provider holds, verifies, and releases—and what it does not.

Escrow.com’s published domain workflow describes an agreed transaction involving funding, transfer, inspection, and disbursement, while its concierge service adds a different level of domain-transfer involvement. ^{[10] [11]} These are examples of why service selection matters. Do not assume that every escrow product has the same custody sequence or that every provider accepts the same assets, jurisdictions, conditions, and payment methods.

Start with the exchange you need to control

Write down the asset, price, parties, and intended delivery route. Is the transaction a single domain, a portfolio, a domain with content, or a long-term payment arrangement? Does the buyer need immediate operational use? Are there transfer restrictions, corporate approvals, or multiple owners? The provider should understand these facts before anyone assumes that a standard workflow will fit.

Decide whether the service needs to hold money only, take temporary domain custody, assist with transfer, administer installments, or coordinate staged delivery. Some needs may require a different product or additional professional support. A provider’s willingness to process a payment should not be mistaken for agreement to administer every bespoke contractual condition.

Ask the broker to explain why the proposed arrangement suits the deal. A useful answer connects the service’s actual capabilities to the transaction’s risks. “We always use it” is not enough when the asset package or structure is unusual. Familiarity can improve execution, but only when the familiar process genuinely fits the current transaction.

Verify the real provider and its scope

Reach the provider independently and confirm its legal entity, service terms, and any relevant regulatory information. Escrow.com publishes jurisdiction-specific licensing and complaint information; other providers should be evaluated through their own authoritative records and the applicable regulatory framework. ^[38] A copied license number or logo on a lookalike site does not authenticate the site.

Confirm that the parties and transaction are eligible. Identity verification, company documentation, source-of-funds questions, and country or payment restrictions may affect timing. Address them early through the genuine provider. Do not disguise the transaction, use another person’s account, or split payments to evade a requirement. Such workarounds can create additional compliance and fraud exposure.

Read the fees and determine who pays them. Use current provider information rather than a fixed number from an old article. A legitimate fee should be visible in the agreed arrangement, not introduced through an unrelated last-minute payment demand. If the transaction changes materially, confirm whether the service and charges also change before proceeding.

Define the sequence without inventing a universal rule

In an ordinary arrangement where the seller delivers directly to the buyer after funding, the seller should rely on the genuine provider’s confirmed funding status and instructions before delivery. A screenshot from the buyer is not enough. The buyer, in turn, should not release funds merely because a transfer has been initiated if the agreed receipt and inspection conditions remain unsatisfied.

A verified neutral-custody or concierge service may use a different sequence, including coordinating receipt of the domain and funds according to its own authenticated instructions. Therefore, “never transfer anywhere until the buyer has paid” is too broad when applied to every service. The important distinction is between delivery to an unverified counterparty and placement into a genuine, agreed custody process whose terms you understand.

Write the actual sequence into the closing plan. Identify who confirms each event and which action follows. The plan should not ask one participant to infer another’s approval from silence or a casual message. Where the contract and provider workflow differ, resolve the mismatch before funding rather than expecting the provider to improvise at the critical moment.

Make inspection and acceptance meaningful

Agree what the buyer must verify after delivery and how long the applicable inspection period lasts under the selected service. Escrow.com explains that inspection periods and acceptance affect release under its process. ^[12] The buyer should understand the consequences of express acceptance, inaction, and any rejection or dispute procedure rather than assuming funds remain held indefinitely until every concern disappears.

For a domain-only purchase, inspection may focus on exact receipt, account control, and the agreed registration arrangement. For a website or portfolio, the scope can be more complex. Define the deliverables and any exceptions clearly enough that the provider and parties can identify whether the required event occurred. A vague promise of satisfaction is not a substitute for a workable acceptance standard.

Do not use the inspection period to postpone all due diligence. Seller authority, legal suitability, and major asset-scope questions should ordinarily be addressed before closing reaches delivery. Some problems cannot be resolved safely by trying to reverse a transfer afterward. Inspection is a final verification stage, not a reason to buy first and investigate the basic premise later.

Understand disputes, cancellations, and limits

Read what happens if the buyer rejects delivery, the seller cannot transfer, a third party asserts a claim, or either party stops responding. The provider’s terms may define procedures, deadlines, fees, and circumstances for holding or releasing funds. Ask questions before accepting the transaction. A dispute process is only useful if you know how to invoke it through the genuine service.

Do not assume that escrow guarantees clean title, future revenue, legal compliance, or recovery from every fraud. Those protections require their own analysis and, where available, specific contractual arrangements. The provider may verify identity for one purpose without investigating every ownership claim. A broker should make these boundaries understandable to the client.

Consider operational continuity as well. Temporary custody or a registrar move may interact with DNS, email, and security settings. Confirm what will remain unchanged and who handles technical issues. A financially well-structured exchange can still disrupt a business if the operational handover is ignored.

Worked example: the wrong service for a staged portfolio

A hypothetical buyer agrees to acquire a portfolio in three groups because the domains are held at different registrars and have different delivery constraints. The parties open one generic transaction with a single description and assume funds will be released proportionately as names arrive. The provider has not agreed to that allocation or received a clear schedule of values and conditions.

Before funding, the broker identifies the mismatch. The parties consult the provider and counsel, choose a supported structure, and define the asset groups, release events, and treatment of exceptions. The buyer knows what each payment covers, and the seller knows what evidence triggers the corresponding release. The revised process is safer because the provider is administering an arrangement it actually understands and supports.

In a simpler single-domain deal, the standard service may be entirely appropriate. The goal is not to buy the most elaborate product. It is to select the least complicated genuine arrangement that adequately addresses the transaction’s risks. A qualified broker can help make that judgment, but every client should still be able to explain where the money and domain will be at each stage and what verified event permits them to move next.

Back to the contents

Chapter 40: Bank Details, Beneficiary Verification, and Wire Fraud

The last payment instruction in a domain transaction can be more dangerous than the first offer. By closing day, the parties may have invested weeks in negotiation, exchanged convincing documents, and become accustomed to a particular email thread. That familiarity makes an unexpected bank-detail change feel like a minor administrative correction. Treat it instead as a new decision about where the money is going.

A sound purchase agreement does not authenticate a payment destination. A genuine broker can have an impersonator. A legitimate escrow provider can have its instructions copied and altered. Your objective is to connect the correct transaction to the correct beneficiary through a source you independently trust, then prevent that connection from being casually replaced.

Establish the payment route before closing pressure builds

Record who is supposed to receive the funds, in what capacity, through which verified service, and for which transaction. In an escrow arrangement, the initial recipient may be the escrow provider rather than the seller. Confirm that structure directly with the provider. Do not change the intended recipient merely because an email says paying the seller directly will save processing time.

Use the provider’s genuine account interface or another independently established channel to obtain current funding instructions. Preserve the transaction reference and any required payment identifiers. Have the payer check that the instructions belong to the correct transaction, currency, and service. A genuine destination for one purpose is not automatically appropriate for every other purpose.

Businesses should decide who prepares the payment and who independently approves it. The second person must review the destination and supporting evidence, not simply approve an amount already approved commercially. Price authorization and beneficiary authorization are different controls. Where a single owner handles everything, a deliberate pause and an independent verification step can provide some separation between preparation and execution.

Verify the beneficiary without inventing certainty

Ask your financial institution what beneficiary checks are available for the particular payment route and jurisdiction. Interpret the answer carefully. A name match, confirmation message, or successful small payment may answer a limited question; none establishes that the recipient has legal authority over the domain or that the underlying transaction is legitimate.

A mismatch deserves an explanation through the genuine provider or other appropriate independent channel. Some legitimate structures involve an escrow entity, a client-money account, a trading name, or an intermediary bank. Do not label every difference fraud. Equally, do not let a plausible explanation supplied by the person requesting the payment substitute for verification by the institution responsible for the account.

The FBI recommends independently verifying payment requests and changes to payment procedures, including through a known contact channel. ^[8]

Apply that principle before the bank transfer is authorized, not after someone has sent a reassuring screenshot.

A changed instruction resets the verification process

Define material changes broadly enough to cover a new bank account, beneficiary, country, currency, payment service, reference, or person authorizing the change. A request to split the amount between several recipients also changes the risk. Pause the affected payment and check the change against the transaction agreement and the provider’s genuine instructions.

Do not use the callback number supplied in the change request as your only source of verification. A reply within the same email chain does not create an independent channel either. Contact the provider or counterparty using details established before the change or obtained independently from an authenticated source. When the relationship itself is new, verify the institution before relying on any employee’s apparent confirmation.

A real operational problem can justify a revised payment route. It cannot justify skipping the verification process. If the provider cannot resolve the issue before a proposed deadline, revise the closing schedule rather than improvising a destination. The cost of a delay is visible; the cost of an unauthorized payment can be much harder to contain.

Keep payment evidence tied to the actual asset

The payment record should identify the exact domain or agreed portfolio schedule, transaction reference, payer, amount, currency, and date. For a multi-domain purchase, preserve the agreed allocation where it matters to staged delivery or refunds. Do not rely on a vague reference such as “consulting” when the actual transaction is a domain acquisition.

Accurate descriptions also protect the seller. A payment from an unexplained third party, especially one accompanied by instructions to send part elsewhere, needs review before delivery. The explanation might be legitimate, but the escrow provider and relevant advisers should understand and approve the arrangement where required. Do not become an informal payment intermediary for people whose role you cannot establish.

Keep bank details out of broadly shared deal summaries. The people coordinating technical transfer usually do not need full payment information. Limit access to those responsible for the transaction and preserve a controlled record. If instructions are transmitted securely, confirm that the secure channel itself is genuine rather than assuming that a password-protected document is trustworthy.

Respond to suspected diversion immediately

If money may have gone to the wrong recipient, contact the sending financial institution’s fraud team immediately through an independently verified channel. Explain the suspected diversion and ask what urgent recall, cancellation, tracing, or recipient-bank contact is possible. The FBI specifically advises immediate bank contact in a business email compromise incident. Recovery is not assured. ^[8]

At the same time, notify the genuine escrow provider, broker, and appropriate internal decision-maker that funding may be compromised. Stop further payments and avoid releasing a domain on the strength of the disputed transfer. Preserve the original messages, payment instructions, transaction identifiers, timestamps, and records of calls. Do not spend the first response period arguing with the apparent sender.

Check whether email or account compromise is continuing. An attacker who diverted one payment may be reading the response and offering a second “corrected” destination. Use a secure, independently verified communication route while the incident is investigated. Chapter 67 provides a broader containment sequence, including reporting and evidence organization.

Worked example: the convenient replacement account

A hypothetical buyer has agreed to acquire a premium domain through a genuine escrow service. The seller’s broker and buyer have exchanged documents for several weeks. On the scheduled funding day, an email in the familiar thread says the provider’s usual receiving account is undergoing maintenance and supplies a replacement account. The message includes the correct price, domain, and transaction reference.

The buyer’s finance lead refuses to treat those details as authentication. She signs into the provider through a saved, verified address and contacts support using the established channel. The genuine provider confirms that the transaction’s funding instructions have not changed. The team preserves the suspicious message, alerts the broker, and investigates how the attacker obtained the deal details.

The important control was not exceptional talent at spotting forged email. The message was convincing. The control was a rule that changed payment destinations require independent verification by the party responsible for receiving the money. The buyer’s process remained effective even when the attacker knew nearly everything about the transaction except how to satisfy that independent check.

A qualified broker should welcome this discipline and help establish it early. Brokerage is especially valuable when several institutions, currencies, or corporate participants make payment coordination harder. The broker’s role is to reduce ambiguity and keep the agreed process intact—not to ask the client to trust a bank instruction merely because it arrived under a familiar name.

Back to the contents

Chapter 41: Fake Payment Confirmations, Reversals, and Chargeback Exposure

A payment can appear convincing long before it satisfies the conditions for delivering a domain. An email may say money was sent. A screenshot may show a debit. An account may display a pending balance. A provider may acknowledge receipt while still completing checks. These are different states, and a seller should not collapse them into the single reassuring word “paid.”

The central question is not whether a buyer can produce something resembling payment evidence. It is whether the genuine institution administering the transaction confirms that the agreed delivery condition has been met, under the actual service terms. Even then, understand what risks remain rather than inventing a universal concept of irreversible money.

Define the release condition before selecting a payment method

Before accepting an offer, decide how payment will be handled and what event authorizes transfer. For an escrow transaction, follow the verified provider’s instructions for the selected product. For another arrangement, obtain appropriate advice about funding status, disputes, fraud exposure, and the evidence needed to establish delivery. A payment method that is convenient for a routine purchase may not fit a valuable, transferable digital asset.

Ask practical questions. Who bears an unauthorized-payment loss? What transactions are eligible for any seller or buyer protection? What evidence is required? What deadlines apply to a dispute? Can the service handle the amount, countries, and asset involved? Seek current answers from the actual provider rather than relying on an old forum post or another seller’s experience.

Do not assume that a protection program covers domains simply because it covers some online purchases. Do not assume the opposite without checking either. Eligibility can depend on the product, account type, transaction structure, jurisdiction, and compliance with the provider’s conditions. The useful conclusion is specific: this transaction is or is not covered under these identified terms.

Authenticate payment status at its source

Use your own verified account access to inspect the transaction. Do not follow a buyer-supplied login link to “release” funds. A notification should lead you to verify an event, not become the sole proof that the event occurred. If the genuine dashboard and the email disagree, stop and resolve the discrepancy with the real provider.

A buyer’s banking screenshot cannot establish what your escrow provider has received. A transfer reference may help an institution locate a payment, but it does not replace confirmation from the recipient. Likewise, a document headed “irrevocable guarantee” needs examination of its issuer, terms, and authenticity. Impressive language cannot supply missing institutional verification.

Be particularly cautious when the message says payment is complete but requires you to pay an account-upgrade fee, send a refund, or transfer the domain before the balance becomes visible. Resolve the purported requirement through the genuine service. Do not fund an unfamiliar account to unlock a payment whose existence has not been independently confirmed.

Available funds are not a universal finality test

The FTC warns that funds from a deposited fake check can appear available before the fraud is discovered, leaving the recipient responsible for money sent onward. A visible balance therefore does not establish that a check is genuine. ^[37]

Avoid converting that warning into an invented waiting rule. “Wait three days,” “wait a week,” or “cashier’s checks are always safe” is not a reliable transaction policy without institution-specific support. Ask your bank about the actual instrument and risk, and consider whether a different closing structure is more appropriate. A stranger’s overpayment is not an opportunity to earn a small inconvenience fee.

Other methods have their own rules. A successful payment notification does not tell you every fact about authorization, disputes, compliance review, or contractual recourse. Conversely, describing every payment as equally unsafe is unhelpful. The task is to choose a method whose documented protections and limitations fit the deal, then follow its required sequence.

Preserve delivery evidence without treating it as immunity

For a seller, evidence should show what was sold, who agreed to buy it, which account or registrar received it, and when the agreed delivery event occurred. Keep the signed agreement, exact asset schedule, provider instructions, transfer confirmations, and relevant acceptance records. These materials may be important if a payment or delivery dispute arises.

Do not fabricate or embellish evidence to strengthen a case. Record what the genuine systems show and distinguish a completed registrar transfer from a website becoming reachable. A live website does not by itself identify who controls the registration. A screenshot of a dashboard may be supplementary, but the provider’s underlying transaction records are usually the better starting point for a factual account.

No evidence package guarantees success in every dispute. A legitimate buyer may have a valid complaint, and a provider may apply conditions the seller did not meet. Good records support an honest explanation; they do not override the agreement or applicable rules. This is another reason to understand the service before the sale rather than learning its requirements after a challenge.

Handle refunds and payment disputes through the original process

If a payment problem arises, communicate through the genuine provider and follow its documented procedures. Do not send a separate refund to a new account merely because the buyer says the original method is unavailable. A separate outward payment can create a second loss while the original transaction is still disputed or reversed.

For an authentic cancellation, document what happens to both the money and the domain. A refund without verified return of the asset can leave the seller exposed; a returned asset without an agreed refund process can leave the buyer exposed. Use supported escrow procedures or a carefully reviewed arrangement rather than relying on reciprocal promises made under pressure.

A chargeback or complaint is not automatically evidence of fraud. Investigate the asserted issue, preserve records, and respond accurately within the relevant process. Avoid threats designed to silence a genuine complaint. Where facts suggest deliberate deception, report those facts through the appropriate channels without turning the response into an unsupported public accusation.

Worked example: a screenshot replaces the closing condition

A hypothetical seller receives an attractive offer and agrees to use escrow. The buyer then sends an image showing a large payment and explains that the escrow interface is slow to update. A second message says the buyer’s launch team needs the domain immediately and offers an additional bonus if the seller sends the authorization code before the end of the hour.

The seller checks the genuine transaction and sees that the provider has not authorized delivery. Instead of debating whether the screenshot looks real, the seller states that transfer will occur when the verified provider confirms the agreed condition. The bonus does not change the response. The buyer’s claimed urgency concerns the buyer’s schedule; it does not establish that funding has occurred.

In a legitimate payment delay, this approach may simply produce a later closing. In a fraudulent attempt, it prevents a screenshot from becoming a substitute for money. The same control works in both situations because it is based on the transaction’s agreed evidence, not on guessing the sender’s motives.

A seller’s broker can add value by setting these expectations before an offer is accepted, coordinating with the provider, and resisting pressure to improvise. The best brokerage process makes the payment condition explicit enough that nobody has to decide, at the most stressful moment, whether a persuasive message should override it.

Back to the contents

Chapter 42: Cryptocurrency Payments Without Magical Thinking

Cryptocurrency does not remove the ordinary questions in a domain transaction. The buyer still needs the correct asset from a person entitled to sell it. The seller still needs the agreed payment under a workable closing arrangement. Both parties still need authenticated instructions, clear terms, and a reliable method of resolving exceptions. Changing the payment technology does not answer those questions automatically.

Nor does cryptocurrency make every transaction a scam. The relevant issue is whether the proposed method is understood, lawfully usable, supported by the chosen providers, and appropriate for the participants. A buyer who cannot explain the asset, network, destination, and confirmation process should not let a seller’s confidence stand in for that understanding.

Separate payment technology from transaction trust

Treat a request for cryptocurrency as a proposal that requires evaluation, not as proof of sophistication. Ask why the method is being used and what protections the arrangement provides. A demand to abandon verified escrow, conceal the payment, or act immediately because traditional safeguards are supposedly obsolete is a reason to stop and reassess.

The FTC notes that cryptocurrency payments typically lack the reversal mechanisms people associate with conventional consumer payment disputes. It also advises reporting suspected fraud to the service used to send the funds and appropriate authorities. Those limitations make preventive verification especially important. ^[52]

Do not accept a supposed technical guarantee that a payment method proves the domain’s title. A blockchain record can concern movement of a token or cryptocurrency; it does not, by itself, establish a seller’s authority to transfer an ordinary DNS registration. Chapter 37 explains the separate issue of blockchain naming and tokenized claims. Payment in cryptocurrency does not turn a conventional domain into a different legal asset.

Write down exactly what payment means

The agreement should identify the currency or token, supported network, amount or conversion rule, relevant timing, fees, and the event that counts as payment for closing purposes. Where a price is negotiated in fiat currency but paid in cryptocurrency, avoid leaving the exchange-rate decision to an informal message at the last moment.

Confirm who bears any conversion cost or value movement during the agreed process. Decide how an underpayment, overpayment, delayed transaction, unsupported asset, or mistaken network will be handled. These are matters to settle with the actual service providers and appropriate advisers, not assumptions to improvise after funds have moved.

A token described as stable should not be treated as eliminating every financial or operational risk. Ask what the provider actually accepts and credits, whether conversion is required, and what happens if the intended transaction cannot proceed. The useful question is not whether a label sounds reassuring. It is whether the selected asset can be used safely within the specific closing arrangement.

Authenticate addresses and instructions through a controlled process

Obtain payment instructions through the genuine provider or independently verified counterparty channel. Check the complete destination and the required network using the provider’s supported procedure. Do not rely only on the first and last few visible characters of an address, a QR code in an email, or a destination copied from an old conversation.

A change to the destination, token, network, or payment route should trigger the same pause as a changed bank account. Reverify it independently and confirm that the contract and service still support the revised arrangement. An instruction to use a new wallet because the usual one is “under review” is not self-authenticating.

A small test transaction may be useful in some supported workflows, but it is not proof of the recipient’s identity, honesty, or authority over the domain. It also does not authorize a later destination change. Use any test only as one technical check within a verified process, not as a substitute for the broader transaction review.

Keep wallet security separate from the buyer–seller conversation

Never disclose a wallet seed phrase, private key, or recovery secret to a buyer, seller, broker, or supposed support representative. A counterparty does not need your recovery material to pay you. A request to enter it into a transaction-verification page should stop the process immediately.

Do not connect a wallet or approve an unfamiliar transaction merely to prove that you are a serious buyer. Ask what the action authorizes and obtain competent technical assistance where necessary. Reading a reassuring label in a website interface is not the same as understanding the permission being granted. For a conventional domain purchase, unrelated wallet permissions should receive particularly skeptical scrutiny.

Use an environment and account arrangement suitable for the transaction’s value. Keep unrelated holdings and business systems outside the deal’s access path where practical. The aim is to limit the consequences of one mistake. A domain negotiation should not expose an entire financial portfolio because someone requested a convenient all-purpose connection.

Use supported custody and document the handover

Before naming an escrow provider in the contract, confirm that it supports the intended cryptocurrency arrangement for your transaction. Do not infer support from an old announcement, a search result, or a third party’s claim. Verify the genuine service, eligible parties, current terms, and exact funding instructions directly.

If a specialist intermediary handles conversion or custody, identify that entity’s role and limitations. Determine which institution confirms funding and which one authorizes domain delivery. Avoid a structure in which each participant assumes someone else has checked payment. A broker can coordinate these responsibilities, but the client should still understand the basic path of both assets.

Keep records of the agreed terms, authenticated instructions, relevant transaction identifiers, provider acknowledgments, and domain delivery. Store them securely and do not publish wallet information unnecessarily. Technical transparency does not require turning a confidential acquisition into a public record assembled for everyone who asks.

Worked example: the unsupported last-minute switch

A hypothetical buyer and seller agree on a conventional escrow closing for a premium domain. After the agreement is signed, the seller proposes payment in a particular token, claiming that the change will remove all banking delays. The seller supplies a wallet address and says the domain will be pushed immediately after the buyer sends the funds.

The buyer does not treat the token as inherently illegitimate. Instead, the buyer asks whether the genuine escrow provider supports that asset and process. The provider confirms that the proposed direct payment is outside the selected service. The buyer’s broker explains that the switch would replace the agreed protection with an unsupported promise and advises retaining the original arrangement unless a properly reviewed alternative is established.

The seller can accept the original process, help develop a supported alternative, or decline the transaction. What the seller cannot reasonably expect is an unexamined change simply because it sounds faster. The buyer’s decision remains grounded in responsibilities, verification, and enforceable terms rather than enthusiasm or hostility toward a technology.

If cryptocurrency has already been sent to a suspected scammer, preserve the destination, transaction identifier, dates, messages, and provider records, and contact the relevant service promptly. Do not send another payment to a stranger claiming that a recovery fee will reverse the first one. Chapter 70 addresses that second-stage trap. The safer principle throughout is simple: sophisticated payment technology requires disciplined transaction controls, not less of them.

Back to the contents

Chapter 43: The Domain Purchase Agreement: Terms That Matter

A domain purchase agreement should turn a negotiated intention into a transaction people can execute and verify. Its value is not measured by how many pages it contains or how intimidating the language sounds. The useful test is whether the parties can identify the asset, their obligations, the conditions for delivery and payment, and the process for handling a problem.

This chapter is an issue-spotting guide, not a universal contract form. The appropriate wording and legal effect depend on the transaction and applicable law. For a material purchase or sale, have a qualified lawyer review the agreement. A broker can organize the commercial terms and closing process, but legal drafting and advice require their own responsibility.

Identify the parties and the asset precisely

Use the correct legal names of the buyer and seller, with sufficient identifying information to distinguish them from similarly named people or entities. Identify the signers and the capacity in which they act. Where an acquisition vehicle, agent, estate, or corporate group is involved, resolve who is actually contracting and who will become the registrant before the closing documents are finalized.

State the exact domain name in plain text. For a portfolio, attach an agreed schedule of unique names and define how corrections are approved. For an internationalized domain, use an unambiguous representation appropriate to the registry and transaction. Do not let a marketing presentation or email subject line become the only description of the asset.

Explain what is included and excluded. A domain-only sale should not silently imply transfer of a website, trademark, software, customer database, social account, or email archive. A broader acquisition needs a corresponding asset schedule and review of rights, permissions, and delivery requirements. The simplest way to prevent an argument about missing assets is to identify the boundaries while the parties are still negotiating.

Convert the price into an executable payment obligation

Specify the amount, currency, fees, taxes where applicable, deposit treatment, and payment route. State whether a deposit is refundable and under what conditions, rather than relying on the label alone. If installments, holdbacks, or staged portfolio deliveries are intended, the agreement and the selected provider’s service must support the same structure.

Name the genuine escrow or other closing service and identify the relevant product. Clarify how its terms interact with the purchase agreement. A private contract between buyer and seller cannot be assumed to make a provider administer unsupported conditions. Ask the provider about unusual release events, split payments, or dispute arrangements before accepting them.

Include a controlled procedure for changing payment instructions. The contract need not contain every sensitive bank detail in a widely circulated copy, but it should not leave changes to casual email. Define the authorized decision-makers and the independent verification required for a revised destination. The commercial obligation to pay should be separated from the practical process of authenticating where payment goes.

Address authority, claims, and the limits of promises

Discuss appropriate seller representations concerning authority to sell, existing agreements, known claims, and the accuracy of material information. Tailor them to the facts. A seller should not casually promise facts beyond its knowledge, and a buyer should not assume that a broad sentence replaces due diligence. The lawyer’s job includes explaining the scope and consequences of the proposed wording.

Consider whether there are existing leases, options, liens, security interests, marketplace commitments, or third-party rights that require disclosure or release. These issues may not be visible in a registrar dashboard. Ask for the evidence appropriate to any identified arrangement, and establish what must be resolved before closing.

A warranty is not the same as practical recoverability. The ability to enforce a promise may depend on the counterparty, jurisdiction, evidence, resources, and available remedies. A buyer who ignores a serious ownership warning because the contract contains a warranty may still face an expensive dispute. Prevention and enforceable promises should support one another, not substitute for one another.

Define delivery, inspection, and acceptance objectively

Describe the intended transfer method and receiving arrangement. Is the domain moving to a different registrar, being pushed to another account, or entering neutral custody? Who provides account identifiers, who authorizes each step, and what evidence establishes completion? Avoid a definition of delivery that depends solely on one party saying the transaction is finished.

State what the buyer is entitled to inspect and how acceptance or rejection must be communicated. For a domain-only transaction, the acceptance criteria should match the promised registration rights and control. For a website acquisition, additional deliverables require separate criteria. Do not make the inspection clause so vague that a provider cannot determine whether the required notice has been given.

Address timing without creating an incentive to bypass controls. Specify relevant time zones, business-day assumptions where needed, and a process for genuine provider delays. A deadline should identify when obligations arise and when a party may exercise agreed rights; it should not force the transfer of a valuable asset before a funding or authority issue has been resolved.

Plan for exceptions before they become accusations

Discuss what happens if the seller cannot deliver, the buyer cannot fund, a transfer lock intervenes, an ownership claim emerges, or a provider declines the transaction. Identify notice requirements, cure opportunities where appropriate, cancellation consequences, and the handling of fees or deposits. Counsel should tailor these provisions rather than copying a clause from an unrelated sale.

Confidentiality, publicity, data handling, and transition support may also matter. A seller may want a confidential price; a buyer may need to announce a rebrand after closing. Make those expectations explicit. Do not promise confidentiality on behalf of institutions whose own legal or regulatory obligations you do not control.

Consider governing law, dispute resolution, service of notices, and the relationship between the contract and provider procedures. These provisions are not decorative boilerplate when parties are in different countries. The question is how a real disagreement would be handled, by whom, and at what practical cost. A lawyer familiar with the relevant jurisdictions can identify issues a broker should not attempt to resolve alone.

Worked example: a domain-only sale with website assumptions

A hypothetical buyer agrees to pay a substantial price for a domain that currently hosts a small information site. The seller understands the deal as a registration-only sale. The buyer assumes that the site’s articles, logo, mailing list, and analytics history will accompany the domain because they appeared in a sales presentation. A short agreement refers only to “the digital property.”

During review, the broker asks both sides to describe the expected delivery. The mismatch becomes obvious before funding. The parties either limit the transaction to the domain and revise the buyer’s valuation, or negotiate a broader asset purchase with legal and technical review. In either case, the final agreement describes what is actually changing hands.

This is not necessarily an attempted scam. It is a gap that could have become a serious dispute or provided cover for deception. Precise drafting makes the gap visible. A well-managed process does not wait for a court or escrow dispute to discover that the parties had different ideas about the product.

Before signing, read the agreement as an operating instruction as well as a legal document. Ask a simple question at each stage: what evidence permits the next consequential action? When the answer is unclear, resolve it. The strongest domain transactions combine a verified counterparty, appropriate legal terms, a supported payment arrangement, and a broker capable of keeping those pieces aligned.

Back to the contents

Chapter 44: Conditions, Approvals, and the Closing Responsibility Map

Many failed closings do not begin with an obviously dishonest participant. They begin with an assumption that someone else has checked a critical detail. The buyer believes the broker verified ownership. The broker believes counsel resolved authority. Counsel believes the escrow provider approved the payment structure. The provider is waiting for instructions nobody realized it needed.

A closing responsibility map removes those gaps. It identifies the important decisions, the person responsible for each, the evidence required, and the conditions that must be satisfied before action. The map should be short enough to use under pressure but specific enough that a new participant can understand what is happening without reconstructing a month of emails.

Distinguish a commercial agreement from permission to close

An accepted price is not the same as a completed verification process. The parties may agree commercially while legal review, identity checks, transfer preparation, or provider onboarding remain incomplete. Record those open items explicitly. Otherwise, enthusiasm about “having a deal” can be mistaken for authorization to send money or release the domain.

Use clear status descriptions. “Price agreed, subject to signed terms and verification” communicates more than “done.” “Funding confirmed by the provider; transfer awaiting authorized approval” is more useful than “payment sorted.” The purpose is not bureaucracy. It is to prevent a conversational shortcut from creating a consequential misunderstanding.

Separate conditions that protect the transaction from preferences that can be negotiated. An unresolved seller-authority issue is not equivalent to a preference for a different meeting time. Critical conditions should not be traded away casually to preserve momentum. Identify who has authority to waive a condition, whether it can lawfully be waived, and what advice is required before doing so.

Assign one accountable owner to each important question

For seller authority, name the person coordinating the evidence and the adviser assessing any legal issue. For funding, identify the genuine provider whose status controls the next step. For transfer execution, name the authorized account holder or technical operator. For inspection, identify the buyer representative who will verify the agreed deliverables.

A broker may coordinate several of these tasks without being the final decision-maker for all of them. Make that distinction visible. “Broker obtains documents; counsel reviews authority; buyer approves proceeding” is a clearer arrangement than “broker handles everything.” The same applies to the seller’s side and to any neutral custodian.

Identify backups before a participant becomes unavailable. A backup should have a defined role and an independently verified identity, not appear for the first time in a closing-day message. Establish how substitutions are approved. The replacement of a payment approver, signer, or receiving-account contact should not be treated as an ordinary scheduling matter.

Build the sequence around dependencies

Some tasks can run in parallel; others depend on a verified prior event. Buyer identity checks and technical preparation may proceed at the same time. Direct delivery to a buyer should follow the applicable funding and closing conditions. Neutral-custody services may have a different supported intake sequence, so the map must reflect the actual product rather than a generic slogan.

Write down the path of the money and the domain separately. At each stage, ask who controls the asset, who can authorize movement, and what happens if the transaction stops. This exercise often exposes an unsupported assumption. For example, a planned refund may depend on a domain being returned, but nobody has defined who verifies that return.

Include operational dependencies such as renewal, email access, DNS hosting, and account eligibility. A domain that cannot move on the expected date may still be deliverable through another approved arrangement, but that alternative must be reviewed. Do not improvise a new custody structure merely because the original schedule has become inconvenient.

Use a closing sheet, not an uncontrolled collection of messages

Maintain a current closing sheet with the exact domain, parties, transaction reference, selected service, transfer method, outstanding conditions, responsible contacts, and approved timeline. Sensitive information should be limited to appropriate recipients. The sheet can reference secure records rather than copying identity documents or full banking instructions into every version.

Give the document a clear version or date. When a material item changes, identify what changed and who approved it. Retain prior versions where appropriate for the transaction record. A quiet replacement of an attachment should not be enough to alter the beneficiary or receiving account.

Keep the closing sheet consistent with the signed agreement and genuine provider instructions. It is an operational summary, not a hidden amendment mechanism. If the summary conflicts with the contract, stop and resolve the conflict with the relevant advisers. Convenience should not create two competing versions of the deal.

Establish a stop rule and an exception process

Every participant should know how to report a concern without being pressured to solve it alone. A stop rule might cover an unexpected payment change, a newly asserted ownership claim, a wrong-domain discrepancy, or a provider instruction that cannot be authenticated. The rule should identify who is notified and what actions remain permitted while the concern is reviewed.

Stopping does not mean accusing everyone of fraud or abandoning the deal permanently. It means preserving the current safe position until the uncertainty is resolved. A genuine operational error can then be corrected without converting it into a financial loss. A fraudulent intervention loses its main advantage: the expectation that nobody will interrupt a transaction already in motion.

For each exception, record the issue, evidence, responsible reviewer, decision, and any revised condition. Avoid verbal waivers that nobody can reconstruct later. Where legal rights or provider obligations are affected, obtain the appropriate written amendment or confirmation. The complexity of the response should match the consequence of the change.

Worked example: the unassigned acceptance decision

A hypothetical company buys a premium domain through a broker and escrow. The finance team confirms funding, the technical team receives the domain, and the marketing team begins planning a launch. Everyone assumes someone else will check the registrant details and submit acceptance. The inspection deadline approaches while a minor account-control issue remains unresolved.

A closing responsibility map would have assigned one buyer representative to confirm the exact asset, account security, registration details, and provider acceptance procedure. It would also have identified the deadline and escalation route. Without that map, several competent people can each complete their own task while the transaction as a whole remains unfinished.

The broker notices the gap, brings the responsible people together, and coordinates a factual status review through the genuine provider. The team resolves the account issue and records acceptance according to the applicable terms. The lesson is not that every closing requires a large committee. It is that every critical decision needs an owner.

For an individual buyer or seller, the map can fit on a single page. For a complex corporate acquisition, it may be a more detailed schedule. In both cases, its purpose is the same: to make responsibility visible before money and registration rights move. Good brokerage adds value by maintaining that visibility and keeping commercial enthusiasm from outrunning verified readiness.

Back to the contents

Chapter 45: Registrar Transfers and Safe Handling of Authorization Codes

A registrar transfer changes the registrar responsible for a domain registration. It is not automatically the same as changing the registrant, moving a website, transferring email, or completing a sale. Those events can be coordinated, but they require separate attention. A scammer benefits when the seller treats one technical step as harmless administration while it actually enables control to move.

Before discussing an authorization code, establish the exact domain, the legitimate transaction, the chosen transfer route, and the condition that permits the step. Technical fluency should follow commercial and identity verification, not replace it. Someone who knows the correct jargon may still be an unauthorized buyer, fake broker, or impersonated support agent.

Understand what the code does—and does not prove

An authorization code, often called an Auth-Code, AuthInfo code, or EPP code, is used in the transfer process for relevant domain registrations. ICANN describes it as a credential involved in moving a domain between registrars. Treat it as sensitive transfer information, not as a harmless ownership certificate. ^[29]

A request to see the code merely to verify that you own the domain is inappropriate for ordinary buyer due diligence. Use a safer, agreed verification method that does not expose a transfer secret. The fact that a person can supply a code also does not establish lawful title or corporate authority. A compromised account may give an attacker access to technically valid credentials.

Do not publish codes in a sales listing, shared spreadsheet, public support forum, or broad email chain. Limit access to the verified participants who need them under the supported closing process. For a portfolio, avoid distributing a complete set when only a particular stage is ready for delivery.

Confirm eligibility with the actual registrars

Ask the current and intended registrar about the domain’s present transfer eligibility, status, and required steps. ICANN’s transfer framework applies to covered registrations, while provider procedures and extension-specific rules still matter. Do not assume that instructions for one top-level domain or registrar account will work unchanged for another. ^[14]

Check for restrictions early, before agreeing to an unrealistic delivery date. Relevant questions include recent registration or transfer activity, changes to registrant information, disputes, account security restrictions, and the current registration state. A lock can be a normal security or policy condition; it is not proof that the seller is fraudulent.

Where a restriction exists, identify its basis and the lawful options. The answer may be to wait, use a supported same-registrar arrangement, or restructure the closing with professional advice. The answer should not be to conceal the problem, falsify account information, or accept a stranger’s paid “unlocking” service.

Prepare the destination before exposing transfer credentials

The buyer should establish the intended receiving account through the genuine registrar and secure it appropriately. Confirm the account identifier and the person authorized to receive the domain. A wrong account number or substituted email address can redirect an otherwise legitimate handover. Verify these details through the agreed communication process.

Determine what registration information must be supplied and how the buyer will confirm it. Plan for any legitimate notices or approvals required by the providers. Do not disable account security broadly because a counterparty says it will make the transfer easier. Follow the registrar’s documented process and ask support to explain any step that appears to require excessive access.

For business-critical domains, coordinate the registration move with DNS and email planning. A registrar transfer is not a reason to make unnecessary technical changes at the same time. Chapter 48 addresses continuity in more detail. The closing plan should say what remains unchanged and who is responsible if a dependency behaves differently than expected.

Release and use the code only within the agreed sequence

For a standard escrow closing, wait for the genuine provider’s applicable delivery instruction before transmitting credentials or initiating delivery to the buyer. For a neutral-custody service, follow its supported intake process, which may differ. The important point is to act within an authenticated arrangement whose custody and payment conditions you understand.

Send sensitive transfer information through the provider-supported secure channel or another appropriately controlled method agreed by the verified parties. Confirm that the recipient is the intended participant. Avoid forwarding the entire transaction history merely to deliver a code; it may expose unnecessary personal, financial, or operational information.

Monitor genuine registrar notices. If a message describes a different domain, receiving registrar, or action from the one expected, stop and contact the real provider. Do not approve an unexpected transfer because the buyer says the discrepancy is cosmetic. The exact transaction should remain consistent from the agreement through the provider’s records.

Verify completion and close the temporary exposure

After the move, confirm the exact domain at the intended registrar and account, the appropriate registrant arrangement, and the buyer’s ability to manage the registration. Public lookup information can supplement that review, but it may not display all details. Use the genuine registrar’s account records and support where necessary.

Restore or confirm appropriate security settings once the transfer stage is complete. Review temporary permissions and remove access that is no longer needed. Ask the registrar how to invalidate or rotate exposed transfer credentials where applicable, especially if a code was shared with the wrong recipient or the transaction was canceled.

Keep the transfer confirmation and relevant timestamps with the deal record. Do not mistake completion of the registrar move for completion of every contractual obligation. Inspection, acceptance, fund release, renewal responsibility, and any transition services may still require action. The closing sheet should identify those remaining tasks.

Worked example: a code requested before buyer verification

A hypothetical seller receives a strong offer for a short domain. The apparent buyer says its compliance department needs the authorization code before opening escrow, supposedly to confirm that the name is transferable. The buyer offers to sign a confidentiality statement and promises not to use the code without permission.

The seller declines to share the credential at that stage and offers non-secret evidence appropriate to the legitimate due-diligence question. The seller also asks the genuine registrar about current transfer eligibility. The buyer can verify the relevant facts without obtaining a secret that enables a transfer request. A confidentiality promise does not change the function of the code.

If the requester is legitimate but inexperienced, the explanation may correct the process. If the requester is malicious, the refusal blocks an unnecessary exposure. Either outcome is better than relying on a promise about how a powerful credential will be used.

A qualified domain broker should understand this distinction instinctively: evidence of a saleable asset is not the same as permission to move it. The broker’s contribution is to sequence due diligence, funding, credentials, approvals, and receipt so that no participant is asked to surrender control merely to demonstrate good faith. A clean technical transfer is the result of a well-defined transaction, not a substitute for one.

Back to the contents

Chapter 46: Account Pushes, Account Handover, and Neutral Custody

Not every domain sale requires an immediate move to a different registrar. Some transactions use a provider-supported change between accounts at the same registrar, often called an account push. Others use a neutral custodian that receives the domain as part of an agreed closing service. These structures can be useful, but they are not interchangeable and should not be described simply as “giving the buyer access.”

The distinction matters because access can be temporary, shared, excessive, or revocable. A buyer needs the agreed registration rights and control, not merely a password that happens to work today. A seller needs a documented delivery process, not an informal account handover that exposes unrelated assets and personal information.

Use the registrar’s supported account-change process

Ask the genuine registrar how it handles a change between accounts for the particular domain and circumstances. Confirm what changes, what does not, which approvals are required, and whether any restrictions affect a later move to another registrar. Do not assume that an account push bypasses all locks or policy conditions.

The receiving account should belong to the intended buyer or an expressly agreed custodian. Verify the account identifier through the established transaction channel. A buyer’s display name is not enough if the provider requires a specific account number or email address. Small administrative errors can have large consequences when they determine where the domain goes.

Confirm whether the process updates registrant information or requires a separate step. The buyer should understand the registration agreement it is entering and any verification obligations that follow. The seller should preserve the provider’s confirmation of the completed action. The goal is a supported change of control, not an ambiguous transfer of login credentials.

Do not substitute a whole-account password exchange

A request to buy or receive an entire registrar account deserves careful scrutiny. The account may contain other domains, saved payment methods, identity documents, support history, recovery settings, API credentials, or services not included in the sale. Handing over a password can expose far more than the negotiated asset.

It can also leave the buyer with an insecure arrangement. The former holder may retain recovery access, active sessions, linked authentication methods, or provider-recognized account history. The fact that the buyer changed the password does not prove that every route of access has been removed. Provider terms may also restrict or govern account transfers, so check rather than assume permission.

Prefer a registrar-supported domain transfer or account-change process that places the asset into the correct receiving arrangement. Where a whole-account transfer is genuinely part of a larger transaction, obtain the provider’s approval and appropriate legal and technical review. Treat it as a distinct asset and security problem, not a shortcut around normal procedures.

Understand what neutral custody actually provides

A genuine domain concierge or custody service may receive the domain into an account it controls and coordinate the exchange with the parties. Escrow.com describes a Domain Concierge service that adds domain-handling assistance and control to its transaction process. The precise sequence and scope should be confirmed for the selected service. ^[11]

Neutral custody can reduce the direct trust required between buyer and seller, but only if the custodian is authentic and the terms are clear. Verify who operates the account, what event permits release, what happens if the deal fails, and how disputes are handled. A website calling itself an escrow custodian does not establish any of these facts.

Do not assume that custody includes a legal opinion on title, a technical migration service, or protection against every future claim. Ask which risks the service actually addresses. A broker should explain why the selected arrangement fits the transaction rather than treating the word “concierge” as a complete risk assessment.

Coordinate custody with funding and inspection

The sequence depends on the product. In some genuine neutral-custody arrangements, domain intake and funding preparation can be coordinated rather than following the same direct buyer-delivery sequence used in a standard transaction. Follow authenticated provider instructions and understand the protections at each stage. A blanket rule copied from another service may be inaccurate.

Before sending the domain into custody, confirm the exact receiving account through the genuine provider and verify that the transaction is active under the agreed terms. Ask what records establish the custodian’s receipt and what conditions govern return if closing does not occur. The seller should not rely solely on an email from the buyer identifying a supposedly neutral account.

Before funds are released, confirm that the agreed delivery and acceptance conditions have been met through the provider’s process. If the domain will remain with the custodian during installments or another extended arrangement, define renewal, DNS control, default, and exit responsibilities. Temporary closing custody and long-term holding are different products with different operational consequences.

Limit access during technical assistance

A broker or technical adviser may help coordinate a push without needing the seller’s master password. Use the provider’s supported delegation or guided process where appropriate. Keep sensitive credentials and unrelated assets outside the adviser’s access unless a specific, justified arrangement requires otherwise.

If screen sharing is used for legitimate assistance, avoid exposing passwords, recovery codes, payment data, or other domains unnecessarily. Do not give remote control to a newly introduced participant just because the person claims to be closing support. Verify the representative and the scope of the session before allowing consequential actions.

After completion, review temporary access and revoke what is no longer required. Confirm that the buyer controls the intended account and recovery channels, and that the seller has removed sold assets from listings and internal inventories. A transfer is not operationally complete while both parties still believe they are responsible for the same renewal or sale authorization.

Worked example: a convenient account containing unrelated assets

A hypothetical seller owns a valuable domain alongside several personal names in one registrar account. The buyer proposes taking over the entire account because an inter-registrar transfer cannot occur immediately. The buyer offers to change the password and promises not to inspect anything else. The seller considers this easier than discussing the registrar’s supported alternatives.

The broker identifies the unnecessary exposure and contacts the genuine registrar. A supported receiving-account process is available for the domain under the relevant conditions, and the buyer can secure its own account. The parties document the method, confirm any later transfer restrictions, and complete the sale through the agreed payment arrangement without sharing the seller’s master account.

In another transaction, a neutral custody service might be the better solution. The key is not that one method is always superior. It is that the selected method clearly identifies the controller, preserves unrelated assets, and provides evidence of the agreed delivery. Convenience is useful only when it does not create a hidden ownership or security problem.

A well-qualified broker helps choose between these structures and coordinates the genuine providers. The client should be able to answer three questions afterward: who controls the domain now, under what agreement, and what verified event allows it to move next? If those answers remain vague, the transaction needs clarification before anyone hands over an account or a domain.

Back to the contents

Chapter 47: Transfer Locks, Waiting Periods, and Closing Deadlines

A transfer restriction can look alarming when a buyer expects immediate delivery. It can also become an excuse used by a dishonest seller to delay scrutiny or demand an extra fee. The right response is neither automatic panic nor automatic acceptance. Identify the actual restriction through the genuine registrar, understand its scope, and build the closing around the supported options.

The phrase “the domain is locked” is too imprecise to resolve a transaction. A routine account security setting, a policy-based restriction on moving between registrars, a dispute-related hold, and a registry-level security service can have different consequences. Ask what the status means for this specific domain and this specific proposed action.

Distinguish the important sixty-day situations

ICANN’s transfer policy distinguishes restrictions associated with a domain’s initial registration, a recent inter-registrar transfer, and a change of registrant. These are not one universal rule. The policy includes a sixty-day period after initial creation, a recent-transfer restriction subject to its stated conditions and exceptions, and a change-of-registrant lock with a registrar-offered opt-out that must be exercised before the change where available. ^[14]

Do not turn that summary into a promise about every extension or provider. Ask the registrar which rule applies, the relevant date, and whether an authorized alternative is available. An opt-out for one kind of lock does not automatically remove another. A buyer’s preferred registrar may need to wait even when a supported same-registrar delivery arrangement is possible.

The sequence of actions can matter. Before changing registrant details as part of a sale, ask how that change affects the intended later registrar transfer. Do not make account changes casually and then assume support can reverse the resulting restriction. Plan the sequence before closing, with the registrar and selected custodian where relevant.

Separate removable security settings from non-routine restrictions

A normal transfer-prohibition setting may be manageable through the account’s genuine interface, while another restriction may require support or may not be removable at that stage. ICANN’s status-code guidance helps explain the meaning of common domain statuses, but a status label alone does not tell the entire factual story. ^[53]

Ask whether the domain is affected by an ownership dispute, court order, abuse investigation, unpaid registration issue, or another material condition. The answer can change the risk assessment substantially. A seller’s explanation should be consistent with the provider’s records and the disclosed transaction history.

Do not ask a seller to disable every available protection for days while negotiations continue. Remove only what is needed, when it is needed, under the approved closing plan. Restore appropriate protections afterward. Security should be managed around a transaction, not abandoned because a transfer is eventually expected.

Make deadlines realistic and specific

A contract should distinguish a target closing date from a condition that cannot presently be satisfied. Identify the responsible time zone, relevant provider operating hours where needed, and any known restrictions. Do not schedule a business launch on the assumption that every participant will complete an unfamiliar procedure instantly.

Build reasonable contingencies for genuine administrative delays without giving either party unlimited discretion. The agreement should explain what happens if transfer cannot proceed by the intended date, what notice is required, and what alternatives may be considered. Counsel can help tailor cancellation or extension provisions to the transaction.

Avoid incentives that reward unsafe shortcuts. A large penalty for a delay the parties already know is likely may push someone toward credential sharing, unsupported account handover, or direct payment outside escrow. The safer response is to design a deliverable closing structure from the beginning. A qualified broker can identify these scheduling problems while commercial terms are still flexible.

Treat “unlocking fees” as claims to verify

A provider may charge legitimate fees for particular services, recovery processes, or account arrangements. The existence of a fee is not itself evidence of fraud. But a stranger’s claim that a special certificate or payment to an unrelated account will remove a policy lock should not be accepted without direct verification.

Ask the genuine registrar what the restriction is, whether the proposed action is possible, and what official fee, if any, applies. Pay only through an authenticated channel for a service you understand and choose to use. Do not send money to a buyer’s nominated technician merely because the buyer says the fee will be reimbursed at closing.

If the stated obstacle changes repeatedly—first a lock, then a compliance certificate, then an insurance deposit—pause the whole transaction. Each new explanation may be an attempt to preserve the appearance of progress while extracting additional payments. Return to the underlying evidence of ownership, authority, funding, and supported transfer capability.

Use alternative structures only after reviewing their consequences

A same-registrar change, neutral custody, delayed closing, or installment arrangement may solve a genuine timing problem. Each changes responsibilities. Determine who controls the domain during the interim, who renews it, who can alter DNS, and what happens if a party defaults or a claim arises.

Do not describe temporary access as completed ownership transfer unless the supported process and agreement establish the intended rights. A buyer who launches a business on a domain still controlled by the seller needs to understand that dependency. A seller who places a name into custody needs clear return and release conditions.

The alternative must also fit the payment provider. A private promise that funds will be released later does not necessarily match the service’s inspection or automatic-release rules. Obtain agreement from the relevant provider before funding or transferring. A workaround is only useful when every important participant recognizes the same arrangement.

Worked example: the avoidable scheduling conflict

A hypothetical buyer plans to move a domain to its preferred registrar immediately after purchase. The seller changes registrant information during preparation without first checking how the current registrar handles the change. A restriction then prevents the expected inter-registrar move within the planned launch schedule.

The parties do not assume fraud, but they do stop treating the original timetable as achievable. The broker verifies the restriction with the registrar, consults the provider about a supported delivery alternative, and obtains appropriate amendments to the closing plan. The buyer separates its branding schedule from the date of a later registrar move and decides whether the revised arrangement is acceptable.

The better outcome would have been to identify the sequencing issue before the change. That is why transfer feasibility belongs near the beginning of due diligence, not at the moment the seller is asked to deliver. A domain can be genuine and valuable while the proposed closing method is temporarily unavailable.

Knowledge of transfer rules should make a transaction calmer, not more reckless. Use it to distinguish ordinary limitations from unexplained obstacles, and to choose a supported path. The goal is a completed sale with clear control and payment—not a race to prove that every delay can be bypassed.

Back to the contents

Chapter 48: Protect DNS, Email, Websites, and Business Continuity

A financially successful domain closing can still become an operational failure if the handover disrupts the services attached to the name. A business may depend on that domain for customer email, account recovery, login systems, website traffic, or internal tools. Treat continuity as a separate workstream rather than assuming that moving registration control moves every associated service safely.

The anti-scam relevance is direct. Confusion during a migration creates opportunities for fake support, unauthorized access requests, and misleading claims about what has been delivered. A documented technical plan reduces both accidental disruption and the uncertainty an attacker can exploit. It also gives the buyer a clearer basis for inspection and acceptance.

Separate registration, DNS hosting, and application services

Identify the registrar, authoritative DNS provider, website host, email provider, and any other relevant service. These may be the same company or several different companies. Record who controls each account and whether the service is included in the sale. A domain-only agreement should not leave the buyer assuming that the seller will continue hosting essential records indefinitely.

Do not infer control from a website loading successfully. The site may continue to work while the buyer lacks registration access, or the buyer may control the registration while a separate service is about to expire. Test the specific responsibility being transferred rather than using a visible web page as a proxy for the whole system.

For a non-operating domain, the continuity plan may be simple. For an active business address, involve a competent technical lead. A broker can coordinate timing and responsibilities, but should not pretend that commercial negotiation expertise replaces knowledge of the buyer’s email, identity, and hosting environment.

Inventory dependencies before changing settings

Create a current record of the configuration and relevant services using authorized access. Identify mail routing, web endpoints, verification records, security-related records, and third-party dependencies that matter to the transaction. Preserve the record securely because it may reveal infrastructure information that should not be distributed widely.

Ask which accounts use the domain’s email addresses for recovery or administrative approval. A seller should remove or replace those dependencies for accounts not included in the sale. A buyer should not inherit access to the seller’s unrelated systems merely because messages begin arriving at the purchased domain.

Conversely, the buyer should establish independent recovery channels for the registrar and other critical services. Avoid creating a circular dependency in which losing the domain also prevents recovery of the account needed to regain it. The appropriate design depends on the organization, but the issue should be considered explicitly rather than discovered during an outage.

Change only what the plan requires

Where possible, separate the registration handover from a major website or email migration. Combining every change into one event makes faults harder to diagnose and can obscure whether the agreed asset has been delivered. The chosen approach should reflect the providers’ actual behavior and the parties’ transition obligations.

Do not assume that existing DNS will remain unchanged under every account push, registrar move, or hosting arrangement. Confirm the provider-specific consequences and prepare the receiving service where needed. A promise that “DNS never changes during a transfer” is too broad to serve as an operational plan.

If DNSSEC is in use, coordinate the relevant signing and delegation information with knowledgeable technical staff. ICANN describes DNSSEC as a way to authenticate DNS data; it is not a guarantee of domain ownership or a protection against payment fraud. Incorrectly managed changes can create a different kind of operational problem, so treat the configuration as part of the migration review. ^[54]

Protect email and private information during the transition

Define whether any mailboxes, archives, forwarding arrangements, or contact addresses are included. A domain purchase does not automatically justify reading the seller’s historical communications. A website acquisition may involve additional data-transfer questions that require legal review and a documented scope.

The seller should plan how customers and counterparties will be informed of new contact details where necessary. The buyer should decide how misdirected mail will be handled without exploiting it. Avoid catch-all collection of unrelated communications as a convenient way to discover valuable accounts or private information.

Remove obsolete forwarding and delegated access when it is safe and appropriate to do so. Confirm that the new owner receives important registrar notices through a controlled address. A lingering forwarding rule can create an unnoticed information path even after passwords and visible account settings have changed.

Define testing and a rollback decision

Before migration, decide what successful operation looks like. For an active domain, that might include website reachability, expected mail flow, certificate behavior, critical integrations, and administrative access. Use tests suited to the actual business rather than a generic checklist copied without understanding.

Identify who can authorize a rollback or other corrective action if a problem occurs. A rollback may not mean reversing the domain sale; it may mean restoring a prior DNS configuration or delaying an application cutover. Distinguish technical recovery from contractual rejection so the teams do not confuse an ordinary migration issue with a dispute over delivery.

Preserve a record of changes, times, and responsible operators. If a suspicious modification appears, this record helps distinguish an authorized transition step from account compromise. Do not allow several participants to make uncoordinated edits because each believes the other is unavailable. One controlled change process is easier to audit and recover.

Worked example: the domain transfers, but renewal email does not

A hypothetical buyer acquires an established domain and receives it into a new registrar account. The website continues to load, so the buyer assumes the handover is complete. Later, the team discovers that critical account notices still depend on an address controlled by the seller’s former agency, while DNS hosting remains on an account scheduled for cancellation.

A proper continuity review would have identified both dependencies before acceptance. The broker could have coordinated the commercial transition while the buyer’s technical lead established the correct notification address and receiving DNS arrangement. The seller could then close unrelated services without creating an unexpected outage.

The problem is not solved by adding more reassuring language to the payment confirmation. It is solved by treating registration control, service continuity, and communications access as separate deliverables. Each has its own evidence and responsible person. That separation also makes it harder for a fake support representative to demand broad access under the pretext of fixing an undefined handover problem.

For a premium acquisition that will become a company’s primary address, continuity planning is part of protecting the purchase price. A qualified broker helps keep the deal organized, but the buyer should involve technical expertise proportionate to the domain’s operational importance. The safest closing is one in which the money, registration, and business services all end up where the parties intended, with no hidden dependence on the former owner.

Back to the contents

Chapter 49: Inspection, Acceptance, and Release of Funds

Inspection is the point at which the buyer checks whether the promised delivery has actually occurred. It should be a planned verification exercise, not a vague period of reassurance after the domain appears in an account. The seller also benefits from a clear inspection process because it creates an objective route from delivery to payment rather than leaving acceptance indefinitely uncertain.

Before closing begins, both parties should understand the applicable period, the event that starts it, the required response, and what happens if nobody acts. Escrow.com’s published inspection guidance explains that acceptance or expiry of the agreed period can lead to release of funds. Read the actual terms for the selected transaction rather than assuming silence keeps the money on hold. ^[12]

Prepare the inspection plan before delivery

Identify the exact deliverables in the agreement and translate each into a check that the buyer can perform. For a domain-only purchase, the core review concerns the correct name, the agreed receiving account or custody arrangement, registration details, and the buyer’s intended control. For a portfolio, the review must reconcile every included name rather than accepting a total count as proof.

Name the person responsible for each check and the person authorized to communicate acceptance. A technical employee may be able to verify account access without having authority to waive a contractual issue. A finance employee may confirm the escrow status without being qualified to inspect DNS dependencies. Keep those roles distinct while ensuring that one coordinator sees the whole result.

Choose an inspection period that fits the supported service and actual scope. A large website acquisition may require different planning from a single unused domain. The period should not be used to postpone fundamental questions about seller authority or legal suitability that should have been addressed before delivery. Inspection is the final gate, not the beginning of due diligence.

Verify the registration, not just a visible website

Sign into the genuine receiving account through an independently verified route. Confirm the exact domain, including the extension and any internationalized representation. Check that the name is not merely listed as a pending transfer, external asset, or item awaiting acceptance. Ask the registrar to clarify ambiguous status labels.

Confirm the agreed registrant arrangement and administrative control using the provider’s available records. Public registration data may be redacted or incomplete, so a public lookup alone may not answer every question. Conversely, the ability to edit DNS is not the same as proof that the buyer has received all promised registration rights. Use evidence appropriate to the deliverable.

Check for unexpected restrictions or dependencies that conflict with the agreement. Some locks or waiting periods may have been disclosed and accepted; others may be new information. Record the distinction. The buyer should not reject a transaction simply because an expected security setting exists, but should not overlook an undisclosed obstacle that materially changes what was purchased.

Reconcile portfolios and broader asset packages carefully

For multiple domains, compare the delivered set with the signed schedule using exact names. Identify missing names, duplicates, substitutions, and unexpected additions. An extra low-value name does not compensate automatically for a missing premium asset. Any substitution requires the agreed approval process, not a verbal assurance that the bundle is approximately equivalent.

Where values or release amounts are allocated by stage, reconcile the relevant group before authorizing that stage’s release. Do not allow a provider to infer an unsupported allocation from an informal spreadsheet. The contract, custody records, and payment instructions should describe the same staged arrangement.

For a website or business asset package, use the separately agreed acceptance criteria for content, software, data, accounts, and transition services. Do not assume that domain receipt establishes delivery of everything else. Equally, do not introduce new requirements after delivery that were never part of the bargain. Clear scope protects both parties from opportunistic reinterpretation.

Communicate issues through the genuine process

If an inspection reveals a problem, document the exact discrepancy and notify the appropriate parties through the provider’s required channel within the applicable period. A casual message to the seller may not satisfy the service’s rejection or dispute procedure. Confirm how the issue affects the current transaction status.

Describe facts rather than conclusions. “The delivered name differs from the signed schedule by one character” is more useful than “this is obviously a scam.” “The registrar confirms the account change is still pending” is more useful than “nothing works.” Precise descriptions allow legitimate errors to be corrected and preserve evidence if deception is involved.

Do not move or materially alter the asset in ways that conflict with the agreement or provider instructions while a return or dispute is being considered. Ask how to preserve the asset and relevant records. A buyer’s attempt to repair everything independently can complicate the factual record, especially in a broader website transaction.

Accept deliberately and document the event

Once the agreed conditions are satisfied, the authorized buyer representative should complete acceptance through the genuine provider’s process. Record the date, transaction reference, and basis for the decision. This need not be a ceremonial exercise; it should simply be clear that acceptance was informed and authorized.

The seller should confirm the provider’s release and disbursement status through its own authenticated access. Do not rely on the buyer’s statement that funds have been released. Distinguish provider authorization, processing, and receipt where the service does so. If a payout issue arises, resolve it with the genuine provider rather than accepting a new payment route supplied by an unfamiliar intermediary.

Keep the acceptance record with the purchase agreement, funding evidence, and delivery confirmations. It forms part of the transaction’s history and may be useful for later ownership, accounting, or dispute questions. Retain it securely without keeping unnecessary copies of sensitive identity information beyond the appropriate retention period.

Worked example: acceptance requested before the final name arrives

A hypothetical buyer purchases a five-domain package with one combined release condition. Four names arrive in the correct account. The seller asks the buyer to accept the entire transaction immediately, explaining that the fifth name is delayed by a routine administrative issue and will follow shortly. The missing name is the package’s most valuable asset.

The buyer checks the agreement and provider terms. Because the transaction has not been structured for partial release, the buyer does not mark full acceptance. The broker coordinates a verified explanation of the delay and, if appropriate, a supported written amendment. The parties may agree to a revised staged structure, but only after the provider confirms it can administer that arrangement.

This response does not presume dishonesty. It simply refuses to record a false completion event. A genuine seller can work through the documented process; a dishonest seller cannot use four successful transfers to make the fifth disappear from the buyer’s attention.

Inspection is most effective when it is boring: the buyer checks the agreed facts, exceptions are resolved, acceptance is recorded, and funds move under known terms. The broker’s contribution is to keep the process organized and prevent pressure from replacing evidence. The final click should reflect a completed review, not exhaustion with the transaction.

Back to the contents

Chapter 50: The Post-Closing Security and Ownership Audit

Closing is the beginning of responsible ownership, not the end of risk management. Once the domain has been delivered and payment completed, the buyer should verify that the registration, access, renewal arrangements, and records are under the intended control. The seller should confirm that the sold asset has been removed from accounts, listings, and processes that could create a later conflict.

A post-closing audit is not a second negotiation. It is the orderly completion of the handover. It catches residual access, stale sale authorizations, incorrect contact details, and forgotten dependencies before they become a new incident. For a valuable business domain, the audit should have a named owner and a documented result.

Confirm the final ownership and account arrangement

Review the genuine registrar account and the records available for the registration. Confirm the correct legal person or entity is reflected where appropriate, the intended administrative contacts are in place, and any required verification has been completed. Do not assume that accepting an incoming domain automatically populated every field exactly as the buyer intended.

For a company, ensure that the asset is not left informally under an employee’s personal account without an approved governance arrangement. Identify who can administer the registration, who approves a sale or transfer, and who can recover the account. The person managing the website need not have unrestricted authority over the registration itself.

Where the domain remains in neutral custody or an installment arrangement, record that status honestly. The buyer may have operational rights without immediate unrestricted registration control. Keep the custody agreement, payment schedule, and release conditions accessible to the responsible people. Calling the asset “fully transferred” prematurely can obscure important obligations.

Review access beyond the password

Change or establish credentials through the genuine provider’s supported process and enable appropriate multifactor authentication. CISA recommends MFA as an important account-protection measure. Use the strongest practical method the provider supports and the organization can manage reliably. ^[21]

Review active sessions, recovery addresses, telephone numbers, delegated users, connected applications, API credentials, and other access paths available in the relevant accounts. Remove temporary participants who no longer need access. A password change is useful, but it should not become an excuse to ignore other authorized routes into the account.

Preserve a secure recovery plan. Store recovery materials according to the organization’s security practices and ensure that access does not depend on one unavailable person. For an individual owner, consider how legitimate recovery would work after a lost device or changed phone number. The goal is resilience without distributing powerful credentials too widely.

Make renewal responsibility explicit

Confirm the current registration term, renewal settings, payment method, and notification destination. Do not rely on a general statement that the transfer “included another year” without checking the actual registration record and applicable conditions. Different extensions and transaction circumstances require specific confirmation.

Set reminders independent of a single email notification. Keep the payment method current and review any premium renewal or special eligibility conditions relevant to the name. A domain acquired at an attractive price can still create an unpleasant surprise if ongoing costs were misunderstood. The acquisition record should include the current renewal information and where to verify future changes.

For a portfolio, reconcile the new assets into the buyer’s inventory with registrar, expiry, cost, and responsible-owner fields. The seller should remove them from its renewal plan once the handover is confirmed. Duplicate responsibility can cause confusion, while assumed responsibility can leave nobody watching the asset.

Remove stale listings and sale permissions

The seller should update marketplaces, broker mandates, landing pages, and any automated sale arrangements to reflect the completed sale. Where a platform supports expedited transfers or preauthorized sale processes, verify how those authorizations are removed or updated. Do not assume every external listing disappears automatically when the registrar account changes.

The buyer should investigate any active listing that still appears to offer the acquired domain. A stale listing may be an administrative issue, but it can also confuse future buyers or create an impersonation opportunity. Contact the genuine platform through its official process and provide appropriate evidence without broadcasting sensitive closing documents unnecessarily.

If the buyer intends to list the domain again, establish fresh, accurate instructions. Confirm the asking price, minimum acceptable terms, authorized broker, and any exclusivity obligations. Do not inherit the seller’s old marketing assumptions accidentally. A new owner needs a new, controlled sales record.

Archive the transaction and close temporary obligations

Create a durable deal file containing the executed agreement, exact asset schedule, key due-diligence conclusions, provider transaction references, delivery confirmation, acceptance, and payment records. Store sensitive documents with access controls appropriate to their content. Keep a practical index so that a future employee or adviser can find the evidence without searching every email account.

Record any surviving obligations: transition support, confidentiality, installments, holdbacks, releases, or post-closing cooperation. Give each a responsible person and completion date where applicable. A transaction is not fully administratively closed while important promises remain known only to the person who negotiated them.

Review data retention with appropriate advisers. Some records may need to be retained for legal, accounting, or business reasons; others may no longer be necessary. Do not interpret security as either deleting everything immediately or retaining every identity document forever. Keep what is justified, protect it, and dispose of unnecessary material through a controlled process.

Worked example: the sold domain remains in an automated listing

A hypothetical seller completes a direct sale of a domain that was previously listed through several channels. The seller updates its own spreadsheet but forgets one marketplace arrangement. A later buyer encounters the old listing and receives conflicting information about availability. The new owner must now explain a transaction it did not authorize.

A post-closing checklist would have required the seller to reconcile every known listing and authorization, and the buyer to check for residual offers. The broker could have coordinated confirmations from the relevant platforms and retained evidence that the old mandate had ended. That modest administrative effort would have prevented a confusing afterlife for a completed sale.

The same principle applies to account access. A former consultant’s permission may have been useful during closing but unnecessary afterward. Removing it is not an accusation against the consultant; it is ordinary completion of a limited role. Good security makes permissions match current responsibilities rather than past convenience.

Schedule a follow-up review after the initial handover, especially for a business-critical domain or large portfolio. Verify that notifications are arriving, services remain stable, and the internal inventory is accurate. The timing should fit the business rather than a universal rule. A valuable domain deserves the same ongoing stewardship as other important business assets: clear ownership, controlled access, reliable records, and no unexplained loose ends.

Back to the contents

Chapter 51: Trademark Threats: Real Legal Risk and Fake Legal Pressure

A legal-looking message about a domain should be neither obeyed automatically nor dismissed automatically. Some notices raise genuine rights issues. Others impersonate lawyers, trademark offices, or dispute providers to demand money, credentials, or a hurried transfer. A third category consists of real commercial opponents making claims whose strength is uncertain. The response should separate authenticity, legal merit, and the requested action.

This chapter provides a method for organizing those questions, not a legal conclusion about any particular name. A material trademark dispute deserves prompt advice from a qualified lawyer. A domain broker can preserve the commercial history and coordinate communication, but should not replace legal counsel when rights and procedural deadlines are involved.

Authenticate the sender and the proceeding

Verify the law firm, professional, office, or dispute provider independently. Use official records and contact channels rather than the telephone number or payment link contained in the demand. A genuine firm’s name and logo can be copied. The existence of a real lawyer with the stated name does not prove that the message came from that person.

Identify what the document actually is. A private demand letter is different from a filed administrative complaint, a court document, or an official registry notice. Ask for the relevant reference and verify it through the appropriate institution. Do not assume that a document is a court order because it uses formal language or includes a seal-like image.

The USPTO warns about trademark-related impersonation and misleading solicitations. That warning supports careful authentication, but it does not mean every trademark notice is false. Verify the particular communication and preserve any genuine deadline while you investigate. ^[55]

Separate trademark existence from entitlement to the domain

A trademark search can be a useful starting point, and the USPTO provides an official search system for U.S. federal trademark records. A search result is not a complete legal analysis of domain ownership or intended use. Other jurisdictions, unregistered rights, timing, goods and services, and the facts of the acquisition may matter. ^[56]

Do not assume that a trademark registration automatically requires every similar domain to be transferred. Equally, do not assume that using a dictionary word, adding another word, or choosing a different extension guarantees safety. Have counsel assess the actual rights and circumstances rather than relying on slogans from buyers, sellers, or online discussions.

For a prospective purchase, legal suitability should be considered before the buyer commits heavily to branding or development. A domain can be technically transferable and still create a serious legal problem for the intended use. Escrow and brokerage can improve transaction execution; they do not turn an unsuitable branding choice into a lawful one.

Recognize pressure that tries to replace legal review

Be cautious when the sender demands immediate payment to an unrelated account, a transfer code, or a confidential transfer before you can consult counsel. A claimed deadline should be verified, not accepted simply because it is short. Genuine proceedings have identifiable procedures; an attacker may use urgency to prevent you from checking whether a proceeding exists at all.

A proposal to settle can be legitimate, but it should be reviewed as a legal and commercial agreement. Confirm who is authorized to settle, what rights are being released, what happens to the domain and money, and how the exchange will be administered. Do not treat an informal promise to “withdraw all complaints” as equivalent to a properly documented resolution.

Avoid responding with threats of your own. An emotional reply can create an unhelpful record and distract from the facts. A neutral acknowledgment that the matter is being reviewed may be appropriate, subject to counsel’s advice. Do not admit infringement, fabricate a history, or promise a transfer merely to make the message disappear.

Preserve the history that matters

Collect the acquisition date and documents, registration history available to you, the domain’s use, relevant correspondence, and any earlier offers or demands. Preserve original records where possible. Do not alter a website or delete communications in an attempt to manufacture a cleaner story after receiving a claim.

Create a factual chronology for counsel. Distinguish what you know personally from what a seller or broker told you. A statement that “the seller said there had never been a complaint” is not the same as independent confirmation that no complaint existed. The distinction helps the adviser assess both the rights issue and any potential claim arising from the sale.

Keep the chronology focused. Counsel needs the important facts and documents, not an unfiltered archive with no explanation. At the same time, do not omit inconvenient material. A useful legal assessment depends on an accurate record, including facts that may weaken your preferred position.

Keep brokerage and legal strategy coordinated

If a claim arises during a pending sale, notify the appropriate participants through the agreed process. Do not continue marketing the domain as free of known disputes while withholding a material claim. Counsel should advise on disclosure, contractual obligations, and any restrictions on transfer. The broker should coordinate the commercial consequences without independently deciding the legal merits.

A buyer’s broker can help avoid using legal threats as a bargaining shortcut. A seller’s broker can help prevent an anxious owner from surrendering a valuable asset merely because a demand sounds authoritative. In both roles, the broker’s best contribution is disciplined process and accurate information, not bravado about guaranteed victory.

Where the parties pursue a negotiated resolution, use a supported payment and transfer arrangement and document the settlement scope. The existence of a dispute does not eliminate ordinary fraud risks. An impersonator can intervene in settlement communications just as in an ordinary sale, particularly if payment instructions or signers change late in the process.

Worked example: a real mark, an unverified demand

A hypothetical domain owner receives a message claiming to represent a company with a genuine trademark. The message demands a transfer code within hours and says that providing the code will prevent an automatic regulatory fine. The owner finds the trademark in an official database and initially assumes the entire demand must therefore be authentic.

The owner’s adviser separates the questions. The trademark exists, but that does not authenticate the sender, establish the legal claim, or justify sharing a transfer credential. The adviser contacts the purported firm independently and asks counsel to assess any real rights issue. The owner preserves the message and does not transfer the domain based on the claimed fine.

The result might reveal impersonation, an inaccurate demand, or a genuine dispute requiring attention. The method remains sound in each case because it does not confuse one verified fact with the whole story. A real trademark can be used as bait just as a real escrow company’s logo can be used on a fake website.

The next chapter explains the basic distinction between UDRP, URS, and reverse domain name hijacking. Read it as a map to the relevant procedures, not as a substitute for timely representation. The safest response to legal pressure is informed, documented, and proportionate—not automatic surrender and not automatic defiance.

Back to the contents

Chapter 52: UDRP, URS, and Reverse Domain Name Hijacking

Domain dispute procedures are important safeguards, but their names are also used in threats and misleading sales pitches. A buyer may be told that a domain is “UDRP-proof.” A seller may be told that refusing an offer automatically proves cybersquatting. A victim of account theft may be told to file a trademark complaint even when the real issue is an unauthorized transfer. Each claim needs careful examination.

The first task is to identify the problem and the procedure that actually addresses it. Trademark abuse, contractual ownership, account compromise, and registrar-transfer disputes can overlap, but they are not the same legal question. Use this chapter to organize the issues for qualified counsel, not to select a remedy by acronym alone.

Understand the basic UDRP test and remedies

Under the Uniform Domain Name Dispute Resolution Policy, a complainant must establish three elements: the domain is identical or confusingly similar to a mark in which it has rights; the registrant lacks rights or legitimate interests; and the domain was registered and is being used in bad faith. UDRP remedies are transfer or cancellation, not an award of damages. ^[57]

That framework explains why a trademark certificate alone does not answer the whole case. It also explains why a registrant should not rely on a single defensive slogan. The relevant evidence must address the actual elements and circumstances. A lawyer familiar with domain disputes can assess the relationship between the acquisition history, intended use, correspondence, and asserted rights.

WIPO’s guide explains the administrative process and provides a route to official procedural resources. Use the current rules and the actual provider’s notices to identify obligations and deadlines. Do not assume that a general article gives the complete timetable for a particular proceeding. ^[58]

Do not confuse URS with a transfer remedy

The Uniform Rapid Suspension system is a distinct procedure for qualifying clear-cut trademark-abuse cases in covered domains. Its remedy is suspension rather than transfer of the registration to the complainant. Applicability depends on the relevant registry framework, so it should not be assumed for every extension. ^{[59] [60]}

A person seeking to acquire a domain should therefore be skeptical of a service promising that a URS filing will simply deliver ownership. Ask counsel what outcome the procedure can provide and whether the facts support its use. A process designed for one remedy should not be marketed as another.

A registrant receiving a genuine notice should respond promptly through the appropriate procedure. Do not ignore it because the domain was purchased through escrow or because a broker believes the name is valuable. Transaction safeguards and trademark rights are different subjects. A well-executed purchase does not exempt the buyer from applicable dispute rules.

Recognize reverse domain name hijacking accurately

Reverse domain name hijacking concerns bad-faith use of the UDRP to try to deprive a registrant of a domain. WIPO’s Overview 3.1 discusses circumstances supporting such findings, including misleading evidence and complaints pursued without a plausible basis. Losing a complaint does not automatically establish reverse domain name hijacking. ^[61]

For a buyer, the practical lesson is to keep acquisition negotiation separate from unsupported legal pressure. A seller’s refusal to accept your budget is not a legal wrong by itself. Do not instruct a broker to threaten a complaint merely to make a price seem unreasonable. Have counsel assess any genuine rights issue independently of the frustration of an unsuccessful negotiation.

For a seller, the lesson is to preserve the negotiation history and obtain advice rather than responding with an automatic counteraccusation. A weak-looking demand may still need a timely response. The label should follow a proper assessment of the facts, not serve as a substitute for one.

Avoid simplistic claims about age, resale, and dictionary words

WIPO’s current overview treats domain resale and dictionary-word arguments in their factual context; neither is an automatic answer to a bad-faith allegation. It also distinguishes relevant acquisition circumstances from a domain’s apparent historical age. A buyer should obtain advice about its own acquisition and intended use, not rely solely on an old creation date. ^[61]

This matters during due diligence. A seller may truthfully say that a domain was first registered many years ago while leaving out a more recent change in ownership or a known dispute. Ask for the relevant history and disclose the intended business use to counsel. The legal assessment should reflect the buyer’s actual plan, not a hypothetical benign use nobody intends to pursue.

Do not assume a prior decision about another domain guarantees the same outcome. Similar words can appear in different factual settings. The value of precedent and overview material lies in helping a qualified adviser identify the relevant analysis, not in providing a slogan that makes further review unnecessary.

Preserve the domain and the procedural record

If a genuine proceeding is underway, ask counsel and the registrar about applicable restrictions before attempting to move, sell, or change the registration. Do not try to evade a dispute by moving the asset through another account or entity. Such conduct can worsen the situation and complicate the record.

Preserve notices, registration records, acquisition documents, website history available to you, and communications with the opposing party. Keep track of how and when notices were received. Use the provider’s genuine channels for submissions and verify payment requests independently. A real dispute can still be targeted by impersonators posing as administrators or settlement agents.

Maintain renewal and account security while the matter is pending, following the applicable rules and advice. Do not assume that a dispute freezes every operational obligation indefinitely. Assign someone to monitor the registration and genuine notices so that an avoidable administrative failure does not create a separate loss.

Worked example: a failed negotiation becomes a threatened complaint

A hypothetical company wants a domain held by an investor. The investor declines the company’s offer and quotes a higher price. A company employee suggests threatening UDRP because the company has recently adopted a similar brand. The employee assumes that a refusal to sell cheaply will make the investor look unreasonable to a panel.

The buyer’s broker does not turn that frustration into a legal threat. Instead, the broker refers the rights question to counsel and continues to treat the acquisition as a commercial negotiation unless a properly assessed legal claim exists. Counsel reviews the relevant dates, rights, use, and communications rather than treating the company’s preferred budget as evidence.

The company may decide to negotiate, choose another name, or pursue a supported legal route. What it avoids is using an administrative procedure as a substitute for a purchase it could not agree. On the seller’s side, preserving the full correspondence helps ensure that any later legal assessment has an accurate account of what happened.

A qualified broker contributes most when it knows the boundary of its role. It can supply transaction history, explain commercial context, and coordinate with counsel, but it should not promise immunity or victory. The safest domain strategy respects both legitimate trademark rights and legitimate domain ownership, using the correct procedure for the actual dispute rather than treating every conflict as a scam.

Back to the contents

Chapter 53: Cross-Border Deals, Country-Code Rules, and Compliance

Domain transactions can involve a buyer in one country, a seller in another, a registrar elsewhere, and a payment provider operating through a separate legal entity. That structure is not inherently suspicious. It does, however, create more questions about eligibility, identity, payment, language, taxation, and enforcement. A safe process answers those questions before the parties become dependent on a closing date.

Geography should not become a substitute for evidence. A foreign counterparty is not automatically risky, and a local counterparty is not automatically trustworthy. The relevant issues are whether the participants can be verified, the asset can lawfully be transferred, the providers support the transaction, and the agreement can be understood and implemented.

Check the extension’s own rules

Do not assume that every country-code domain follows the same registration and transfer rules as a generic top-level domain. Some namespaces have eligibility requirements, local connections, naming conditions, or transfer procedures that affect who can receive and retain a registration. Verify the current rules with the responsible registry and registrar.

For example, auDA publishes specific licensing and transfer rules for .au domains, including requirements relevant to the new registrant. A buyer considering such a name should review the applicable category and eligibility conditions rather than assuming that payment alone creates a valid entitlement. ^{[34] [35]}

Ask whether the buyer’s intended legal entity qualifies and what evidence is required. Do not use a nominal local representative or inaccurate registration information merely because a seller says everyone does it. A structure that depends on concealment or a person whose obligations are unclear can turn a valuable acquisition into a fragile arrangement.

Verify identities and authority across systems

Corporate records, identification documents, and professional registers differ by jurisdiction. Obtain appropriate help interpreting them rather than dismissing unfamiliar formats or accepting them uncritically. Confirm the entity’s exact legal name, status, signer authority, and relationship to the registration and payment accounts.

Translations may be necessary for meaningful review. A buyer should not sign a document it cannot understand because the seller supplies a reassuring summary. For material terms, use competent translation and legal advice appropriate to the jurisdictions involved. Decide which language version controls and how inconsistencies will be resolved.

Keep identity verification proportionate and secure. The fact that a transaction is international does not justify sending every personal document to every participant. Use the genuine provider’s compliance channel where required and limit broader sharing to what is necessary for the specific legal or commercial question.

Confirm provider support before negotiating around it

Ask the escrow or payment provider whether it supports the parties, countries, currencies, amounts, and asset type. Complete required onboarding early enough that a declined account does not create pressure for a last-minute direct payment. A provider’s general international marketing does not establish eligibility for every possible transaction.

If compliance review raises questions, answer accurately through the genuine service. Do not split payments, disguise the payer, alter descriptions, or route funds through unrelated people to avoid checks. Where sanctions, financial controls, or other legal restrictions may be relevant, obtain current guidance from qualified advisers and the responsible institutions.

A legitimate provider may decline a transaction without implying that either party is a criminal. The response is to understand the reason where available and consider a lawful supported alternative. A stranger offering to bypass the restriction for an advance fee is not solving the compliance problem; the proposal may create additional risk.

Allocate currency, fees, and tax questions explicitly

State the price currency and the payment currency, if different. Identify who bears conversion costs, sending and receiving fees, and any shortfall caused by deductions. A seller should not discover at disbursement that the net amount is materially below the agreed expectation because the contract never addressed these items.

Obtain tax advice appropriate to the transaction rather than assuming that a domain sale is treated identically everywhere. The relevant questions can depend on the parties, asset package, business status, and jurisdictions. This guide does not provide tax rates or a universal classification because those would be unreliable without the actual facts.

A tax or compliance payment request should be authenticated at the responsible source. Do not pay a supposed border-release charge, ownership tax, or international transfer certificate merely because an email says the domain cannot move otherwise. Ask which authority or provider requires it, under what rule, and through which verified channel payment is made.

Make enforcement and practical communication realistic

Discuss governing law, dispute forum, notices, and enforcement with counsel before signing. The existence of a favorable clause does not answer every practical question about pursuing a claim abroad. Consider the counterparty’s identity, assets, cooperation, and the cost of a dispute in relation to the transaction’s value.

Plan communication across time zones. Identify working hours, backups, and realistic approval windows for banks, registrars, lawyers, and the buyer’s technical team. A closing should not depend on a single employee answering an unexpected call in the middle of the night. Predictable scheduling reduces the temptation to accept unverified substitutes.

Keep the operational record clear enough for all participants. Use exact dates and time zones rather than “tomorrow morning.” Avoid ambiguous number formats or currency symbols. A small clarification in the closing sheet can prevent a major misunderstanding, particularly when different conventions are normal in the parties’ countries.

Worked example: an eligible seller, an ineligible buyer

A hypothetical buyer agrees to acquire a country-code domain from a seller who validly qualifies under the namespace’s rules. The buyer assumes those rights can simply be purchased and held through its existing foreign company. Only after price agreement does the registrar ask for eligibility evidence the buyer cannot provide.

A qualified broker identifies the issue before funds are sent and refers the proposed structure to appropriate local advice. The parties verify whether a lawful qualifying arrangement exists and whether the buyer actually wants the obligations it would entail. If not, they can cancel under the agreed conditions or consider a different domain rather than improvising false information.

The seller’s ownership was not necessarily defective, and the buyer was not necessarily deceived. The failure was treating a transferable registration as if its eligibility conditions disappeared on sale. A namespace-specific review turns that hidden assumption into an explicit decision.

International experience is one reason a strong broker can be valuable in a premium transaction. The benefit is not a claim to override local rules; it is knowing when those rules, provider limitations, or legal questions need attention. The safest cross-border deal is one in which differences are understood and documented, not ignored because the domain itself looks the same on every screen.

Back to the contents

Chapter 54: Employees, Agencies, Freelancers, and Insider Access

A domain can become vulnerable without any stranger sending a phishing message. An employee may register it in a personal account, an agency may retain broad access after a project ends, or a freelancer may be the only person who knows how to recover the account. These arrangements can function smoothly for years and still create serious problems during a sale, dispute, staff departure, or security incident.

The answer is not to distrust everyone who helps manage a website. It is to make ownership, authority, and access explicit. A business should be able to identify who owns the registration rights, who administers the account, who may authorize a sale, and what happens when a working relationship ends. Those are separate questions even when one person currently performs every role.

Put important domains into an intentional governance structure

For a business asset, decide which legal entity should be the registrant and how the registrar account should be controlled. Record that decision and align the provider’s records with it through the supported process. Avoid leaving the arrangement dependent on an employee’s informal understanding that the company can have the domain later.

Where an agency registers a name on a client’s behalf, the engagement should explain the ownership and administration arrangement. The client should know what it will receive, what access it has, and how it can move the asset when the engagement ends. A low-cost website package should not conceal a commercially important dependency.

For founders and small teams, address the domain before a disagreement develops. A company may rely on a name originally acquired by one founder personally. Documenting the intended transfer or license early is easier than reconstructing intentions during a financing, sale, or breakup. Obtain legal advice where rights or consideration need formal treatment.

Match permissions to the job being performed

A designer who edits pages may not need authority to transfer the domain. A marketing contractor may need limited DNS changes without access to saved payment methods or every registration in the account. Use supported roles and delegation where available, and review what each permission actually allows.

Avoid shared master passwords when the provider offers a more controlled alternative. Shared access makes it harder to identify who performed an action and harder to remove one person without affecting everyone else. Where a provider lacks granular roles, consider whether a different account arrangement or additional internal controls are warranted.

Keep recovery routes under intentional control. A former employee’s personal phone number or email address should not remain the only way to recover a critical business account. Establish backups and an approval process that protects against both lockout and unauthorized recovery. Convenience for the current administrator should not determine the company’s long-term ability to retain its domain.

Verify authority when an insider proposes a sale

A buyer should not assume that a person with a company email address or registrar access can sell the company’s domain. Ask for the appropriate corporate authorization and verify it through the agreed process. The seller’s technical role may explain access without establishing authority to dispose of the asset.

This is particularly important when the proposed sale is unusual: a company’s primary domain, a name used by a subsidiary, or an asset apparently offered far below expectations. Do not treat unusual circumstances as proof of theft, but identify the decision-maker and supporting approvals before proceeding.

A broker can help by separating the contact who can execute the transfer from the person who can approve the sale. Counsel may need to review corporate, employment, insolvency, or agency issues. The transaction should not depend on a buyer deciding that technical access is close enough to ownership.

Build offboarding into the normal workflow

When an employee or contractor leaves, review registrar, DNS, hosting, email, marketplace, and recovery access as appropriate. Revoke permissions that are no longer required and preserve legitimate business records. Coordinate the timing so that access removal does not unexpectedly break a service the business still needs.

Update the domain inventory and responsibility map. Identify the new administrator and ensure that the person can actually access the necessary systems through authorized means. A document naming a new owner of the task is not enough if the old administrator remains the only recovery contact.

Apply the same process when a broker’s mandate ends or a transaction is canceled. Temporary access and authority should expire with the role unless a specific continuing arrangement has been agreed. Removing access is ordinary governance, not an accusation that the former participant intends harm.

Handle disputes without unauthorized self-help

If an agency or former employee refuses to cooperate, preserve the relevant agreements, invoices, registration records, and communications. Ask the registrar about its supported account or ownership review process, and obtain legal advice about the dispute. Do not attempt to break into an account, impersonate the former administrator, or fabricate documents to regain control.

A disagreement over unpaid invoices may involve real contractual rights and responsibilities. It should not be reduced automatically to “the agency stole the domain,” especially when the registration arrangement was poorly documented. Equally, a legitimate fee dispute does not make every threatened action appropriate. Counsel can distinguish the issues and advise on a lawful route.

Protect business continuity while the rights question is resolved. Use authorized alternative contact channels, preserve evidence, and avoid making public allegations beyond what can be supported. A broker may assist with transaction history or negotiation, but should not market itself as able to override provider procedures or decide contested ownership.

Worked example: the retiring administrator

A hypothetical company prepares to sell a valuable unused domain. The employee who registered it years earlier is retiring and has always managed it through a personal registrar account containing other names. The company believes it owns the asset, the employee agrees in principle, and the buyer is ready to close. Nobody has documented the handover or checked the account’s recovery settings.

The broker pauses execution long enough for the company and employee to formalize the appropriate authority and use the registrar’s supported process. Counsel addresses any ownership documentation needed, and the technical team establishes a receiving arrangement that does not expose the employee’s unrelated personal domains. The buyer receives evidence of a clean, authorized transaction rather than a password passed between people who trust one another.

The same situation could become far harder if the employee were unavailable or the relationship had deteriorated. That is why internal governance belongs in scam prevention. Clear records and limited permissions reduce the opportunities for both genuine misunderstanding and deliberate abuse.

The lasting objective is organizational independence from any one individual’s goodwill or memory. A company should be able to prove its rights, administer the asset, and complete a lawful sale without relying on an informal favor. Qualified brokerage is most effective when that foundation exists—and can help identify when it needs to be repaired before a buyer is invited to rely on it.

Back to the contents

Chapter 55: Extortion, Coercion, and Threats to Your Business

An extortionate message tries to make the cost of refusing seem greater than the cost of compliance. In a domain context, the threat may involve stolen access, website disruption, exposure of private information, reputational damage, or a claim that the sender can interfere with a pending sale. The first response should protect people and preserve options, not reward the sender’s demand for an immediate, isolated decision.

Some threats are bluffs; others reflect a real compromise. Do not decide which solely from the sender’s confidence or the amount of technical detail in the message. Separate the claim from independently verifiable facts. If there is an immediate threat to personal safety, contact local emergency services or the appropriate police authority rather than treating the matter only as a domain transaction.

Identify the threatened asset and the evidence

Ask internally what the sender claims to control: the registrar account, DNS, website host, email system, confidential documents, or merely information already public. Each possibility requires a different response. A screenshot of a public page does not establish account access, while an unexpected provider-confirmed change deserves urgent investigation.

Preserve the original message and any attached evidence without opening suspicious files unnecessarily. Record timestamps, account identifiers, transaction references, and the exact demand. Have qualified technical staff inspect relevant logs and systems through authorized access. Do not let the sender direct the investigation by requiring you to install software or visit a purported verification portal.

Avoid challenging the sender to demonstrate destructive capability. The aim is to assess risk safely, not provoke a proof exercise that harms the business. Use your own providers and security team to establish what has changed and what remains under your control.

Do not confuse a high asking price with extortion

An owner refusing to sell a domain cheaply is not, by itself, committing extortion. A difficult negotiation, a firm reserve price, or a decision not to sell can be legitimate. The analysis changes when unlawful threats, unauthorized access, deception, or other coercive conduct enter the situation.

Likewise, a real legal demand may be unwelcome without being a scam. Chapter 51 explains how to authenticate and assess such claims. Use precise language when reporting the facts. Calling every hard bargain “blackmail” can obscure the conduct that actually needs attention and weaken the credibility of a legitimate complaint.

A qualified broker can help maintain that distinction. The broker should negotiate commercially where a commercial negotiation is appropriate and refer genuine threats or legal issues to the right specialists. Professional representation is not a license to use intimidation on either side of a deal.

Contain access and involve the right responders

Where account compromise is suspected, contact the genuine registrar or relevant service provider through an independently verified channel. Ask about protective restrictions and recovery steps appropriate to the incident. Secure unaffected communication channels so the attacker cannot monitor or redirect the response.

Bring in legal, security, and operational decision-makers as needed. If insurance may apply, review the policy and contact the insurer through its genuine process without delaying urgent containment. Do not assume coverage, reimbursement, or approved-vendor requirements; verify the actual policy and circumstances.

The FBI does not support paying ransomware demands and warns that payment does not guarantee recovery. Although a domain-related threat may differ from ransomware, the broader caution remains important: a criminal’s promise is not a reliable assurance that payment will end the harm. Obtain specialist and law-enforcement guidance for the actual incident. ^[62]

Keep decisions centralized and documented

Name one coordinator for the response and define who may communicate externally. Multiple employees replying independently can reveal conflicting information or accidentally make commitments. The coordinator should maintain a factual log of messages, provider contacts, decisions, and unresolved questions.

Do not make promises about payment, settlement, or silence without the appropriate advice and authority. Any contemplated transaction with a threatening party may raise legal, sanctions, evidentiary, and practical issues. These require current assessment, not a generic internet answer. A broker should not offer to solve them through an informal private payment.

Separate business-continuity decisions from the threat conversation. The company may need to move customer communications to a safe channel, suspend a compromised service, or prepare an alternative website. Those protective steps should be evaluated on their own merits rather than presented to the attacker for approval.

Protect customers from secondary deception

If a compromised domain could send misleading messages or host a fake payment page, determine what warnings are necessary through secure channels. Coordinate with counsel and relevant providers so the message is accurate and does not expose more sensitive information. Customers need actionable guidance about what not to trust and where to obtain verified updates.

Do not announce that everything is safe merely because the visible website has been restored. Confirm the relevant account, email, DNS, and access issues with the technical team. An incomplete recovery can leave paths for further deception even when the homepage looks normal.

Preserve evidence while restoring service. Avoid deleting logs or rewriting the timeline to make the incident look smaller. An honest record helps the organization learn, supports reporting, and may be important for legal or insurance questions. Operational recovery and evidentiary preservation should be coordinated rather than treated as competing goals.

Worked example: a threat timed to a sale announcement

A hypothetical company announces that it has acquired a premium domain. Soon afterward, an unknown sender claims to have retained access through the seller’s former administrator and demands payment to avoid disrupting the launch. The message includes details from the public announcement and a screenshot of the website’s existing DNS information.

The company does not treat those public details as proof of control. Its technical lead checks the genuine registrar, DNS provider, recovery settings, and access logs. Counsel and the security team preserve the threat and decide on appropriate reporting. The broker supplies the closing record and helps contact the verified former owner without using any contact details supplied by the threatening sender.

If the review finds no compromise, the company still has a documented threat and a stronger understanding of its controls. If it finds unauthorized access, the response can proceed through the correct providers without having wasted the initial period negotiating on the attacker’s terms. In both cases, verification replaces panic.

The most useful preparation is a business-continuity and incident-response plan established before a threat arrives. A valuable domain should not be the only route to your customers, your account recovery, or your advisers. Professional brokerage can help organize the acquisition and its records, but ongoing resilience is what prevents a threatening message from controlling the business’s next decision.

Back to the contents

Chapter 56: Protect Personal Data and Confidential Deal Information

Domain due diligence requires information, but more information is not automatically better. A buyer may need evidence of authority without needing an unredacted passport in every email thread. An escrow provider may require identity checks without the seller needing to see the same documents. A broker may need a budget without having permission to disclose it to every potential counterparty.

Treat information as another asset in the transaction. Decide what is needed, why it is needed, who should receive it, how it will be transmitted, and how long it should be retained. That discipline supports legitimate verification while reducing the material available for impersonation, identity theft, and later pressure.

Begin with a purpose, not a document demand

For each requested item, identify the question it is supposed to answer. A corporate record may help identify an entity. A board authorization may address authority to sell. A provider’s secure identity process may satisfy its compliance requirements. These purposes should not be blurred into a general demand for everything the other party can produce.

Ask whether a less intrusive form of evidence can answer the question adequately. A redacted document, direct professional confirmation, or provider-administered verification may be appropriate in some circumstances. Do not redact information the responsible institution genuinely requires without discussing it; the goal is sufficient verification, not concealment.

The UK ICO’s data-minimisation guidance emphasizes keeping personal information adequate, relevant, and limited to the purpose. The legal framework applicable to a particular transaction may differ, but the practical discipline is useful: collect what the legitimate task requires, not an indefinite archive of everyone involved. ^[47]

Authenticate the recipient before sending sensitive material

Verify the institution and its upload channel independently. A request for identification can be legitimate and still be impersonated. Do not assume that a page is genuine because it displays a familiar escrow logo or because the request appears inside a long-running email conversation.

Check the person’s role and need for access. A buyer’s marketing consultant may not need the seller’s identity documents. A technical transfer assistant may not need banking information. A broker should be able to explain who will receive confidential material and how it relates to the engagement.

Avoid using ordinary reply-all messages for sensitive attachments. Use a verified secure method appropriate to the content and provider requirements. Where passwords or access controls are used, remember that they protect transmission or storage only if the destination itself is correct. Encryption does not make an impostor an authorized recipient.

Control the commercial information flow

A buyer’s identity, budget, launch plan, and acquisition strategy may be commercially sensitive. A seller’s reserve price, financial circumstances, portfolio composition, and urgency may be equally sensitive. Agree with the broker what can be disclosed and at what stage.

Confidentiality should support a legitimate transaction, not conceal material facts from institutions entitled to know them. A buyer can pursue a discreet acquisition while still providing required information to counsel, escrow, and other responsible parties. Do not confuse confidentiality with permission to use false identities or misleading compliance information.

Keep internal negotiation notes separate from documents intended for the counterparty. Before sharing a file, review comments, tracked changes, embedded data, and access permissions. A document can reveal more than its visible final text. The practical control is a deliberate release process, especially for material offers and legal drafts.

Manage access to shared deal rooms and collaboration tools

Use individually assigned access where practical and remove participants whose roles have ended. Avoid permanent public links for confidential transaction records. Check whether recipients can download, reshare, or invite others, and choose settings that fit the actual collaboration need.

Do not upload unredacted identity documents, private contracts, or sensitive deal data into an unapproved online tool merely to summarize or translate them. Confirm that the organization permits the service and understands its data-handling terms. Convenience during a busy closing should not bypass confidentiality or privacy obligations.

Maintain an index of the authoritative documents so that participants do not circulate outdated versions. A controlled file set also reduces the risk that an attacker can introduce a replacement agreement or payment instruction into a confusing collection of attachments. Information governance and fraud prevention reinforce one another here.

Plan retention, disclosure, and incident response

Determine what records should be retained for legal, accounting, compliance, and business purposes, with advice where necessary. Delete or restrict unnecessary copies through a controlled process. A canceled deal does not always justify immediate destruction of every record, but it also does not justify keeping unlimited sensitive information without a purpose.

If information may have been exposed, identify what was involved, who had access, and which accounts or people may be affected. The FTC’s business breach guidance recommends coordinated security, legal, and communications responses and preservation of evidence. Apply the relevant local legal requirements rather than assuming a single global notification rule. ^[63]

Do not promise secrecy about a breach before understanding applicable duties. Equally, do not publish personal documents as proof that a counterparty behaved badly. Reporting can be supported with appropriately handled evidence without turning private information into a public weapon. Counsel can help balance preservation, disclosure, and protection of affected people.

Worked example: the fake compliance upload

A hypothetical seller is completing a genuine escrow transaction. An email says the provider needs a fresh identity check and links to a page asking for a passport, bank statement, and account password. The message includes the correct transaction reference, which makes it seem plausible.

The seller signs into the provider through a previously verified address and checks the actual requirements. The genuine service does require a particular identity document but does not require the registrar password or the additional materials requested by the linked page. The seller submits only the required information through the authentic channel and reports the suspicious message.

The lesson is not to refuse all identity checks. It is to authenticate the recipient, understand the purpose, and separate legitimate compliance from excessive or unrelated demands. A scam can borrow a real requirement and add a dangerous extra step. The presence of one valid request does not validate the whole package.

A qualified broker can improve this process by staging disclosure and directing participants to the proper institutions. The broker should not become an unnecessary warehouse of personal documents or a reason to bypass the provider’s secure procedures. The best transaction record contains enough evidence to support the deal while exposing no more sensitive information than the legitimate process requires.

Back to the contents

Chapter 57: Scams Aimed at Domain Investors and Portfolio Owners

Domain investors face the same basic fraud risks as other buyers and sellers, but repetition and scale change the operating problem. An owner handling hundreds or thousands of names may receive many inquiries, renewal notices, marketplace messages, and transfer requests. A weak process can be repeated quickly, while a convincing scam can hide among ordinary administrative work.

The solution is not to investigate every low-value inquiry as though it were a corporate acquisition. It is to standardize safe handling, identify escalation triggers, and preserve stronger controls around consequential actions. Efficient investing requires a process that can reject bad interactions cheaply without making legitimate buyers struggle through unnecessary friction.

Build a portfolio system that supports verification

Maintain an accurate inventory with exact names, registrar, registration status, renewal information, acquisition record, active listings, and any special obligations. Keep sensitive credentials out of ordinary sales spreadsheets. A portfolio list should help identify the asset, not provide everything needed to move it.

Record who is authorized to price, negotiate, and sell each name. Where several brokers or marketplaces are involved, make mandates and exclusivity visible. Conflicting instructions can create disputes even without fraud, and they can make an unauthorized representative look credible. A buyer should not have to untangle the seller’s internal sales arrangements after accepting an offer.

Use a consistent process for adding newly acquired names. Reconcile the delivered inventory, archive the purchase evidence, review account security, and update sale permissions. A portfolio that grows faster than its records becomes harder to defend against both mistaken claims and deliberate impersonation.

Screen inquiries without rewarding advance-fee traps

A genuine inquiry should be able to proceed toward a defined transaction without requiring the seller to buy an appraisal, certificate, or unrelated service from the supposed buyer’s chosen vendor. Use a standard response that offers a verified transaction route and declines paid prerequisites. Chapter 22 explains the appraisal pattern in detail.

Qualify serious interest proportionately. Ask about the exact domain, intended transaction structure, and readiness to use an appropriate closing service. Do not demand intrusive personal information from every early-stage prospect. As the discussion becomes material, escalate identity and authority checks through the proper channels.

Separate a high offer from evidence that the buyer can and will close. A portfolio owner can waste substantial time responding to imaginary demand even without losing money directly. Track the difference between inquiries, credible offers, funded transactions, and completed sales. That distinction improves both scam resistance and investment decision-making.

Treat bulk offers and portfolio access cautiously

An offer to buy many names can be attractive because it promises immediate liquidity and less administrative work. Verify the buyer, exact asset schedule, allocation where relevant, funding arrangement, and staged delivery conditions. Do not lower the verification standard simply because the transaction would solve a cash-flow problem.

Be cautious about requests for full registrar access to “audit” the portfolio. A buyer can review an appropriately prepared inventory and evidence without receiving master credentials. If deeper technical review is justified, use a controlled method with limited access and professional coordination.

For partial portfolio sales, isolate the intended assets operationally where the provider supports it. Confirm that transfer preparation does not expose unrelated names. A batch authorization file or broad API permission can create a much larger risk than the value of the specific sale being negotiated.

Question services that promise demand rather than demonstrate it

Investors may be offered guaranteed end-user leads, exclusive buyer databases, automated outbound systems, or managed sales programs. Evaluate the actual deliverable, contract, fees, data rights, and evidence of performance. A list of company names is not the same as confirmed purchase interest, and an email address is not permission to make misleading claims.

Do not allow a marketer to advertise your domains with fabricated traffic, false scarcity, invented offers, or unauthorized trademark references. The seller remains exposed to the consequences of its sales process even when an outside contractor writes the messages. Require accurate representations and clear approval boundaries.

An investment coach or portfolio manager should not be evaluated solely on screenshots of selected sales. Ask how acquisition costs, renewals, unsold inventory, commissions, and unsuccessful transactions are treated. The economic questions in Chapter 38 remain relevant at portfolio scale: gross sale prices are not the same as net investment returns.

Use escalation tiers rather than one rigid workflow

For a routine low-value sale through a genuine marketplace, the supported platform process may be proportionate. A premium direct inquiry, unusual payer, corporate authority issue, or complex transfer should trigger a more detailed review. Set these triggers in advance so that excitement about a particular offer does not decide the standard.

A specialist broker can be especially useful for the portfolio’s most valuable assets or for a strategic bulk sale. The broker may help qualify buyers, manage outreach, negotiate terms, and coordinate closing. It does not follow that every inexpensive name needs a bespoke brokerage mandate. Allocate professional attention where it can materially improve the outcome.

Review exceptions after each significant transaction. If a particular scam pattern repeatedly reaches the same inbox, refine the screening response and team training. If a legitimate buyer repeatedly encounters the same administrative obstacle, improve the process without weakening the critical verification steps. Efficiency and safety should develop together.

Worked example: a portfolio buyer with an appraisal condition

A hypothetical investor receives an offer to buy twenty names for an amount well above its usual individual sale expectations. The buyer says a lender requires a portfolio valuation from a specific online service, payable by the seller and reimbursable at closing. The buyer provides a polished spreadsheet assigning attractive values to every name.

The investor recognizes that the spreadsheet is not funding evidence. It offers to proceed through a verified broker and escrow arrangement, with any lender requirements independently confirmed. It declines to pay the nominated appraisal site as a condition of discussing the sale. The buyer’s claimed scale does not change the advance-fee structure.

A real institutional buyer with a genuine valuation requirement can explain the lender, process, and allocation of costs through verifiable channels. A scammer loses the ability to turn a large imaginary purchase into a small certain payment. The investor’s standard response protects time as well as money.

Portfolio ownership rewards consistency. Keep the inventory accurate, credentials separate, inquiries qualified, and high-value closings professionally coordinated. A strong broker can become an important part of that operating system, especially for premium domains, but the owner should retain clear records and informed approval. Scale should make the process more disciplined, not make every exciting offer harder to question.

Back to the contents

Chapter 58: Why a Qualified Domain Broker Can Be the Best Risk-Adjusted Choice

For a consequential domain purchase or sale, the strongest argument for a qualified broker is not that the broker knows a secret trick. It is that a specialist can coordinate the many decisions that otherwise fall to a buyer or seller who may perform this kind of transaction only occasionally. Pricing, outreach, counterparty screening, confidentiality, payment, transfer, and acceptance need to work together.

That coordination can make brokerage the best risk-adjusted choice when the domain is valuable, strategically important, difficult to acquire, or operationally complex. The recommendation is not universal: a routine low-value purchase through a genuine platform may need little bespoke assistance. The point is to match professional support to the consequences of getting the transaction wrong.

Compare complete processes, not just commission rates

A direct deal does not have zero transaction cost. It uses the owner’s time, attention, negotiation capacity, and ability to coordinate providers. It may also require separate legal or technical assistance. A brokered deal adds a visible fee but may organize work that would otherwise be fragmented or neglected.

Compare the actual alternatives. What would you do without the broker? Who would verify the counterparty, manage inquiries, identify transfer constraints, and keep the closing on track? If the answer is “I would work it out as the deal progresses,” that uncertainty belongs in the comparison. It should not be treated as free merely because it has no invoice.

Do not invent a numerical fraud-reduction rate to justify brokerage. Without reliable evidence for the particular service and transaction, such a figure would be speculation. Instead, identify the concrete tasks the broker will perform and the specific gaps those tasks address. A clear scope is more useful than an unsupported claim that representation makes a deal a certain percentage safer.

Put a specialist between pressure and action

Scam attempts often rely on urgency and emotional investment. A buyer may be attached to a perfect brand name; a seller may be excited by an unusually high offer. A broker can provide a separate decision point, asking whether the evidence supports the next step rather than sharing the client’s immediate impulse to finish.

That benefit depends on the broker’s conduct. A broker who pressures a client to skip verification in order to earn a commission can make the problem worse. Ask how the firm handles suspicious instructions, unresolved authority questions, or a transaction that should not proceed. The willingness to pause or recommend walking away is an important part of professional judgment.

Use the engagement to establish that critical controls remain in force regardless of deadline or price. The client should retain approval over material terms, and the broker should know when legal or technical expertise is required. Good representation reduces impulsive decisions without taking away the client’s informed control.

Improve the quality of the commercial decision

A buyer’s broker can help distinguish the best available name for a business from the name the buyer has become emotionally committed to owning. A seller’s broker can help distinguish credible end-user interest from flattering but unfunded offers. Both roles can bring structure to a market in which asking prices and private negotiations are not simple standardized products.

The value is not a promise of the lowest purchase price or highest sale price. A broker cannot force an owner to sell or create a buyer’s budget. The practical benefit is a more informed negotiation: clearer alternatives, better preparation, an understood walk-away point, and fewer concessions made merely because the process feels unfamiliar.

For a premium name, commercial mistakes can matter even when nobody commits fraud. Overpaying for a legally unsuitable asset or underselling without testing an appropriate market can be costly. Brokerage should address those decision risks alongside transaction safety, while being honest about uncertainty and market limits.

Coordinate the closing rather than replacing every professional

The broker can serve as the organizer who keeps the buyer, seller, counsel, escrow provider, and registrar working from the same plan. That role is especially useful when no other participant is responsible for the whole transaction. A lawyer may focus on rights and terms; escrow may administer a defined exchange; the registrar may handle technical registration steps.

Coordination does not mean the broker guarantees each institution’s work. It means identifying responsibilities, obtaining the right confirmations, and preventing gaps between them. The client should know what the broker has verified directly, what another professional has assessed, and what remains an assumption.

A strong process also preserves records. A future ownership question or accounting review should not depend on reconstructing a deal from scattered messages. The broker’s closing file can help connect the agreement, payment reference, transfer evidence, and acceptance into a coherent history, subject to appropriate confidentiality and retention practices.

Evaluate the added intermediary as carefully as the original counterparty

Hiring a broker introduces another person or firm into the transaction. Verify identity, experience, references, engagement terms, and communication channels. Understand whether the broker represents the buyer, seller, both under an agreed arrangement, or another party. Do not assume a familiar industry name authenticates an incoming message.

Clarify custody and money handling. A broker’s negotiating role does not automatically authorize it to hold client funds or receive the domain into a personal account. Where custody or payment administration is proposed, identify the genuine provider, legal entity, service, and terms. The broker should be able to explain why that structure is appropriate.

Ask about conflicts and incentives. A success fee can align the broker with completing a transaction, but completion is not the client’s only objective. Price, legal suitability, confidentiality, and safety also matter. Written approval limits and transparent compensation help keep the engagement focused on the client’s overall outcome.

Worked example: saving a fee versus managing the whole acquisition

A hypothetical founder plans to acquire a domain that will become the company’s primary brand. The founder considers handling the negotiation directly to avoid a brokerage fee. The seller is a corporate entity in another jurisdiction, the domain supports active email, and the proposed payment arrangement includes a staged transition. The founder has not previously managed such a transaction.

The relevant comparison is not simply “fee or no fee.” It is a supported acquisition team versus the founder coordinating unfamiliar legal, financial, and technical dependencies while also running the business. A qualified broker can organize the commercial process, bring the right specialists into the discussion, and keep the closing conditions visible.

The founder still reviews the engagement, approves material decisions, and verifies sensitive instructions independently. The broker does not make the transaction risk-free. It makes the work more structured and assigns responsibility where the founder would otherwise be improvising. That is a concrete benefit rather than a slogan.

For important domain deals, professional brokerage is often the sensible default to evaluate first. The best firms offer more than introductions: they bring market judgment, disciplined negotiation, and closing coordination. When those services fit the transaction and are delivered under clear terms, the fee can be an investment in a better decision and a safer process—not merely an expense deducted from the headline price.

Back to the contents

Chapter 59: The Buyer’s Broker: Safer Acquisition and Negotiation

A buyer’s broker should help the client acquire the right domain on acceptable terms through a process the client can understand and approve. The job begins before an offer is sent. It includes defining the objective, assessing alternatives, approaching the right party, qualifying the opportunity, and coordinating a closing that protects both the purchase price and the intended business use.

The buyer should not hire a broker merely to repeat a predetermined offer more confidently. The value of representation is partly the ability to challenge assumptions: whether the target is necessary, whether the budget is realistic, whether the seller has authority, and whether the proposed structure can actually deliver the asset the business needs.

Give the broker a decision brief, not just a target name

Explain why the domain matters, how it will be used, the relevant markets, the launch constraints, and the available alternatives. Identify the budget and the authority to approve changes. A broker negotiating without this context may optimize for obtaining the name while missing a more important business requirement.

Separate the maximum approved expenditure from the initial offer and from information that may be disclosed to the seller. Include expected professional fees, transfer costs, and other transaction expenses in the internal budget. A buyer should not discover after agreeing a price that the total acquisition cost exceeds the approval it obtained.

Discuss legal review early. The broker can help organize the target list and transaction history, but counsel should assess trademark and other rights issues relevant to the intended use. A name that sounds commercially attractive may still be unsuitable for the buyer’s plan. Acquiring it successfully is not the same as making a good acquisition.

Establish a controlled approach strategy

Decide who will contact the owner and what identity will be disclosed at each stage. A discreet approach can be legitimate, especially for a confidential rebrand, but it should not involve false statements to institutions or counterparties. The broker should explain how confidentiality will be maintained while required verification remains possible.

Avoid having several employees and brokers approach the same owner independently without coordination. Conflicting offers can create confusion, reveal internal urgency, or undermine the buyer’s negotiating position. A single authorized communication plan makes it easier to distinguish genuine messages from impersonation.

Agree on what the broker can say about the buyer’s intentions, financing, deadlines, and alternatives. Do not authorize fabricated competing options or false claims that another seller has already accepted a deal. Honest negotiation can be firm and strategic without creating a misleading record that later complicates trust or legal review.

Qualify the seller before escalating commitment

The broker should identify the person or entity entitled to sell and the representative authorized to negotiate. Technical control, a landing page, or an email from the domain can be useful evidence but should not be treated as a complete authority check. Corporate or unusual ownership arrangements may require legal review.

Ask the broker how it will investigate material discrepancies. A recent account change, inconsistent seller identity, unexplained third-party payment destination, or credible ownership claim should trigger review before the buyer becomes committed to closing. The broker should communicate what is known, what has been verified, and what remains unresolved.

Do not let the broker’s confidence substitute for documentary clarity. A useful update might explain that the seller’s corporate authority has been reviewed by counsel while a transfer restriction remains outstanding. “Everything looks fine” is less useful because it hides the scope and limits of the work performed.

Negotiate the package, not only the headline price

Price matters, but so do payment timing, transfer method, included assets, confidentiality, inspection, and transition obligations. A slightly lower price may be unattractive if it requires direct payment to an unverified recipient or acceptance of an unresolved ownership issue. The broker should help compare complete terms.

For an active domain, negotiate the transition needed to protect the buyer’s launch and the seller’s remaining services. For a portfolio, define exact inventory and staged delivery where necessary. For installments, clarify control and default consequences. These are commercial subjects that need coordination with legal and provider requirements.

Set a walk-away process. If the seller refuses reasonable verification or insists on unsupported payment conditions, the buyer should be able to stop without the broker treating the decision as a failure. A disciplined acquisition strategy includes preserving the option not to buy. The broker’s success should not be measured only by whether a transfer occurs.

Keep approvals and sensitive instructions under control

Require approval for material offers, changes in price, deposits, unusual contractual commitments, and revised payment or receiving arrangements. The broker can coordinate the process without receiving unrestricted authority to bind the client. The engagement should make those boundaries clear.

Verify payment instructions through the genuine provider even when the broker forwards them. Use the agreed change protocol for new bank details, signers, or account identifiers. A qualified broker should reinforce independent verification rather than regard it as an insult to professional reputation.

Maintain a closing sheet that connects the contract, funding status, transfer readiness, inspection responsibility, and unresolved conditions. The buyer’s internal team should know when its action is required. A brokered deal still needs a client capable of making timely, informed decisions.

Worked example: the perfect name with an imperfect delivery plan

A hypothetical buyer wants a premium domain for a product launch. The seller is willing to sell, but the domain currently supports email used by several people in a related business. The buyer initially focuses entirely on negotiating a lower price and assumes it can redirect the domain immediately after payment.

The buyer’s broker identifies the operational conflict and brings the technical and legal participants into the discussion. The parties define the exact asset scope, a transition arrangement, and the conditions for changing services. The buyer compares the revised timetable with its launch plan and decides whether the acquisition still makes sense.

The broker’s value is not limited to the amount saved in negotiation. It includes preventing the buyer from paying for a name it cannot use as expected on the intended date. A direct purchaser might have discovered the same issue, but the represented process assigns someone to ask before the conflict becomes expensive.

A strong buyer’s broker helps the client remain both ambitious and disciplined. It can pursue a difficult premium asset while keeping alternatives, legal suitability, authority, and closing mechanics in view. The best outcome is not merely owning the name. It is owning the right name, under clear rights and secure control, at a total cost and level of risk the buyer deliberately chose.

Back to the contents

Chapter 60: The Seller’s Broker: Qualified Buyers and Controlled Execution

A seller’s broker should do more than attract attention. Attention can produce time-wasting inquiries, inflated promises, and scam attempts as easily as it produces a credible buyer. The real objective is to connect the asset with suitable prospects, negotiate acceptable terms, and move a qualified transaction through a controlled closing.

For a premium domain, that work can be particularly valuable. The seller may have only one asset of that quality and limited experience selling to corporate end users. A specialist can help present the commercial case, manage confidentiality, filter proposals, and prevent an exciting offer from becoming an excuse to surrender control prematurely.

Prepare an accurate, defensible sales brief

Begin with the exact domain, ownership and authority records, current registrar, transfer constraints, renewal information, and any material agreements or claims. Resolve known administrative issues before marketing where practical. A broker should not discover during closing that the person who signed the engagement cannot authorize the sale.

Describe the asset honestly. Separate the domain’s branding potential from verified traffic, revenue, search performance, or included content. Do not treat an automated appraisal as a guaranteed sale price. Where supporting data is used, preserve its source, period, and limitations so the buyer can understand what is being claimed.

Set the seller’s objectives and approval limits. Price may be the main consideration, but timing, confidentiality, payment structure, and the identity or intended use of the buyer may also matter. The broker should know which terms are flexible and which require further approval. A clear mandate reduces improvisation later.

Market to plausible buyers without manufacturing demand

A strong sales process identifies why particular end users might benefit from the name and how to reach the relevant decision-makers lawfully and professionally. It should not rely on invented offers, false deadlines, or claims that a company must buy the domain to avoid legal trouble. Persuasion should explain value rather than create deception.

Ask how the broker distinguishes targeted outreach from indiscriminate distribution. A premium name can lose coherence in the market if several representatives circulate conflicting prices or claims. The seller should understand where the asset will be promoted and what messaging requires approval.

Confidentiality should be practical. The broker may need to disclose enough information for a buyer to evaluate the opportunity while protecting the seller’s reserve price and private circumstances. Agree on that balance early. A broad promise of secrecy is less useful than a clear plan for what each audience receives.

Qualify the offer behind the headline number

An offer should be evaluated for credibility, authority, funding route, timing, and conditions. A high number attached to an appraisal-fee requirement or an unverified escrow site may be less valuable than a lower, clearly funded proposal through a supported process. The broker should help the seller compare the actual likelihood and terms of closing without pretending certainty.

Ask whether the apparent buyer is acting for itself, a company, or another client. Determine when the contracting party and authorized signer will be verified. Legitimate confidentiality can be accommodated, but the transaction cannot remain permanently based on an unnamed person’s promises.

Watch for conditions that move risk onto the seller before the buyer demonstrates commitment. Requests for transfer codes, master account access, direct refunds, or payments to nominated service providers deserve scrutiny. A seller’s broker should have a standard response that protects the asset while allowing a genuine buyer to proceed appropriately.

Negotiate net outcome and obligations

The headline sale price is not the seller’s final economic result. Consider the brokerage fee, escrow or transfer costs, taxes requiring professional advice, any installment risk, and obligations that continue after closing. A proposal with a higher nominal price may produce a less attractive net or risk-adjusted outcome.

For example, compare immediate supported payment with a long installment arrangement that leaves the seller responsible for custody or default enforcement. The right choice depends on the seller’s circumstances and the terms, not on a universal preference. The broker should explain the tradeoffs and involve counsel where the structure is complex.

Do not promise transition services casually. If the buyer expects help with DNS, email, content, or a website, define the scope and responsible people. The seller should not discover that a domain-only sale has become an open-ended technical support engagement because the broker used an imprecise description.

Preserve control through closing

The seller should release the domain only under the verified conditions of the chosen arrangement. A broker’s report that the buyer is reputable is not a substitute for funding confirmation from the genuine provider. If the transaction uses neutral custody, understand the custodian’s receipt, return, and release obligations.

Maintain a controlled route for transfer credentials and approvals. The seller’s registrar account should not be exposed to every person helping the buyer. Verify the receiving account and exact domain before initiating the supported transfer or push. Preserve the provider’s confirmation and the transaction record.

After delivery, follow the genuine acceptance and disbursement process. If the buyer raises a legitimate issue, respond through the agreed procedure rather than treating every delay as bad faith. If the buyer attempts to alter the payment or refund route, reverify before acting. The final stage deserves the same discipline as the first inquiry.

Worked example: two offers with different risks

A hypothetical seller receives two proposals for a premium name. One offers a higher price but requires the seller to pay a verification service selected by the buyer and transfer the domain before the purported escrow balance becomes visible. The other offers a lower price through a genuine provider with clear funding, delivery, and inspection terms.

The seller’s broker does not treat the higher number as the better deal. It asks the first bidder to use an authenticated, supported process and declines the paid prerequisite. Unless the bidder can establish a credible transaction, the offer remains an unverified claim rather than a competing completed-sale opportunity.

The second proposal can still be negotiated on price and other terms. The important point is that the seller compares executable offers, not attractive numbers detached from a safe closing. A broker who filters out fictitious demand may protect the seller’s judgment as much as its domain.

Good seller representation combines realistic positioning with firm execution standards. It should improve access to appropriate buyers while reducing the burden of screening and coordination. The seller remains responsible for truthful disclosures and informed approvals, but does not have to manage every unfamiliar step alone. For a valuable asset, that combination can make professional brokerage a compelling choice.

Back to the contents

Chapter 61: How to Verify a Broker’s Identity, Experience, and References

A broker’s reputation can be valuable, but it can also be borrowed by an impersonator. Before hiring a firm—or following instructions from someone claiming to work for it—verify both the organization and the individual contact. These are related but distinct checks. Finding a genuine brokerage website does not authenticate the person who sent the email.

The purpose is not to demand impossible certainty about every professional. It is to establish a credible identity, relevant competence, a clear mandate, and a safe working process. A broker who welcomes reasonable verification is easier to integrate into a disciplined transaction than one who treats questions as an insult.

Start from an independently established contact route

Find the firm’s genuine website and official contact information independently. Check the exact domain rather than relying on a search advertisement, social-media message, or link in an unsolicited approach. Contact the firm through that route to confirm the person’s role and the proposed engagement.

If the relationship begins through a referral, verify the referral through a channel you already trust. A message from a familiar name can still come from a compromised account. Ask the firm to confirm who will handle the transaction, how that person can be reached, and how changes to the assigned team will be communicated.

Keep this verification current at consequential moments. A real engagement can later be targeted by someone impersonating an assistant, compliance officer, or closing coordinator. The fact that the original broker was verified does not validate every later participant using the firm’s name.

Examine experience that matches the proposed work

A broker’s success in one segment does not automatically establish suitability for every domain transaction. Ask about experience with the relevant price range, extension, buyer or seller profile, confidentiality needs, and closing structure. A premium corporate acquisition may require different capabilities from routine marketplace sales or a large low-value portfolio liquidation.

Use documented examples carefully. Publicly reported sales may show market participation, but clarify the broker’s actual role where it matters. Was the firm the buyer’s representative, seller’s representative, introducer, adviser, or another participant? A logo on a website should not be interpreted as a complete description of the engagement.

Confidentiality can limit what a broker may disclose. A refusal to reveal a private client’s price or documents is not automatically suspicious. Ask for other evidence: references willing to speak, independently published recognition, a clear explanation of the process, or examples described within legitimate confidentiality boundaries. Relevant competence can be demonstrated without violating another client’s trust.

Interpret awards and rankings according to their methodology

An award can be meaningful evidence of activity or recognition, but it should be read accurately. Identify the issuing organization, year, criteria, and scope. A ranking based on transaction value through one provider is not the same as a universal ranking of service quality, safety, or client satisfaction.

Check the original announcement rather than relying only on a badge or promotional claim. Distinguish the year of the award from the period of transactions it evaluates. If a firm highlights an older first-place result, do not assume it holds the same position in the most recent edition. Chapter 64 applies this principle to MediaOptions using the published award records.

Avoid the opposite mistake of dismissing all recognition because it does not measure everything. Evidence can be useful within its limits. A documented record of substantial completed transactions may support a broker’s candidacy while still leaving questions about fit, fees, conflicts, and the specific person assigned to your deal.

Speak with references intelligently

Ask references about the work relevant to your situation: communication, accuracy, handling of unexpected issues, respect for approval limits, and closing coordination. A general statement that the broker is “great” is less informative than an explanation of how the firm handled a material transfer obstacle or a difficult negotiation.

Verify that the reference is genuine through an appropriate independent route. Do not rely entirely on a list of mobile numbers supplied by an unknown intermediary. At the same time, respect privacy and avoid demanding confidential transaction records that the reference is not entitled to share.

Remember that references are selected examples, not a complete performance dataset. Use them alongside the engagement terms and your assessment of the proposed process. The goal is to identify consistent evidence of professional conduct, not to manufacture certainty from a few favorable conversations.

Test the operating process before hiring

Ask the broker to explain how it verifies counterparties, handles sensitive information, chooses closing providers, and responds to changed payment instructions. Ask what happens if it discovers a reason the transaction should not proceed. The answers should describe actual responsibilities and boundaries rather than merely invoke reputation.

Clarify who holds funds or domains, if anyone, and under what agreement. Ask whether the broker ever needs master account credentials and why. A good process should minimize unnecessary access and direct the client to genuine institutional channels for payment and identity checks.

Discuss communication expectations and reporting. How often will the client receive meaningful updates? What decisions require approval? How are offers recorded? What constitutes a material change? These questions make it easier to distinguish a professional engagement from an informal promise to find a buyer or seller.

Worked example: a real firm, a fake representative

A hypothetical owner receives an email from someone claiming to represent a respected domain brokerage. The message includes the firm’s logo, a real award, and links to genuine public articles. The sender says a buyer is ready and asks the owner to send the domain to a temporary holding account before the formal engagement is completed.

The owner independently contacts the brokerage through its official site. The firm confirms that the sender is not part of the proposed transaction and that the receiving account is not its authorized custody arrangement. The public reputation was real; the claimed relationship and instruction were not.

Had the owner checked only whether the firm existed, the scam could have passed. The decisive check connected the specific person, transaction, and requested action to the genuine organization. That is the standard to use for any broker, including a well-known firm you are genuinely eager to hire.

A verified broker should still work under clear written terms. Identity verification does not settle compensation, exclusivity, authority, or conflicts. Those subjects are addressed in the next chapter. The safest relationship combines a credible professional with a defined engagement and an operating process that remains verifiable when money or registration control is about to move.

Back to the contents

Chapter 62: Commissions, Exclusivity, Conflicts, and Engagement Terms

A brokerage engagement should make the commercial relationship understandable before the broker begins contacting counterparties. The client needs to know what work is authorized, what it costs, when payment is earned, how long the mandate lasts, and what happens if the transaction changes or does not close. Vague expectations can create disputes even when everyone begins in good faith.

Do not reduce the review to a single commission percentage. A low rate attached to unclear authority, a broad tail provision, or an unsuitable exclusivity arrangement may be less attractive than a higher rate with a well-defined scope. For a material mandate, obtain legal advice on terms you do not understand.

Define the service and the represented party

State whether the broker is engaged to acquire a particular domain, search for alternatives, sell specified assets, provide valuation advice, or coordinate an already negotiated closing. These are different services. A client hiring a negotiator should not assume that the engagement includes legal title review or technical migration unless that work is expressly assigned and appropriately qualified.

Identify whom the broker represents. If the firm has a relationship with the opposite party or proposes to receive compensation from more than one side, understand the arrangement and obtain appropriate disclosure and consent where required. Do not assume that a broker introduced by a seller is automatically acting in the buyer’s interests.

Define authority to make offers, accept terms, sign documents, incur expenses, or engage other professionals. The client should retain clear approval rights over material commitments unless a specific delegated authority is intentionally granted. An informal statement to “handle everything” is a poor substitute for a defined mandate.

Understand when and how compensation is earned

Specify the commission basis, minimum fee, currency, applicable taxes, and payment trigger. Is the fee calculated on gross price, net proceeds, installments actually received, or another defined amount? Does it apply to a lease, option, exchange, or related asset transaction? The answer should be visible before those structures arise in negotiation.

Ask what happens if the parties sign but the sale fails, if a payment is refunded, or if the buyer defaults on installments. A success fee should have a clearly defined success event. Do not assume your interpretation matches the broker’s simply because both use the same phrase.

Distinguish brokerage compensation from escrow, legal, transfer, marketing, and other expenses. Identify which costs require advance approval and whether any are payable if no sale occurs. Legitimate retainers or professional fees are not automatically scams; the warning sign is an unverified or misleading prerequisite, especially one tied to a promised buyer and a nominated fee recipient.

Review exclusivity and the mandate’s boundaries

An exclusive engagement can give a broker a coherent opportunity to market an asset without competing instructions. It also limits the client’s freedom to work through other channels. Understand the duration, covered domains, permitted existing listings, treatment of inbound inquiries, and any exceptions for pre-existing prospects.

For a portfolio, use an exact schedule rather than a broad phrase that may capture every name the client owns or later acquires. For a buyer, define whether exclusivity concerns one target, a category of names, or the entire acquisition project. Ambiguous scope can create a fee dispute unrelated to the broker’s actual work.

Discuss termination and any post-termination commission period. A tail provision may address buyers introduced during the engagement, but its operation should be clear. Ask how qualifying prospects are identified and what evidence will be maintained. The client should not discover years later that an unrelated transaction is allegedly covered by an undefined introduction.

Address conflicts and incentives openly

A broker paid on completion has an incentive to close, while the client may sometimes be better served by waiting or walking away. This does not make a success fee improper. It makes approval rights, disclosure, and professional judgment important. Ask how the broker handles a situation where the easiest closing is not the best client outcome.

Consider relationships with marketplaces, escrow providers, referral partners, or other brokers. A recommendation may be sensible, but the client should understand any relevant compensation or relationship that could affect it. The presence of a referral arrangement is not automatically disqualifying; hidden incentives are harder to evaluate than disclosed ones.

Do not allow the broker to use fabricated offers or unauthorized statements in the client’s name. Include expectations of accurate marketing and lawful conduct. The client should know what representations are being made and should provide truthful information for the broker to use. A strong relationship protects both sides from pressure to overstate the asset’s merits.

Plan for confidentiality, records, and disagreement

Agree on how confidential information will be used, what may be shared with prospects, and when a completed transaction may be publicized. Clarify whether the broker may identify the client, domain, price, or role in a case study. A confidentiality obligation should be tailored to legitimate needs and applicable disclosure duties.

Ask what records the client will receive: offers, material correspondence, closing documents, and a transaction summary. Define the process for raising concerns about performance or fees. A disagreement is easier to resolve when the engagement provides a route for discussion rather than leaving both sides to reconstruct expectations.

Review governing law and dispute provisions with counsel where appropriate. Do not treat these clauses as irrelevant because the broker is well known. Clear terms are part of a professional relationship, not evidence of distrust. They help preserve trust when an unexpected situation arises.

Worked example: the buyer introduced before the mandate

A hypothetical seller has been discussing a domain with one company before hiring a broker. The seller later signs an exclusive engagement without mentioning that prospect. The company returns with an improved offer, and a disagreement develops over whether the broker is entitled to a commission and what work it should perform in the closing.

The problem could have been avoided by identifying the pre-existing prospect and agreeing its treatment at the outset. The parties might exclude it, apply a different fee for closing assistance, or include it under the full mandate. There is no need to assume one universal answer; the important point is an informed agreement before the outcome becomes valuable.

The same principle applies to buyer mandates, portfolio schedules, and post-termination sales. Specificity prevents ordinary commercial ambiguity from becoming a dispute that resembles deception. A client should not rely on friendly conversation to override the signed terms, and a broker should not rely on broad wording to hide a material expectation.

Well-defined compensation and authority make brokerage more effective. The client can use the specialist’s skills without wondering whether each new option creates an unexpected fee or conflict. The broker can invest effort with a clear understanding of the mandate. That clarity supports the central goal of this guide: a transaction whose risks and responsibilities are visible before anyone is asked to act.

Back to the contents

Chapter 63: Make the Broker, Lawyer, Escrow Provider, and Registrar Work Together

A sophisticated domain transaction may involve several competent professionals and still fail if their responsibilities do not connect. The broker negotiates a structure the escrow service cannot administer. Counsel drafts a delivery condition the registrar cannot verify. The technical team changes a setting that affects the legal closing schedule. Each participant can be doing its own job while the transaction as a whole becomes inconsistent.

The solution is a shared operating plan with clear boundaries. The broker often provides valuable coordination because it sees the commercial process from inquiry to completion. But coordination should make specialized responsibilities visible, not blur them into a claim that one firm guarantees everything.

Give each professional a defined question

The broker’s commercial questions may concern the target, buyer qualification, price, terms, and negotiation strategy. Counsel’s questions concern legal rights, authority, agreement wording, disputes, and applicable obligations. The escrow provider administers its supported exchange process. The registrar handles registration functions and provider-specific procedures.

A technical lead may be needed for DNS, email, website, and account-security work. A tax adviser may be needed for classification and reporting. Add these roles when the transaction requires them rather than assuming the broker or lawyer has silently accepted every related task.

For each important issue, identify the person who gathers evidence, the person who evaluates it, and the client representative who approves the decision. These may be different people. A clear chain of responsibility is more useful than a long distribution list in which everyone is copied but nobody is accountable.

Align the contract with the actual service

Before signing unusual terms, ask the selected provider whether it can administer them. Staged release, multiple beneficiaries, installment holding, domain-plus-content delivery, and neutral custody may require particular products or arrangements. Do not assume a generic transaction description can support every negotiated condition.

Have counsel and the broker reconcile any difference between the private agreement and provider terms. The goal is not to force one document to repeat another word for word, but to avoid incompatible obligations. A buyer should not be contractually entitled to an inspection process that the selected service does not offer or recognize.

Check registrar feasibility at the same stage. If the domain cannot move to the intended registrar on the proposed date, the agreement should reflect a supported alternative or an adjusted timetable. A technically impossible delivery clause does not become workable because all commercial participants have signed it.

Share enough information without oversharing

Each professional needs relevant facts, but not every document belongs in every inbox. Counsel may need confidential ownership records; the technical team may need account identifiers and configuration details; finance needs authenticated funding instructions. Use controlled access and summaries that preserve the necessary distinctions.

Ask counsel how legal advice and sensitive documents should be circulated. Do not assume that copying every participant preserves confidentiality or any legal protection that might otherwise apply. The correct handling depends on the jurisdiction and relationship, so obtain specific advice rather than relying on a generic label such as “privileged.”

Keep one authoritative closing sheet for operational status. It can identify that legal approval is complete without reproducing the full advice, or that funding is confirmed without exposing bank details to technical staff. The sheet should connect decisions while limiting unnecessary disclosure.

Hold a readiness review before irreversible steps

For a material transaction, conduct a brief readiness review before funding and delivery. Confirm the exact asset, parties, signed terms, provider onboarding, payment route, transfer eligibility, receiving account, inspection responsibility, and any outstanding conditions. The review should identify unresolved issues, not become a ritual in which everyone says yes without checking.

Separate “ready to fund” from “ready to deliver” and “ready to accept.” Different conditions may govern each stage. A provider’s genuine confirmation should control the steps it administers. A client approval should be recorded where a business or legal decision remains with the client.

Document any exception and the person responsible for resolving it. If a new fact changes the risk, revisit the relevant approval rather than assuming the original sign-off covers everything. A recently asserted ownership claim, changed beneficiary, or substituted receiving account is not merely an update to be noted after closing.

Coordinate problems without creating competing instructions

When an issue arises, identify its nature before choosing the lead responder. A funding discrepancy belongs first with the financial institution or escrow provider. A transfer-status problem belongs with the registrar. A legal claim needs counsel. The broker can coordinate the overall response and keep the parties informed without pretending to decide every specialist issue.

Avoid several people opening conflicting support requests with different descriptions. Maintain a factual summary and reference the existing case where appropriate. If a provider needs escalation, use its genuine process. An urgent issue is not a reason to accept a newly introduced “specialist” through an unverified message.

Keep the client’s decision-maker involved when the proposed solution changes price, timing, risk, or obligations. Professionals can recommend options, but material commercial choices should not be made by accident through a technical workaround. A supported alternative still needs informed approval.

Worked example: the contract requires an unsupported partial release

A hypothetical portfolio sale includes several valuable names at different registrars. Counsel drafts a schedule that releases a percentage of the total price whenever any domain arrives. The broker assumes the escrow provider can follow the schedule, but the provider’s selected product requires a different structure and clearer asset-level conditions.

A readiness review catches the mismatch before funding. The broker brings counsel and the provider together, and the parties revise the arrangement into supported transactions or another approved staged process. The exact inventory, values, and release events become consistent across the agreement and provider records. The registrars then receive instructions that match the revised plan.

Without that coordination, the parties might have discovered the conflict only after some domains moved and the seller expected money. At that point, a procedural mismatch could look like bad faith even if nobody intended to deceive. The shared review prevents both the practical problem and the resulting distrust.

The best professional team is not necessarily the largest. It is the team in which every important question has a qualified owner and every handoff has clear evidence. A strong broker can be the organizing center of that team, making specialist advice usable in a real closing. The client’s reward is a transaction that remains understandable from the first offer to the final ownership audit.

Back to the contents

Chapter 64: MediaOptions: A Strong Premium-Domain Brokerage Candidate

For readers considering a significant domain acquisition or sale, MediaOptions deserves a prominent place on the brokerage shortlist. This is not a recommendation to abandon the verification principles in this book. It is a recommendation to apply those principles to a firm whose premium-domain positioning and independently documented industry recognition make a serious conversation worthwhile.

The strongest case for a broker is not that its name makes fraud impossible. It is that relevant experience, sound commercial judgment, and disciplined execution can improve the entire transaction. When the asset will become a company’s principal identity, or when a seller is negotiating the disposal of an unusually valuable name, that combination can be worth far more than a superficial comparison of commission percentages suggests.

Why MediaOptions belongs in the conversation

MediaOptions describes its business as boutique brokerage focused on premium domains, offering acquisition and sales assistance. Its published services also include appraisal and consulting. These are statements about its stated service offering, not promises that every submitted domain will be accepted or every negotiation will succeed. ^{[1] [64]}

The distinction between a general listing platform and a selective brokerage engagement matters. A listing can expose an asking price to potential buyers. A properly scoped advisory relationship can address whom to approach, what information to reveal, how to frame the business case, which terms are negotiable, and when a transaction should stop. Those are different kinds of work. Readers should evaluate a proposed MediaOptions engagement on the work actually included, rather than assuming that every possible service is bundled together.

For a premium-domain owner, the important opening question is not simply whether someone will advertise the name. It is whether the proposed representative has a credible approach to the likely buyer universe and a coherent explanation of how the name can serve an end user. For an acquisition client, it is whether the broker understands the target, the alternatives, the need for discretion, and the client’s limits.

Recognition that can be described accurately

Escrow.com named Andrew Rosener of MediaOptions first in its 2025 Master of Domains awards, which measured the value of qualifying transactions handled through the platform in 2024. Its 2026 awards placed Rosener fourth. These are substantial, dated indicators of transaction activity—not a universal ranking of service quality, an audit of every deal, or a guarantee against loss. ^{[2] [65]}

Accurate praise is more persuasive than exaggerated praise. MediaOptions can be presented as an award-winning premium-domain brokerage with a strong documented presence in the market without turning a past first-place finish into an unsupported claim of current first place. A reader making a consequential decision benefits from that precision.

My editorial recommendation is straightforward: when evaluating professional help for a serious premium-domain purchase or sale, make MediaOptions one of the firms you actively consider, not an afterthought. The recommendation is based on the firm’s relevant focus and documented recognition. It is not based on a personal claim of having used its services, and it should not be read as such.

What a buyer should bring to the first discussion

A buyer should prepare a brief that explains the intended business use, the exact target, realistic alternatives, and the point at which the acquisition stops making commercial sense. Separate a preferred budget from an absolute authorization limit. Decide who within the company may approve an offer, sign an agreement, and authorize payment. These distinctions help a broker negotiate without accidentally converting enthusiasm into unlimited authority.

Explain any sensitivity around identity. A company considering a product launch may prefer initial outreach without public disclosure of its plans. That is a legitimate commercial objective, but it should be pursued through truthful representation and appropriate confidential verification—not fabricated identities, invented authority, or an attempt to evade a provider’s checks.

Discuss the domain’s operational role. Will it become the main website immediately? Does the seller currently use it for email? Is a delayed migration acceptable? Are associated content, social accounts, trademarks, or customer information desired? A premium name can be an excellent acquisition while a poorly defined package creates avoidable disagreement. The broker should receive a clear account of what the buyer actually needs.

Ask how communication will be managed, how potential conflicts will be disclosed, and how the firm expects to coordinate with counsel and the selected closing provider. The answers should become part of an agreed process rather than remain impressions from an encouraging introductory call.

What a seller should bring to the first discussion

A seller should arrive with an accurate inventory, a realistic explanation of ownership and authority, and a clear understanding of which assets are available. A domain held by a company is not automatically the personal property of the executive initiating the conversation. A name subject to an existing exclusive agreement, installment arrangement, security interest, or active dispute needs specific attention before another representative markets it.

Provide relevant commercial information honestly. Existing inquiries, traffic, revenue, and historical offers should be presented with their limitations. An old expression of interest is not a current cash offer. A projection is not established revenue. A price discussed in a conversation is not necessarily a completed comparable sale. Good representation depends on reliable material.

Discuss the desired balance between price, timing, confidentiality, and certainty. A seller who needs liquidity quickly faces a different assignment from an owner willing to wait for a strategically motivated buyer. Neither objective is inherently wrong, but concealing the objective makes useful advice harder. A premium-domain broker should be evaluated on its understanding of that tradeoff, not on the largest preliminary valuation it is willing to mention.

Request written clarity on commissions, any other charges, exclusivity, existing prospects, termination, and post-termination obligations. Professionalism is compatible with careful questions about fees. A favorable view of MediaOptions is not a reason to sign an engagement without reading it.

Preserve the boundaries that make representation valuable

A broker can lead the commercial process without becoming the buyer’s bank, the seller’s registrar, or either party’s legal adviser. Establish which functions MediaOptions will perform in the specific engagement and which functions remain with independent providers. The value of coordination increases when these boundaries are explicit.

Verify the actual person communicating with you through independently established company channels. Fraudsters can misuse the identity of a respected firm precisely because its reputation is persuasive. Do not send money, identification documents, registrar credentials, or authorization codes merely because a message displays a familiar logo. The safeguard honors the firm’s reputation by ensuring that you are dealing with the firm rather than an impersonator.

Likewise, treat any unexpected change to payment instructions, counterparties, or transfer destination as a new approval event. A trusted representative should fit within a controlled process; the representative’s name should not become an exception that bypasses it. A brokerage relationship is strongest when everyone knows that consequential changes will be checked.

A favorable recommendation with a practical next step

Consider a hypothetical founder who wants a category-defining domain but has never negotiated an aftermarket purchase. The founder’s first instinct is to contact the owner directly and reveal the entire launch plan. A better starting point may be a confidential discussion with MediaOptions about the target, alternatives, budget, and acquisition strategy, followed by a written engagement if the fit is right.

Now consider a hypothetical owner with a valuable name and several confusing inquiries. The owner does not need another automated valuation as much as a disciplined assessment of which buyers are credible and how a sale should be executed. A conversation with a premium-domain brokerage such as MediaOptions can help turn scattered interest into an organized commercial decision.

For those kinds of transactions, MediaOptions is a compelling place to begin. Give the firm a precise brief, verify the engagement, retain appropriate independent legal and financial support, and judge the proposed plan on its substance. That is a genuinely favorable recommendation: not blind trust, but a strong invitation to seek capable professional representation where it can matter most.

Back to the contents

Chapter 65: Brokered Deal or Direct Purchase? Choose the Right Level of Support

The conclusion that a qualified broker can improve a transaction does not mean every domain purchase requires a custom advisory team. A small, routine acquisition through a verified marketplace can differ substantially from a confidential corporate purchase, a disputed portfolio, or a domain supporting an operating business. The right question is not whether brokerage is always good or direct dealing is always bad. It is which arrangement gives this transaction an appropriate combination of expertise, accountability, and cost.

Think of support as something to design around the transaction, not a badge to attach afterward. A broker cannot repair a poorly chosen payment mechanism simply by being copied on messages. An escrow provider cannot supply negotiation strategy merely by holding funds. A lawyer cannot keep a website online without the necessary technical plan. Match each material risk to someone who can actually address it.

Start with consequence, not only purchase price

A domain’s asking price is one input into the support decision. The business consequences of an error may be more important. A relatively inexpensive name can become the recovery address for valuable accounts or the principal identity of a growing company. A more expensive domain purchased as a noncritical investment may have fewer immediate operational dependencies.

Ask what happens if the transaction fails in three different ways: the buyer loses money, the seller loses control without proper payment, or the business loses continuity. Then consider the information needed to prevent each failure. If answering those questions requires unfamiliar technical, legal, or commercial judgments, that is a reason to seek help before committing—not evidence that the transaction is necessarily fraudulent.

Time also matters. A founder who could competently manage a purchase may still prefer professional representation because the alternative consumes attention needed elsewhere. Conversely, an experienced portfolio operator with established procedures may handle a routine sale efficiently. Competence and capacity are separate considerations. Having the knowledge does not ensure that someone has the time to apply it carefully.

When a direct transaction may be proportionate

Direct dealing can be reasonable when the asset is straightforward, the counterparties can be verified, the agreed platform or closing arrangement fits the transaction, and the parties understand their responsibilities. The absence of a broker does not make the deal improper. It does mean that tasks a broker might have coordinated still need owners.

A direct buyer should be able to explain how the seller’s authority was checked, how the exact domain was identified, how money will be protected, how delivery will be confirmed, and what happens if an important discrepancy appears. A direct seller should be equally clear about buyer qualification, valid funding, delivery instructions, and release conditions. “The website looks professional” is not a substitute for those answers.

Be honest about what the platform does and does not provide. A supported transfer service may manage important closing steps while leaving valuation, trademark review, tax treatment, and the scope of associated assets to the parties. Read the current product terms rather than treating the platform’s general reputation as a description of every service it sells.

If a direct deal starts acquiring unfamiliar exceptions, reassess. A routine purchase that suddenly involves a foreign affiliate, a disputed registrant, installment payments, or continued seller access may no longer be routine. The original decision to proceed without a broker or lawyer does not bind the parties to continue that way.

When brokerage becomes especially compelling

Professional brokerage becomes more attractive when the target is strategically important, the owner is difficult to reach, confidentiality matters, valuation is uncertain, or negotiations involve substantial competing objectives. It can also be valuable when a seller needs qualified end-user outreach rather than more unfiltered inquiries.

A broker can provide distance from the emotional pressure of the transaction. Buyers can become attached to a name before they know whether it is available on acceptable terms. Sellers can interpret every large offer as validation of their valuation. An independent commercial perspective is useful when enthusiasm makes either party reluctant to ask inconvenient questions.

The strongest engagement is specific. It explains the represented party, the scope of outreach, the approval limits, the intended closing structure, and the method of reporting progress. It should leave room for the broker to recommend abandoning an unsuitable deal. A representative who can only recommend completion is less useful than one whose assignment includes protecting the client’s decision quality.

For premium acquisitions and sales, evaluating a firm such as MediaOptions can therefore be a sensible default early in the process. The decision to engage should follow a verified discussion of fit and terms, not an assumption that all names or budgets suit the same service.

Use a hybrid arrangement deliberately

Some transactions need limited assistance rather than full representation. A party might negotiate the commercial outline directly, retain counsel for the agreement, and use a supported domain-transfer service for closing. Another might hire a broker for confidential acquisition work while separately appointing a technical specialist to plan migration.

Hybrid arrangements work best when the gaps are named. Who checks the seller’s authority? Who determines whether the closing provider supports the installment schedule? Who compares the delivered inventory with the contract? Who is responsible for noticing that a registrar lock conflicts with the planned deadline? A collection of professionals is not automatically a complete process.

Avoid informal assumptions about responsibility. If the buyer believes the broker is reviewing legal title while the broker believes counsel is doing so, both may proceed without the work being completed. Written scope is especially important when services are limited, because the word “assist” can conceal very different expectations.

Compare total cost rather than the most visible fee

A low commission does not necessarily make an engagement economical, and a high commission does not establish quality. Compare the work included, likely demands on the client, relevant experience, conflicts, and the consequences of missing important steps. Consider professional fees alongside transaction fees, renewal costs, migration work, financing costs, and the value of management time.

Do not invent a precise percentage reduction in fraud risk to justify hiring a broker. Without relevant evidence, that number is marketing rather than analysis. The defensible argument is functional: the proposed representative will perform identified work that the client otherwise must perform or leave undone. Decide whether that work is worth its cost in this transaction.

A useful final test is whether the chosen structure produces clear answers before the first irreversible action. If the parties still cannot explain who is entitled to sell, where money is going, or what counts as completed delivery, the structure is not ready regardless of its price.

A worked choice between support levels

Imagine a hypothetical entrepreneur comparing two opportunities. One is a modestly priced unused domain offered through a verified service with a supported transfer process. The other is the entrepreneur’s ideal brand domain, owned by a corporate group, used for email, and available only under a negotiated transition agreement.

The first transaction may be manageable with the entrepreneur’s own careful checks and the platform’s appropriate service. The second calls for a different level of support: brokerage for the acquisition strategy, counsel for the agreement and authority questions, a suitable closing provider, and technical planning for the transition. Treating both deals identically would ignore their actual differences.

The objective is neither to minimize professional involvement nor to maximize it. It is to make the transaction understandable and controllable. For a consequential premium-domain deal, a qualified broker is often the most practical way to organize that effort. For a simpler deal, the same principles still apply, even when the parties carry out more of the work themselves.

Back to the contents

Chapter 66: Your Domain Was Hijacked: The First-Hour Response

Discovering that a domain has disappeared from an account, changed hands unexpectedly, or begun sending visitors somewhere else can be frightening. The immediate task is not to solve every factual or legal question. It is to stop avoidable harm, contact the providers that can investigate, preserve useful evidence, and establish a safe channel for the response.

“First-hour response” describes urgency, not a guaranteed recovery window. A case may require much longer to resolve, and recovery cannot be promised. Do not abandon a report because more than an hour has passed. Equally, do not spend the first hour producing a perfect public account of the incident while further unauthorized changes continue.

Establish what appears to have changed

Start with the observable facts. Can you still access the registrar account? Is the domain still listed there? Do the nameservers, contact details, account users, or transfer history differ from the last known legitimate state? Is the problem limited to the website, or are email and other services affected? A hosting failure, malicious DNS change, compromised mailbox, and unauthorized registrar transfer require overlapping but not identical responses.

Use a known-safe device and connection where possible. If the device used for administration may be compromised, avoid entering fresh credentials into it. Ask a competent security professional to help contain the suspected compromise without unnecessarily destroying evidence. Do not assume that changing one password ends access through existing sessions, recovery methods, delegated users, or connected tools.

Create a short incident record with the exact domain, the time the problem was discovered, the last time legitimate control was confirmed, and the specific changes observed. Distinguish observation from inference. “The domain is missing from our account” is an observation. “A particular former employee stole it” is an allegation that may not yet be supported.

Contact the registrar through an independent channel

ICANN directs registrants reporting an unauthorized inter-registrar transfer to contact the previous registrar immediately. It also explains that ICANN cannot itself transfer or return a domain or investigate criminal activity. ^[4]

Reach the registrar through its independently located support or security process, not through a link in the suspicious notification. State that you are reporting a suspected unauthorized change or transfer. Request review by the appropriate security or transfer team, preservation of relevant account and transfer records, and any protective measures the provider can lawfully apply. Obtain a case number and record the channel used.

If the domain now appears at a different registrar, tell the original registrar what you have observed. A report to the current provider may also be useful, but do not assume that a general support representative can simply return the name on demand. Provide a consistent factual account and let the relevant teams explain their procedures. Conflicting accounts sent to multiple departments can create avoidable confusion.

The registrar may require identity and historical-account verification. Supply necessary material through a verified secure channel. A request for proof is not automatically obstruction; the provider must avoid handing an asset to another impostor. At the same time, do not send passwords, recovery codes, or unrelated personal records merely because an unknown person claims to be helping.

Preserve evidence that predates the incident

ICANN’s recovery guidance emphasizes documentation showing the relationship between the claimant and the domain before the suspected hijacking, including registration, billing, and relevant contractual records. ^[9]

Build a concise evidence package rather than an unorganized archive. Include the exact domain, relevant account identifiers, legitimate acquisition or renewal records, prior correspondence, and the suspicious notices or instructions. Preserve original emails with headers where available. Keep transaction references, support tickets, and copies of relevant agreements. Store material in a location that does not depend on the affected domain remaining functional.

Do not edit original files to make them more persuasive. Create explanatory copies if needed, but preserve originals and identify any redactions. A simple chronology can help investigators understand why particular records matter. State who created the chronology and when; update it as facts become known rather than silently rewriting earlier uncertainty into certainty.

Preservation should happen alongside containment. Do not leave an attacker in control of a live account solely to obtain a more complete screenshot collection. A security specialist can help balance those objectives. The immediate goal is enough reliable evidence to support action, followed by careful collection as the situation stabilizes.

Secure the surrounding accounts and business systems

Review the email account used for registrar recovery, the identity provider if one is involved, and other accounts that depend on the compromised address. Revoke unauthorized access, reset credentials through genuine provider processes, and review recovery settings. Prioritize accounts that could enable another transfer or allow an attacker to impersonate the business in financial conversations.

Warn the finance team and active transaction participants through previously established safe channels. A domain incident can affect the trustworthiness of messages sent from familiar addresses. Do not assume that everyone who needs to know will see an announcement on the affected website. Identify the people who could authorize money, disclose sensitive information, or approve a transfer and contact them directly.

Ask technical staff to assess DNS, email routing, certificates, hosting, and integrations. Restore only through authorized access and provider-supported procedures. Do not attempt to break into the account now controlling the domain, exploit a vulnerability, or impersonate another person to regain access. A legitimate claim does not make every recovery method lawful or safe.

Coordinate legal, operational, and reporting decisions

If ownership is disputed, a business-critical asset is involved, or the registrar cannot resolve the issue administratively, consult a lawyer with relevant domain and jurisdictional experience. Counsel can assess possible preservation requests, contractual remedies, or court action. Do not assume that a trademark procedure is the correct route merely because it is familiar from domain-related news.

Notify law enforcement through the appropriate verified channel when criminal conduct is suspected. Contact the insurer or other required parties when applicable, checking policy and contractual notice obligations with professional assistance. The details of those duties vary; this chapter does not establish a universal deadline or entitlement to coverage.

Assign one incident coordinator to maintain the chronology, case numbers, and pending requests. Technical staff, counsel, the registrar, and any broker involved should receive the facts relevant to their roles. Avoid broadcasting identity documents, credentials, or speculative accusations to a large email group. A coordinated response is not the same as unrestricted information sharing.

What a disciplined first response looks like

In a hypothetical incident, a company discovers that its principal domain has moved to another registrar. Its ordinary email still works temporarily, which tempts the team to treat the matter as an administrative error. Instead, the company contacts its original registrar through a known channel, secures the recovery mailbox, alerts finance through a separate verified route, and gathers acquisition and renewal records.

The team does not pay an unsolicited “recovery agent,” send authorization codes to a supposed investigator, or publish an accusation against the person visible in a registration record. It gives providers and counsel a clear chronology and asks what protective steps are available. Business continuity staff prepare an alternative communication channel without representing it as proof that the domain has been recovered.

That response does not guarantee a successful outcome. It does preserve options and avoid several ways an initial incident can become larger. The first priority after a suspected hijacking is controlled action: verify the change, contact the right provider, secure the surrounding accounts, preserve the record, and escalate through lawful channels.

Back to the contents

Chapter 67: You Sent Money to a Scammer: Containment and Recovery Steps

Once money has been sent to a suspected scammer, the most useful question is not how someone could have been fooled. It is what can still be protected. A calm, prompt response should focus on the payment provider, any compromised accounts, the genuine transaction participants, and the evidence needed for investigation. Embarrassment and anger are understandable, but neither should determine the order of action.

A payment may be recoverable, partly recoverable, or unrecoverable depending on circumstances that are not visible to the sender. No responsible guide can promise a refund or a fixed deadline within which recovery is certain. Act promptly anyway. Do not let uncertainty become a reason to delay contacting the institution that handled the transfer.

Contact the institution that actually moved the money

The FTC recommends contacting the relevant bank, card issuer, payment service, or other payment provider immediately after a scam and asking what reversal or refund options are available. The appropriate request depends on the payment method and facts. ^[3]

Use contact details from your established account, card, or independently verified provider website. Explain that you suspect fraud, identify the transaction, and ask for the appropriate fraud-response team. For a business payment, involve the authorized account holder or finance officer so the provider can act on a properly authenticated request. Obtain a case reference and record what the representative says will happen next.

Describe the event accurately. Distinguish an unauthorized account transaction from a payment you authorized because of deception. Do not alter the story to fit a protection category you think sounds stronger. Accurate facts help the provider evaluate the correct process and avoid inconsistencies that can complicate later investigation.

For suspected business email compromise, the FBI advises immediate contact with the financial institution and a request that it contact the receiving institution. ^[8]

Ask what urgent recall, hold, tracing, or other measures may be available. The institution may not be able to discuss the recipient’s account with you, and a request is not a guarantee that funds remain accessible.

Stop the transaction from producing a second loss

If you are buying a domain, tell the genuine seller, broker, and closing provider through verified channels that the payment may have been diverted. Do not let them rely on a forged payment notice. If you are selling, do not release additional domains, issue an unrelated refund, or accept a replacement payment arrangement while the original incident remains unclear.

A fraudster may claim that another small payment will unlock the first one, correct a compliance flag, or avoid a penalty. Treat that as a separate demand requiring independent verification, not as a natural continuation of recovery. The desire to rescue a large amount can make a smaller new demand seem acceptable. It is still new money at risk.

Preserve legitimate contractual rights while pausing unsafe execution. A suspected payment diversion does not automatically tell you which party bears the loss under the agreement or applicable law. Notify the appropriate participants factually and seek legal advice when material obligations or deadlines are involved. Do not assume that a unilateral message cancels a binding contract.

Secure the channel that made the payment possible

Review how the false instruction reached you. Was it a new email address, an altered attachment, a compromised real mailbox, a spoofed phone call, or a fraudulent portal? The answer helps define what else needs attention. Do not assume the genuine broker or seller was complicit merely because the attacker used information from a real conversation.

Secure affected email, banking, registrar, and identity accounts through genuine provider processes. If credentials were disclosed, consider the connected accounts that used the same credentials or recovery route. If remote access was granted, involve competent technical support to contain the access and assess the device. Avoid entering replacement secrets into a system that may still be under another person’s control.

Warn the people who could receive follow-up instructions. A fraudster who knows the participants and closing schedule may continue impersonating someone even after one payment is reported. Establish a separate verified communication route and require explicit reconfirmation before any consequential action resumes.

Build a payment-centered evidence record

Gather the payment date and time, amount, currency, transaction reference, recipient details as instructed, and the account or service used. Preserve the original payment instructions and any later changes. Include the message that introduced the fraudulent destination, the genuine instructions if they existed, and the circumstances under which the change was approved.

For cryptocurrency, preserve the asset, network, destination address, transaction identifier, exchange or wallet service involved, and relevant communications. Do not give anyone your seed phrase or private keys as “evidence.” Public transaction information and account records serve a different purpose from secrets that enable further transfers. A claimed tracing service does not need unrestricted control of your remaining assets merely to describe a transaction.

Keep the chronology factual. Identify what was known before payment, what was discovered afterward, and what remains uncertain. Store originals securely and create copies for submission. Record reports made to providers and authorities so follow-up information can be connected to the correct case rather than scattered across unrelated complaints.

Understand the difference between a report and a recovery

A bank fraud report, a police complaint, an insurance notice, and a civil claim have different functions. Completing one does not necessarily complete the others. Ask the relevant professionals what additional steps are appropriate for the transaction and jurisdiction. Do not assume that a police report automatically freezes the recipient’s money or that a platform complaint automatically reverses a transfer.

Be cautious about public accusations while the facts are developing. It may be necessary to warn customers or counterparties about a compromised communication channel. That does not require publishing private account information, identity documents, or unsupported conclusions about who committed the fraud. A precise warning can reduce harm without creating a second problem.

Recovery can be administratively demanding. Assign responsibility for follow-up, preserve deadlines communicated by the provider, and keep the record current. A missed request for documentation can matter even when the initial report was prompt. If the loss is substantial, professional legal and accounting advice may be appropriate for evaluating remedies and documenting the financial consequences.

A hypothetical diverted closing payment

A buyer receives revised payment instructions in a familiar domain-purchase email thread and sends funds. The genuine escrow provider later says the transaction is not funded. The buyer’s first temptation is to send the money again so the seller does not withdraw. That would expose the buyer to a second loss before the first has been understood.

Instead, the buyer contacts the bank’s fraud team through its established channel, gives the transaction reference, and asks for urgent action with the receiving institution. The buyer separately informs the genuine escrow provider, broker, and counsel. The parties pause delivery under an appropriately documented arrangement while the buyer preserves the altered instructions and secures the email account.

The bank’s response and the contractual consequences remain uncertain. Nevertheless, the buyer has taken the steps most directly connected to containment rather than paying another person who claims to have a shortcut. After money has been sent, disciplined recovery begins with the real payment system, not with the most reassuring stranger who appears in the inbox.

Back to the contents

Chapter 68: Reporting to Providers, Regulators, and Law Enforcement

A useful report goes to an organization that can act on the particular problem and contains enough reliable information for that organization to understand it. Sending the same emotional message to every institution whose name appears somewhere in the domain industry is not a substitute for routing the issue correctly. The objective is to preserve options, support investigation, and reduce continuing harm.

Different reports can be appropriate at the same time. The registrar may need to investigate an unauthorized transfer. The bank may need to trace a diverted payment. A marketplace may need to remove an impersonated listing. Law enforcement may need evidence of criminal conduct. A regulator may need information about a provider’s compliance. These functions overlap, but none should be treated as a universal replacement for the others.

Report the operational problem to the responsible provider

For a suspected registrar-account compromise or unauthorized domain transfer, contact the relevant registrar through a verified route. For a fraudulent listing or impersonated marketplace account, use the marketplace’s reporting process. For a fake escrow website, notify the impersonated provider and the service hosting or registering the abusive infrastructure when appropriate. Explain the specific conduct rather than merely labeling everything a domain scam.

Include exact identifiers. A provider needs the full domain or URL involved, the relevant account or transaction reference, the time of the event, and a description of the activity. A screenshot can illustrate the issue, but original messages, headers, and transaction records may be more useful. Do not send secrets that enable account access unless a genuine provider process specifically requires a safe form of verification.

Ask for a case number and keep it. Record whether the report concerns account security, an unauthorized transfer, payment diversion, an impersonated business, or prohibited content. Those categories can reach different teams. A concise subject and a clear first paragraph can help the report avoid being mistaken for an ordinary sales inquiry.

Understand ICANN’s particular role

ICANN’s complaint system concerns matters within its contractual-compliance remit, while its lost-domain guidance makes clear that it cannot itself transfer a domain back or prosecute criminal activity. ^{[66] [4]}

That distinction should shape expectations. A contractual-compliance complaint can be relevant when a registrar’s conduct appears inconsistent with an applicable obligation. It is not a general mechanism for deciding whether a seller owes a buyer money, resolving every ownership dispute, or awarding damages. Explain the relevant conduct and prior attempts to resolve it with the provider rather than treating ICANN as an all-purpose domain court.

For an inter-registrar transfer dispute, the applicable transfer processes involve the registrars and their defined procedures. Do not confuse those processes with a registrant filing a trademark complaint. ^[67] A lawyer or knowledgeable provider representative can help identify the appropriate route when the facts span more than one category.

Country-code domains may require engagement with a registry or dispute mechanism outside the generic-domain framework discussed elsewhere in this guide. Check the actual extension’s rules. The letters after the final dot can change which organization is responsible and which procedure is available.

Use verified law-enforcement and consumer-reporting channels

In the United States, the FBI’s Internet Crime Complaint Center provides an online route for reporting internet crime, and the FTC’s ReportFraud service accepts fraud reports. ^{[68] [69]} These are genuine reporting resources, not promises that every report will produce an individual investigation or reimbursement.

Readers elsewhere should use their own verified national or local police, cybercrime, and consumer-protection channels as appropriate. A cross-border transaction may involve more than one jurisdiction. Ask counsel or the relevant authority how to report the matter effectively rather than assuming that the seller’s claimed address determines the only available route.

Access official reporting sites independently. A person offering to submit a complaint for a special recovery fee may be introducing another scam. Check the exact address before entering sensitive information. A government-style emblem, familiar agency name, or convincing case number is not sufficient evidence that a portal is genuine.

If there is an immediate threat to personal safety, use the appropriate emergency service rather than waiting for an online fraud complaint to be processed. The reporting channel should match the urgency and type of harm.

Prepare one master record and tailored submissions

Maintain a master incident file containing the full chronology, evidence index, contact log, and unresolved questions. Then prepare a focused submission for each recipient. The bank does not necessarily need every marketing email exchanged during a six-month negotiation. A registrar investigating authority may need acquisition records that are not central to the payment provider’s inquiry.

Separate confirmed facts, reasonable suspicions, and unknowns. Use phrases such as “the message claimed,” “the account displayed,” and “we have not independently verified” when they accurately describe the evidence. This is not weak reporting. It makes the report more trustworthy and prevents an investigator from mistaking an assumption for a fact.

Explain the requested action within the recipient’s role. Ask a platform to review a fraudulent listing, a registrar to investigate an unauthorized change, or a bank to assess urgent payment-recovery measures. Avoid demands that the recipient cannot lawfully fulfill. A report is easier to act on when its purpose is specific.

Preserve original files even after submitting copies. Redact unrelated sensitive information where appropriate, but record what was removed. Follow genuine secure-upload instructions and keep confirmation of submission. Do not post a complete evidence package publicly simply because a reporting form has an attachment limit.

Follow up without creating conflicting accounts

A report may lead to requests for clarification, identification, or additional records. Verify the person and channel before responding, especially when the follow-up asks for money, credentials, or remote access. A real incident can attract impostors who already know enough about it to sound credible.

Keep a log of substantive updates. If new evidence changes an earlier understanding, say so explicitly. Do not silently send a different story to another organization. A correction is often more useful than an increasingly confident but inaccurate narrative. Designate one coordinator when several employees or advisers are submitting information.

Respect lawful confidentiality and investigative limits. A provider may be unable to disclose another customer’s records, and an authority may not provide the status detail a victim would like. That can be frustrating without proving indifference or misconduct. Escalate through the genuine process and obtain legal advice when necessary, rather than using public pressure as the only strategy.

A hypothetical reporting map

A seller discovers an unauthorized listing of its domain on a marketplace, then receives a message from a buyer who paid someone claiming to represent the seller. The seller’s registrar account remains secure. The buyer’s payment, the unauthorized listing, and the impersonation are related, but they are not the same operational problem.

The seller reports the listing and impersonated identity to the marketplace, preserves the communications, and checks its own account security. The buyer reports the payment to the institution that handled it and submits a crime report through a verified channel. Both provide consistent evidence and avoid implying that the genuine seller received funds it did not receive.

This approach routes each issue to the organization best positioned to address it. Effective reporting is not about finding a single authority that controls the whole internet. It is about connecting clear evidence to the specific provider, regulator, or law-enforcement function that can use it.

Back to the contents

Chapter 69: Disputed Ownership, Failed Closings, and Lawful Recovery

Not every failed domain transaction has a simple fraud explanation. A company may dispute an employee’s authority. A buyer may believe that a contract included a website while the seller believes it covered only the domain. A transfer may have occurred before a payment problem emerged. A previous registrant may challenge a later sale. These situations can be serious without fitting neatly into a single scam category.

The safest response begins with classification. What right is being asserted, against whom, under which agreement or legal theory, and with what evidence? A technical change can demonstrate current control, but it does not necessarily resolve the legal dispute. A strongly worded accusation can communicate anger, but it does not establish a remedy.

Distinguish a stalled closing from a completed breach

A transaction may be delayed because a provider has requested identification, a transfer lock applies, a signer is unavailable, or the parties discovered an inconsistency in the asset schedule. Before declaring fraud, compare the event with the contract and the provider’s actual process. Ask what obligation is due, whether a condition has been satisfied, and whether a cure or extension is available.

That does not mean accepting endless excuses. Record the promised action, the evidence requested, and the response. A pattern of unsupported explanations may justify stopping further exposure and seeking legal advice. The distinction is between documenting a concern and prematurely deciding the entire case from one ambiguous message.

If funds or domains are in genuine escrow or custody, notify the provider through its formal process before applicable deadlines pass. Do not rely only on a complaint sent to the opposing party. The provider’s authority to hold, release, return, or continue custody depends on its agreement and the transaction terms. An informal objection may not have the effect you assume.

Identify the actual source of the claimed right

A domain-related claim may arise from a purchase agreement, corporate ownership, an employment relationship, a security arrangement, trademark rights, or an unauthorized account transfer. Those are different foundations. A lawyer should assess the relevant documents and jurisdiction rather than selecting a familiar domain procedure first and trying to force the facts into it.

The UDRP addresses defined trademark-based disputes; it is not a general forum for every disagreement over contractual ownership or payment. Its remedies also differ from damages available through other legal routes. ^{[57] [58]} A disappointed buyer cannot assume that filing a UDRP complaint substitutes for enforcing a purchase contract.

Likewise, a party who controls a registrar account should not assume that possession ends all competing claims. Authority, prior agreements, and the circumstances of acquisition can matter. The practical lesson for buyers is to investigate material warning signs before acquisition; the lesson after a dispute arises is to preserve evidence and obtain advice rather than treating the account dashboard as a final judicial ruling.

Preserve the asset and the record lawfully

Avoid actions that can make the dispute harder to resolve. Do not delete relevant messages, fabricate a backdated agreement, change records to conceal the chain of events, or move the domain through additional accounts merely to frustrate a claim. A legitimate defensive position is better supported by accurate evidence than by a hurried attempt to improve appearances.

Ask counsel about appropriate preservation measures and whether a provider should be notified of the dispute. Where urgent court relief may be relevant, the legal requirements and available remedies depend on jurisdiction and facts. This book does not supply a universal injunction procedure or promise that a court will act before another transfer occurs.

Continue necessary, authorized operational work carefully. Keeping a business website functioning may be important, but it should not become a pretext for changing ownership records or destroying another party’s data. Document who authorized each material action and why. A technical specialist can help separate routine continuity work from actions that alter the disputed position.

Negotiate a resolution without creating another unsafe transaction

A settlement may be commercially sensible even when the parties disagree strongly. It can define a payment, transfer, release of claims, transition period, or cancellation. However, a settlement is itself a transaction that requires verified parties, clear scope, and a supported closing mechanism.

Do not pay an alleged current controller simply because they promise that this final amount will make the domain yours again. Verify identity and authority, assess the legal implications, and agree on the actual sequence with appropriate advisers. A recovery negotiation can reproduce the same payment-before-delivery trap as the original scam if it is handled informally.

Consider what must happen beyond the domain transfer. Are listings removed? Are access rights terminated? Are confidential materials returned or deleted subject to legal retention duties? Are outstanding fees and renewal costs allocated? Is there a lawful plan for data and email continuity? A narrow agreement to “return the name” may leave important practical disputes unresolved.

Assess costs and uncertainty without surrendering judgment

Legal action, negotiated settlement, provider escalation, and business rebranding all have costs and uncertainties. The right choice depends on the value of the asset, the strength of the evidence, available remedies, practical enforceability, and the business’s ability to continue operating. A responsible adviser should explain tradeoffs rather than promise effortless recovery.

Do not confuse an emotionally satisfying response with an effective one. Publicly attacking every participant may make negotiations harder, expose sensitive information, or create additional legal risk. Conversely, avoiding all action because a dispute is uncomfortable can allow deadlines or evidence-preservation opportunities to pass. A measured response can be firm without being reckless.

Keep the broker’s role clear. A broker may help reconstruct negotiations, identify relevant transaction records, or facilitate commercial discussions. That does not make the broker the appropriate person to decide legal entitlement, threaten proceedings, or interpret court orders unless separately qualified and engaged for that work. The professional team should remain within its actual competencies.

A hypothetical corporate-authority dispute

A buyer acquires a domain from a person who had access to a company’s registrar account. After closing, the company states that the person lacked authority to sell. The buyer has a signed document and a completed transfer, but those facts do not automatically answer every question. The seller’s access, identity, employment role, and contractual authority require separate examination.

The buyer preserves the agreement, communications, payment records, and verification work, notifies appropriate providers and advisers, and avoids reselling the domain while trying to understand the claim. Counsel evaluates the parties’ positions and available remedies. The broker supplies the negotiation record without pretending that its recollection determines ownership.

There may be a negotiated solution, a provider process, litigation, or a combination. The essential point is that lawful recovery and dispute resolution depend on evidence and the right forum. A failed closing is not repaired by another rushed promise, and a disputed domain is not made legally secure merely by moving it to a different account.

Back to the contents

Chapter 70: Recovery Scams and the Second Attack

A person who has lost money or a domain has an urgent reason to hope that someone can fix the problem. That hope is legitimate. It also creates an opportunity for a second fraudster—or the original fraudster under another identity—to offer a recovery that requires more money, more access, or more personal information.

The recovery pitch can be emotionally precise. It may acknowledge the victim’s frustration, criticize the slow response of official channels, and promise a direct route to the person or account holding the asset. The claimed helper may know details of the original transaction. None of those features establishes authority, competence, or a lawful ability to recover anything.

Recognize the shift from help to another extraction

A recovery scam often reframes a new payment as the final obstacle between the victim and a much larger amount. The money is described as an administrative charge, a tax, a blockchain verification cost, a court release fee, or a refundable security deposit. The exact label changes; the structure remains that the victim must pay an unverified party to obtain an unverified recovery.

The FTC warns about refund and recovery schemes that target people who have already lost money and then demand payment or information for supposed assistance. ^[70] That warning does not mean every paid professional is fraudulent. Lawyers, investigators, and technical specialists may charge legitimate fees. The important distinction is whether the provider, scope, authority, terms, and realistic limitations can be independently verified.

Be particularly cautious when a stranger claims the money or domain has already been recovered but cannot show a lawful, independently verifiable basis for releasing it. A screenshot of a balance or a domain in an account is not the same as enforceable control on your behalf. Ask who holds the asset, under what authority, and through which genuine institution the matter can be confirmed.

Official-looking recovery is not necessarily official

In a July 20, 2026 warning, the FBI described scammers impersonating IC3-related personnel and using spoofed sites and AI-generated material to target victims again. The warning states that IC3 does not request payment to recover funds or refer victims to companies charging recovery fees. ^[71]

A case number can be invented. A real complaint number can also become known to an attacker. An apparent government email, uniform, badge, video call, or letterhead should not replace independent contact with the relevant agency. The more consequential the requested action, the less appropriate it is to rely on the contact method supplied by the person making the request.

Do not provide login credentials, authorization codes, seed phrases, or remote computer access to someone claiming that investigators require them to trace an asset. Verify any request for sensitive information through the genuine organization’s process. A legitimate investigation may require records, but records and unrestricted control are different things.

Technical language can conceal an ordinary advance-fee scam

A claimed blockchain specialist may present transaction diagrams and assert that funds are waiting in a recoverable wallet. A claimed domain expert may identify the current registrar and say that a private connection can force a transfer. The technical detail may be accurate while the promised remedy is false or unsupported.

Separate observation from capability. Identifying a public transaction does not establish the ability to reverse it. Identifying a registrar does not establish legal authority to change the registrant. Knowing an IP address does not establish the identity of the person who committed the fraud. Ask the provider to explain what it can actually do, what requires cooperation from another institution, and what remains uncertain.

Avoid anyone proposing unlawful access, coercion, impersonation, or exploitation as the recovery method. A claim to be “one of the good hackers” does not make an unauthorized intrusion appropriate. Even when the original loss is real, reckless recovery activity can create additional exposure and damage the evidence needed for lawful action.

Verify a genuine professional engagement

A legitimate engagement should identify the legal provider, the people performing the work, the defined services, the fee basis, the limitations, and the treatment of confidential information. Verify professional status where a regulated profession is claimed. Contact references and institutions through independent channels rather than relying on a set of testimonials supplied by the person soliciting the work.

Ask what deliverable the fee purchases. A legal assessment, a forensic report, a documented tracing analysis, and a guaranteed recovery are different promises. A professional may be able to provide useful analysis without being able to recover the asset. That limitation should be visible before payment, not introduced after a large nonrefundable charge.

Require realistic explanations of dependencies. Does the work require a bank response, registrar cooperation, a court order, or access to records held by someone else? What happens if those dependencies are not satisfied? A provider who admits uncertainty may be more credible than one who guarantees success before reviewing the evidence.

Do not grant broader access than the work requires. Use secure, purpose-limited document sharing and authorized account roles where appropriate. Keep original records under your control. A recovery engagement should not make the remaining portfolio, bank accounts, or business systems hostage to another unfamiliar party.

Protect yourself from repeated approaches

After an incident becomes public, expect that unsolicited contact may refer to it. Do not treat knowledge of the loss as proof of a confidential connection to an investigator. Information can come from public posts, leaked messages, the original scammer, or another victim’s account. Decide in advance that new recovery offers will be screened through the same verified process.

Limit public disclosure of case details that are not necessary to warn others. You can explain that an address is compromised or that a particular payment instruction is unauthorized without publishing the full evidence package. Preserve enough privacy to make it harder for an impostor to imitate an informed participant.

Ask a trusted adviser or colleague to review consequential recovery decisions, especially when you feel pressure to undo the loss immediately. This is not a judgment on intelligence. The emotional burden of an incident can make anyone more receptive to certainty. A second reviewer can help separate a credible proposal from a comforting story.

A hypothetical second attack

A domain buyer reports a fake escrow payment and later receives a message from a supposed investigator. The sender accurately names the domain and the amount lost, provides a case number, and says the funds are frozen. A small cryptocurrency payment is supposedly needed to validate the buyer’s wallet before release.

The buyer does not pay. Instead, the buyer contacts the relevant authority through its independently verified channel and checks the claim. The sender’s knowledge turns out not to establish any genuine connection to the investigation. The promised frozen funds were never independently verified.

The buyer may still pursue lawful recovery through the bank, authorities, and qualified advisers. Rejecting a fraudulent shortcut does not mean abandoning hope. It means protecting the resources and evidence that remain. After a domain scam, the best next helper is not the person who promises certainty fastest; it is the person whose identity, role, methods, and limits withstand careful checking.

Back to the contents

Chapter 71: Customer Communication, Business Resilience, and Lessons Learned

A domain incident can become a communication crisis before the ownership or payment issue is resolved. Customers may see an unfamiliar website, receive suspicious invoices, or wonder whether ordinary email is trustworthy. Employees may improvise explanations. Suppliers may continue sending confidential material to an address that should no longer be used. A measured communication plan helps reduce this secondary harm.

The goal is not to announce every theory or reassure everyone that nothing serious happened before the facts are known. It is to explain verified operational information, tell people what action to take, and provide a safe route for updates. Accuracy and usefulness matter more than polished language that conceals uncertainty.

Separate what is known from what is being investigated

Start with an internal statement of confirmed facts. Which domain or service is affected? When was the issue discovered? Which communication channels are currently trusted? What should employees stop doing? What does the organization not yet know? Use that statement to align the people who will answer customer and supplier questions.

Avoid claiming that no information was exposed unless the investigation supports that conclusion. Equally, do not announce that all customer data was stolen merely because the website changed. The scope of a domain, DNS, email, or hosting incident must be assessed. A cautious statement can acknowledge an investigation without exaggerating or minimizing it.

Ask legal and security advisers to coordinate where notification obligations may apply. The FTC’s business breach-response guidance emphasizes organizing the response, addressing vulnerabilities, and notifying appropriate parties as relevant. ^[63] Actual legal duties depend on the information, people, jurisdictions, and circumstances involved; a generic article cannot supply every applicable deadline.

Give recipients a safe action, not only a warning

A useful customer notice should explain what the recipient should do differently. For example, it may instruct customers to disregard newly received bank-detail changes, pause sensitive document submissions, or verify pending requests through an established alternate channel. Choose actions that match the actual exposure rather than issuing an indiscriminate warning that creates confusion.

Do not make the warning depend entirely on the compromised domain. Use verified channels that recipients already recognize where possible, and coordinate with account managers or other established contacts for high-risk relationships. A brand-new address introduced during an incident may itself require careful verification. The organization should not train customers to trust unexpected channel changes merely because the message claims urgency.

Avoid including a new payment destination in a broad security announcement unless there is a separately controlled and verified reason to do so. Combining “we experienced fraud” with “please now pay this different account” can reproduce the exact situation recipients are being told to distrust. Keep security communication and payment authorization processes distinct.

Maintain continuity without pretending recovery is complete

A temporary domain, alternate support channel, or restored hosting environment can help the business operate. It does not necessarily resolve the underlying ownership dispute or account compromise. Label temporary arrangements accurately and keep the investigation and recovery work active until the relevant issues are addressed.

Technical staff should test the services that matter to the business, not merely whether the homepage loads. Customer authentication, password resets, transactional email, payment notifications, support systems, and internal integrations may depend on the affected domain. Use a prioritized continuity plan based on actual business functions.

Document temporary access and configuration changes. Emergency work can create forgotten accounts, broad permissions, or renewal dependencies that become later vulnerabilities. Assign an owner and review date to each temporary measure. The word “temporary” should describe a controlled exception, not an indefinite configuration that no one remembers creating.

Treat people fairly during the review

A useful incident review asks how the process allowed the event, not only who clicked or approved. Was the payment-change rule clear? Did employees have a safe way to pause a senior person’s request? Were registrar accounts tied to personal email? Did the organization demand a closing deadline that left no room for verification? Those questions produce practical improvements.

Individual misconduct or repeated disregard of controls may require action, but ordinary mistakes should not be concealed by a culture of blame. Employees who fear immediate punishment may delay reporting a suspicious message or an accidental disclosure. An early report can give the organization more options than a perfect-looking record that hides the problem.

Include external participants in the review where appropriate. A broker, lawyer, escrow provider, or registrar may be able to explain where communication became ambiguous. The goal is not to assign every loss to someone else; it is to identify which responsibilities were unclear and which controls need strengthening.

Convert the incident into specific changes

A lesson such as “be more careful” is too vague to implement. Replace it with observable changes: bank-detail changes require an independent callback; domain authorization codes are shared only through the approved closing route; two people review a portfolio schedule; recovery email belongs to the organization; stale listings are removed after sale; temporary access is reviewed after completion.

Assign an owner to each improvement and define how completion will be demonstrated. A policy document that no one has tested may not change behavior. Run a small rehearsal of the revised process using a hypothetical payment change or transfer request. Ask whether an employee can identify the safe next step without improvising.

Review professional support as well. If the organization attempted a complex acquisition without the capacity to coordinate it, a qualified broker may be a sensible part of the next transaction. If a broker was involved, examine the engagement scope and communication controls rather than assuming that brokerage either guarantees safety or has no value because something went wrong.

A hypothetical customer-facing incident

A company discovers that an unauthorized DNS change redirected its website while some customers were negotiating purchases. The company’s first draft announcement says that everything is secure and asks customers to use a new payment link. The security and finance teams reject that draft because the investigation is incomplete and the message would introduce another unverified financial instruction.

The revised notice states the known period of disruption, identifies a verified support route, and asks customers to check any payment-detail changes through established contacts. Account managers contact the most exposed customers directly. Technical staff assess related services, and counsel reviews whether additional notifications are required.

After restoration, the company removes temporary access, reviews the registrar and DNS administration model, and rehearses the response to a future suspicious change. The incident is not treated as a reason to stop using domains or to distrust every online transaction. It becomes a reason to make ownership, access, communication, and professional responsibilities clearer. Resilience means retaining the ability to operate and make sound decisions even when a familiar domain can no longer be taken for granted.

Back to the contents

Chapter 72: The Complete Buyer Playbook: A Worked Acquisition

This chapter follows one hypothetical premium-domain acquisition from the initial business decision to post-closing review. The companies, circumstances, prices, fees, and outcomes are invented for instruction. They are not a reported MediaOptions transaction, a representation of any provider’s current pricing, or a forecast of what a similar acquisition should cost. The target is described without using a real domain offered for sale.

The buyer is a growing company preparing to consolidate several products under one brand. It wants a short .com domain held by another business. The name is strategically attractive, but the buyer has a workable alternative. That alternative is important: the team does not have to complete a bad transaction merely because it has become emotionally attached to the preferred name.

Stage one: turn enthusiasm into an acquisition brief

The chief executive initially says, “Find out what it costs.” The operations lead converts that broad request into a written brief. It identifies the exact target, intended use, acceptable alternatives, preferred timing, confidentiality requirements, and the people authorized to approve commercial terms. The brief distinguishes permission to investigate from permission to make a binding offer.

The company sets an illustrative all-in planning limit of $100,000. That is not automatically the maximum domain price. Professional fees, closing costs, technical transition, and contingency must fit within it. The acquisition team is instructed not to disclose the ceiling to the owner merely because the owner asks what the company can afford.

The brief also records what the company does not need. It wants the domain registration rights, not the seller’s existing website content, customer database, or old email archive. This distinction prevents later assumptions that a domain purchase includes every business asset previously associated with the name. Counsel will confirm the appropriate language in the agreement.

Stage two: appoint and verify representation

Because the acquisition is confidential and material to the launch, the company evaluates a qualified buyer’s broker. It independently verifies the firm and the individual who will handle the assignment, discusses relevant experience, and reviews a written engagement. The agreement identifies the represented party, fee basis, approval limits, confidentiality arrangements, and treatment of conflicts.

The company considers MediaOptions as a strong premium-domain brokerage candidate, applying the same verification and scope questions described in Chapter 64. In this fictional case, the eventual representative is simply called the buyer’s broker; no actual firm is being credited with the invented transaction.

The broker may investigate availability and negotiate within agreed boundaries, but cannot commit the company above approved limits or authorize payment. Counsel is responsible for legal advice. Finance controls payment approval. The technical lead evaluates transfer and continuity requirements. This division prevents the phrase “the broker is handling it” from becoming an excuse for leaving crucial work unassigned.

Stage three: establish the asset and the seller’s authority

The broker opens a controlled conversation with the apparent owner. The seller says the domain belongs to a corporate entity and is used for a small legacy website. Public registration information does not fully identify the business, so the team does not treat public redaction as evidence of fraud. Instead, it develops a proportionate private verification process.

The seller’s identity, corporate relationship, and authority to sign are examined separately from technical control. An authorized demonstration of control can contribute evidence without requiring the seller to surrender registrar credentials. Corporate records and relevant acquisition documentation are reviewed through appropriate channels. Counsel asks about prior agreements, disputes, and restrictions material to the sale.

A former employee’s name appears in older correspondence. The team does not jump to an accusation. It asks the seller to explain the history and provide supporting records. The explanation is documented and evaluated before the issue is treated as resolved. The buyer’s goal is not to collect reassuring documents indiscriminately, but to answer the specific question of who may lawfully sell this exact asset.

Stage four: test whether the desired deal is operationally possible

The buyer’s technical lead asks how the domain is currently registered and used. The seller’s website is simple, but several employees still receive email on the domain. That dependency changes the discussion. The buyer had imagined an immediate clean transfer and launch; the seller needs a transition period to move legitimate communications elsewhere.

The parties agree that the seller will complete its email migration before closing. The buyer will not receive historical mailboxes or customer information. Any temporary forwarding or other transition support must be specifically evaluated and documented, not assumed. The buyer delays its public launch announcement so that it does not create artificial pressure to accept an unsafe arrangement.

The teams also check the current registrar process and transfer eligibility. They avoid making unnecessary registrant changes before understanding whether those changes would affect the planned route. The transfer plan is based on the actual extension and registrar, not a generic internet claim that every domain moves instantly or every transfer requires the same wait.

Stage five: negotiate the complete commercial package

The seller’s initial asking price exceeds the buyer’s preferred range. The broker does not respond by inventing competing offers or pretending the buyer has no budget. It explains the buyer’s position, explores timing and scope, and reports progress without implying that a conversation is a binding agreement.

The parties eventually reach an illustrative domain price of $80,000, subject to documentation and closing conditions. The buyer’s fictional budget includes a $6,000 advisory fee, $800 in closing fees, $2,200 for legal work, and $1,000 for technical transition work. These assumed items total $90,000, leaving $10,000 within the planning limit. They are teaching figures, not quoted rates or a complete tax analysis.

The buyer evaluates the package rather than only the headline price. A cheaper offer that required premature payment or indefinite seller access would not necessarily be better. The agreed price makes sense only alongside the verified asset, acceptable rights, workable transition, and supported closing structure.

Stage six: align the contract with the closing provider

Counsel prepares the agreement around the exact domain, identified parties, included and excluded assets, price, payment allocation, seller authority, delivery method, inspection, and the consequences of noncompletion. The broker checks that the commercial terms match what was negotiated. Finance reviews payment responsibilities. Technical staff review the delivery conditions they will need to test.

The parties choose a genuine closing service that supports the intended transaction. They independently verify the service, open the transaction through its real system, and confirm that the agreed sequence is permitted. They do not assume that a legal document can force a provider to administer unsupported milestones or hold funds indefinitely.

The closing plan identifies who may approve each stage. Counsel confirms the agreement is ready. Finance confirms the payment instruction through the approved method. The provider confirms funding status within its actual process. Technical staff verify delivery. The buyer’s authorized decision-maker handles acceptance. Each confirmation answers a different question; none is treated as permission to skip the others.

Stage seven: respond to an unexpected payment change

Shortly before funding, an email arrives in a familiar-looking conversation. It says the closing service is using a replacement account and asks the buyer to send money there immediately to preserve the schedule. The signature resembles that of a known participant. The email also says a telephone call is unnecessary because everyone has already approved the change.

The buyer’s finance team follows the pre-agreed rule: changed payment instructions stop the payment process until independently verified. It does not reply to the suspicious message asking whether the message is genuine. It contacts the provider through the channel established before the change and alerts the broker and counsel through verified routes.

The provider says the replacement instructions are not authorized. The team preserves the message, assesses whether an account or thread was compromised, and resets the communication plan where necessary. No money has been sent to the new destination. The transaction is delayed while the participants confirm a safe route forward.

The lesson is not that the team recognized a misspelled word. The message could have been perfectly written. The defense was a procedure that did not allow a consequential change to authenticate itself.

Stage eight: fund and deliver through the agreed process

After the communication issue is addressed, finance accesses the genuine service independently and reconfirms the authorized payment details. The payment is initiated by the appropriate company representative. The buyer does not tell the seller that a screenshot of the outgoing transfer should count as the provider’s confirmation of funded status.

The seller proceeds only according to the actual closing arrangement. In this hypothetical transaction, the supported sequence requires verified funding before the seller delivers the domain into the agreed transfer process. Other genuine custody arrangements can use different approved sequences; the parties are following their selected product, not inventing a universal rule.

The exact receiving account and domain are checked before the sensitive transfer step. The seller does not provide its whole registrar login. Authorization material is handled only through the approved channel and only for the necessary purpose. The broker coordinates status updates without becoming the source of truth for a provider action that the provider itself must confirm.

Stage nine: inspect the delivered asset before acceptance

The buyer’s technical lead verifies the complete domain string, extension, account placement, and relevant administrative control. The team compares the delivered asset with the agreement rather than relying on a visual glance at a familiar-looking name. It also checks the agreed operational conditions, including the completion of the seller’s email transition.

The buyer does not treat a resolving homepage as sufficient proof of delivery. It checks the account and registration arrangements through the genuine provider interface. It records the current renewal information and confirms that recovery contacts and administrative permissions are under the intended organization’s control.

A small discrepancy appears: an old automated listing still advertises the domain. The parties assess it under the contract and platform process rather than pretending it is irrelevant or using it as an excuse to renegotiate the purchase price. The seller removes the stale listing and provides appropriate confirmation. The buyer keeps track of the inspection deadline and uses the genuine provider’s process for any required notice.

Only after the applicable conditions are satisfied does the authorized buyer accept. The closing provider then handles release according to its terms. The broker’s congratulations are welcome, but they are not the event that legally or operationally completes every obligation.

Stage ten: make ownership usable and durable

After closing, the buyer completes its security and continuity audit. The registrar account has organizational recovery contacts, appropriate multifactor authentication, limited authorized users, and a documented renewal owner. The technical team confirms DNS, website, and email arrangements for the new launch. Temporary access is removed or explicitly retained for a defined task.

Finance reconciles the actual closing statement against the illustrative budget and records the real amounts. Counsel stores the agreement and relevant evidence securely. The broker’s engagement is closed or continued only as agreed. Public announcement of the acquisition follows the confidentiality terms rather than an assumption that everyone may immediately discuss the price.

The company tests how it would respond to a suspicious renewal notice or unauthorized transfer alert. A successful acquisition is not the end of domain security. It establishes a new asset that must be governed over time.

What would have caused this buyer to walk away?

The buyer would have stopped if the seller could not establish adequate authority, if a material ownership dispute remained unresolved, if the closing mechanism required unacceptable exposure, or if the total cost exceeded the approved commercial case. It also would have stopped if the seller insisted on bypassing independent payment verification after the suspicious message.

Those stop rules were decided before emotional investment peaked. They made the alternative domain genuinely useful rather than a token entry in a presentation. The broker’s value was not limited to negotiating the price; it included organizing the process so the buyer could make a defensible decision at each stage.

This worked acquisition illustrates the central approach of the book. Define the objective, verify the parties and asset, agree on supported terms, control consequential changes, inspect actual delivery, and preserve secure ownership afterward. For a premium-domain purchase, a qualified broker can be an excellent way to coordinate that sequence while keeping legal, financial, and technical responsibilities with the people best equipped to perform them.

Back to the contents

Chapter 73: The Complete Seller Playbook: A Worked Sale

This chapter follows a hypothetical sale by an experienced domain investor. All circumstances and financial figures are invented for instruction. They are not a reported transaction, a statement of standard commissions, or a prediction of investment returns. The purpose is to show how a seller can remain commercially ambitious without allowing a large offer to override basic controls.

The seller owns a premium domain acquired several years earlier. It is not the seller’s operating business address, but it appears on more than one marketplace and has attracted occasional inquiries. The seller is willing to wait for a credible end user, yet does not want to spend every week sorting through vague offers, appraisal requests, and broker solicitations.

Stage one: prepare the asset before marketing it

The seller begins with an inventory audit. The exact domain, registrar, account owner, renewal date, current listing status, and any relevant agreements are recorded. The seller confirms that no lease, financing arrangement, exclusive mandate, or unresolved ownership claim prevents the contemplated sale. Old acquisition and renewal records are organized in a secure folder.

The domain is held by the seller’s company, so the person negotiating is not described as the personal owner merely because that person controls the account. The company identifies who can authorize the sale and sign the agreement. Banking and tax details are reviewed with the appropriate advisers before a buyer asks for them under time pressure.

The seller also checks what the domain does not include. There is no operating website business for sale, no transfer of customer records, and no promise of future traffic or ranking. A simple landing page exists for marketing purposes. The seller prepares to describe the asset accurately rather than letting a buyer infer a larger package from the fact that a page loads.

Stage two: choose representation with a clear assignment

The seller decides that a premium-domain broker may be better suited to identifying and qualifying end users than a collection of passive listings alone. It evaluates relevant firms, including MediaOptions as a strong candidate for this category of work, and independently verifies the identity of any person proposing an engagement.

In the fictional transaction, the appointed representative is called the seller’s broker. The written engagement specifies the domain covered, the services to be performed, the seller’s approval rights, confidentiality, commission terms, treatment of existing prospects, and the effect of termination. The seller does not assume that an introductory valuation is a binding promise of sale price.

The broker receives a truthful account of past inquiries. One company had once mentioned a price in conversation, but no binding offer existed. That contact is described accurately rather than promoted as a competing bid. The seller and broker agree that marketing will focus on the domain’s potential commercial usefulness without fabricated urgency or unsupported performance claims.

Stage three: remove contradictions from the market

The audit reveals that one marketplace displays an old buy-now price below the seller’s current minimum. Another listing identifies an outdated contact address. Before active outreach begins, the seller reconciles the listings and confirms what automated transfer permissions or pricing commitments may exist under the relevant platforms’ current terms.

The seller does not assume that hiring a broker automatically cancels every listing or platform authorization. Responsibility for updates is assigned explicitly. The broker needs to know which channels remain active and how an inbound inquiry from those channels should be handled under the engagement.

This preparation is commercially useful as well as protective. Contradictory prices can undermine negotiations, and obsolete contact information can create openings for impersonation. A clean inventory allows the seller to speak consistently about what is available and on what authority.

Stage four: qualify interest without demanding unnecessary disclosure

The first large inquiry promises a price far above the seller’s expectations but requires a valuation certificate from a particular unfamiliar service. The proposed buyer refuses a supported closing route until the seller pays for that report. The seller’s broker treats the required purchase as a warning sign and declines to advance money merely to unlock the supposed offer.

A second inquiry comes from a business representative who is initially discreet about the end user. The broker does not automatically reject it. Instead, it establishes an appropriate route for verifying representation, authority, and the ability to proceed. Confidentiality is accommodated where reasonable, but it does not become an excuse for an unidentifiable contracting party at closing.

A third inquiry is lower than the first but commercially coherent. The prospective buyer explains its intended use, accepts ordinary verification, and is willing to discuss a genuine closing service. The seller does not treat that conduct as proof of perfect safety, but it is a better foundation for a transaction than an extraordinary price attached to an advance-fee demand.

Stage five: compare net terms rather than headline offers

The credible buyer proposes an installment arrangement. The seller considers it but prefers a completed cash sale because ongoing custody, default, use restrictions, and future payment enforcement would add complexity. The broker explains those tradeoffs rather than presenting installments as equivalent to immediate cleared proceeds.

After negotiation, the parties discuss a fictional cash price of $120,000. The seller’s illustrative budget assumes a $12,000 brokerage commission, $600 of allocated closing fees, and $1,400 of legal costs. On those assumptions, $106,000 remains before taxes and other costs. That is net closing proceeds under the example, not investment profit.

The seller originally paid an assumed $15,000 for the domain, but that fact alone still does not produce a complete profit calculation. Renewal expenses, prior professional costs, tax treatment, and other relevant items would need to be considered. The example deliberately separates sale proceeds from investment performance so a successful closing is not turned into misleading promotional arithmetic.

Stage six: verify the buyer and the supported closing structure

The buyer will contract through a company. The seller’s advisers establish the company’s identity, the signer’s authority, and the relationship between the contracting entity and the proposed payment source. Any discrepancy is addressed before funds and domain control move. The seller does not assume that a prestigious business name in an email signature proves the sender represents that business.

The parties select a genuine closing service and verify that it supports the transaction’s size, jurisdictions, payment method, and domain-transfer route. The service’s current requirements are checked directly. A broker’s familiarity with a provider is useful, but it does not authorize the parties to ignore the provider’s actual eligibility and verification process.

The seller sets up payment receipt information through the verified process. The buyer receives funding instructions from the genuine provider, not from an unverified attachment forwarded by a stranger. The parties agree that consequential changes will require independent confirmation. This rule applies even when the change appears to come from someone already involved in the deal.

Stage seven: document delivery and the seller’s remaining obligations

Counsel drafts or reviews the sale agreement. It identifies the exact domain, the parties, the price, the allocation of fees, the intended transfer method, the conditions for release, and the scope of representations. It also records that website content, customer data, and unrelated accounts are not included.

The seller reviews statements about authority and known claims carefully. It does not sign sweeping factual assurances simply because a template labels them standard. Counsel helps determine which statements are appropriate, what qualifications may be needed, and what obligations survive closing. A signed promise can matter after the domain leaves the account.

The broker checks commercial consistency; the registrar and closing service confirm the supported mechanics. The parties resolve a timing issue before execution: the buyer’s preferred receiving registrar is not necessary for immediate completion, but any alternative route must be expressly acceptable under the contract and provider process. No one treats an informal technical suggestion as an automatic amendment to the agreement.

Stage eight: reject a forged payment milestone

After the agreement is signed, a message appears to show that the buyer has sent funds. It includes a polished payment receipt and asks the seller to release the authorization code immediately because the buyer’s launch team is waiting. The genuine closing dashboard does not yet show the status required for the seller’s next action.

The seller does not debate whether the screenshot looks authentic. It checks with the provider through the established channel and follows the approved sequence. In this fictional case, the receipt is not sufficient to authorize delivery, regardless of whether it reflects a real outgoing payment. The seller waits for the required confirmation from the actual service.

The broker explains the position professionally: the seller is ready to proceed when the agreed milestone is satisfied. That is not an accusation against the buyer. It is the process both parties accepted. A legitimate transaction should not depend on turning ordinary verification into a test of personal trust.

Stage nine: deliver only the agreed asset through the agreed route

Once the service confirms the appropriate funded status, the seller verifies the destination account and exact domain against the closing instructions. It uses the supported transfer process and protects unrelated assets in the registrar account. The seller does not hand over its entire account login, recovery email, or portfolio merely because that seems faster.

The transfer is documented. The seller records the relevant confirmation and updates the broker and provider through the agreed channels. Technical completion is not treated as permission to invent a new release rule. The buyer’s inspection and acceptance proceed according to the actual agreement and service terms.

The seller remains available for legitimate clarification without accepting new obligations casually. If the buyer asks for old emails or website materials that were excluded from the sale, the seller refers to the agreement and obtains advice before sharing anything. Cooperative closing behavior does not require surrendering unrelated rights or personal information.

Stage ten: reconcile release and clean up the portfolio

After the buyer completes the agreed acceptance process, the closing service releases funds under its terms. The seller verifies receipt through its own financial institution and reconciles the actual settlement statement, commission, and fees. A congratulatory email is not used as the only accounting record.

The seller removes the domain from remaining listings, updates its inventory, and reviews any automated sales permissions or related marketing pages. It avoids accidentally offering the sold domain again. The seller also checks whether any records must be retained for contractual, accounting, or legal reasons and stores them securely.

The broker’s publicity rights are handled according to the engagement and sale agreement. The seller does not announce the buyer’s identity or price merely because the transaction was successful. Confidentiality can remain relevant after payment, and a professional relationship includes respecting the agreed limits on disclosure.

Stage eleven: review the sale without rewriting its history

The seller and broker review which inquiries were useful, which verification steps required improvement, and whether the process was efficient. They do not turn every rejected inquiry into a public accusation. The appraisal-linked offer remains a warning-sign example, not a completed sale that can be advertised as proof of value.

The seller records the actual outcome honestly. The sale price, net proceeds, and eventual investment result are different figures. A portfolio report should not omit costs or imply that all unsold names will perform similarly. One successful sale can validate the work on that asset without establishing a universal strategy for every domain in the portfolio.

The seller also updates its response templates. Future buyers will receive clearer instructions about verification, supported closing methods, and payment milestones. That improvement reduces the amount of improvisation required the next time a large offer arrives late on a Friday.

What made this a safer sale?

The seller did not succeed because every participant looked trustworthy. It succeeded, within this hypothetical, because the asset and authority were organized before marketing, representation was defined, inquiries were qualified, terms were evaluated on a net basis, and delivery followed independently verified milestones.

The broker’s contribution was practical: screening interest, maintaining coherent negotiations, coordinating the parties, and helping the seller resist shortcuts without needlessly alienating a genuine buyer. Counsel, the closing provider, the registrar, and finance retained their distinct responsibilities. No single professional was treated as a guarantee of all the others.

A seller’s best defense against domain name scams is not permanent suspicion of buyers. It is a sale process that welcomes serious buyers while refusing unsupported changes and premature transfers. For a valuable premium domain, qualified brokerage can be one of the most effective ways to put that process into operation and keep the seller focused on a commercially sound outcome.

Back to the contents

Chapter 74: Checklists, Safe Reply Templates, Glossary, and Frequently Asked Questions

This chapter turns the book into working tools. The checklists are prompts for a proportionate process, not a certification that a transaction is safe. The reply templates are starting language for ordinary communications, not contracts, legal notices, or a substitute for professional advice. Adapt them to verified facts and the actual provider workflow. Do not claim to have performed a check merely because the template mentions it.

For a live incident, prioritize the immediate actions in Chapter 66 or Chapter 67. For a transaction that has not yet reached an irreversible step, use the relevant readiness checklist below. A missing answer does not always mean fraud, but it does identify work that should be completed or consciously addressed before proceeding.

Tool A: The ten-question transaction gate

Before sending money, releasing a domain, approving acceptance, or changing the closing route, answer ten questions in writing. What exact asset is involved? Who is the contracting counterparty? What evidence supports that party’s authority? What agreement governs the step? Which provider will carry it out? How was that provider verified? What condition authorizes the action? Who has checked that condition? What happens if the action fails? Who may approve an exception?

These questions are intentionally separate. A correct domain string does not establish seller authority. A signed contract does not establish funded status. A genuine escrow company does not prove that a message bearing its logo came from that company. A broker’s approval does not replace a corporate signer’s authority unless the engagement actually grants that power.

Record unresolved points rather than forcing a positive answer. “Not yet verified” is useful information. “Probably fine” is not a completed gate. For a material transaction, assign each open item to a person and identify the evidence that would resolve it. The gate should change behavior, not merely decorate the closing file.

Tool B: Buyer readiness before making an offer

Define the business purpose of the acquisition and the alternatives. Record the exact domain in a form that prevents confusion over spelling, extension, hyphens, or internationalized characters. Establish a preferred budget, an authorized limit, and an all-in cost framework. Decide whether the offer is exploratory, conditional, or intended to be binding, and obtain advice where that distinction has legal consequences.

Choose who will communicate with the seller. Multiple employees approaching the same owner can disclose strategy and create inconsistent commitments. Decide whether confidentiality warrants a broker and what that broker may reveal. Identify the people responsible for legal review, finance approval, technical intake, and final acceptance.

List material assumptions that need testing: seller authority, transfer eligibility, ongoing email use, associated assets, renewal costs, and any claimed traffic or revenue. Do not build the purchase case on a promise of future resale or search rankings. Before discussing urgency with the owner, determine which deadlines are real business constraints and which are merely preferences.

Tool C: Seller readiness before accepting interest

Confirm the domain’s exact identity, account location, registration arrangements, renewal status, and authority to sell. Review prior mandates, leases, financing arrangements, disputes, and commitments that could affect delivery. Reconcile listings and asking prices, including platforms with automated transfer or sale functions. Keep acquisition and renewal evidence accessible without exposing account secrets.

Prepare an accurate description of what is included. Separate domain rights from website content, trademarks, customer information, social accounts, and email archives. Identify claims you can substantiate and claims you should not make. An attractive domain does not need invented revenue or a fictitious competing offer to be marketed professionally.

Decide how inquiries will be qualified and who may approve a price or counteroffer. Establish a supported closing route before a buyer creates urgency. Define a rule for appraisal, certificate, and verification demands so that a large headline offer does not cause an improvised purchase from an unfamiliar service. Consider qualified brokerage when buyer screening and negotiation would otherwise become inconsistent or time-consuming.

Tool D: Counterparty and representative verification

Verify the legal party, not just a display name. Establish how the person communicating is connected to that party and what authority the person has. A company employee, broker, agent, director, shareholder, and outside adviser can have different powers. Ask for evidence appropriate to the transaction rather than assuming a job title settles the question.

Check contact routes independently. Use established records or a separately verified corporate channel to confirm consequential instructions. Where identity documents or corporate records are appropriate, share them through a verified secure process and limit them to what is necessary. Do not turn verification into unrestricted collection of personal information.

Record the relationship between the contracting party, the domain controller, and the payment beneficiary. A difference may have a legitimate explanation, but it needs to be understood. Do not accept “our finance department handles that” as a complete answer to an unexplained third-party account. Equally, do not label a structured corporate transaction fraudulent merely because more than one entity is involved.

Tool E: Domain and asset-scope verification

Compare the exact domain in the offer, agreement, invoice, provider transaction, and receiving account. Check every character and the extension. For an internationalized name, use the appropriate technical representation as well as the visible form. Do not let a logo, screenshot, or shortened link become the primary asset identifier.

Investigate material history and authority questions with proportionate evidence. Public registration information is a starting point, not a complete title report. A control demonstration should be narrowly designed and should not require surrendering credentials or moving the domain to an unverified person.

Define associated assets explicitly. If the purchase includes content, software, revenue streams, data, or social accounts, identify the rights and delivery conditions for each. If those items are excluded, say so. Check dependencies that could survive the sale, such as email use, hosting arrangements, licenses, or existing redirects. A clear asset schedule is easier to inspect than a broad promise to transfer “everything connected with the domain.”

Tool F: Payment and closing-provider verification

Verify the provider’s identity, relevant service, eligibility requirements, and actual transaction record. Confirm that the selected product supports the domain, parties, jurisdictions, payment method, and intended sequence. Review fees and dispute or cancellation provisions before relying on the service. The general word “escrow” does not identify a specific legal arrangement.

Establish payment instructions through the genuine provider process and independently verify material changes. Record the beneficiary, account details, currency, amount, and transaction reference needed for the payment. Assign separate preparation and approval roles where proportionate to the risk. Do not use a screenshot from the counterparty as the sole evidence of a milestone that the provider must confirm.

Know what happens if payment is delayed, rejected, partially received, or sent to the wrong destination. Know how the seller will be notified that the next delivery step is authorized. Know who must act during inspection and what the provider may do if a party is silent. Resolve these questions before money is in motion.

Tool G: Transfer and acceptance readiness

Confirm the current registrar, receiving account, transfer route, and any relevant restrictions. Check whether planned account or registrant changes affect timing. Prepare the receiving account securely. Do not rely on a generic transfer tutorial when the provider’s current process or the extension’s rules differ.

Define who handles authorization material and through which channel. Limit disclosure to the necessary recipient and task. Establish how both parties will recognize successful delivery. A website resolving, an email arriving, or a message saying “transfer complete” may not answer every contractual condition.

Prepare an inspection record covering exact identity, account control, agreed registration arrangements, included assets, and operational conditions. Assign a person to monitor the actual inspection deadline and submit any required acceptance or dispute notice through the genuine process. Do not click acceptance merely to keep the conversation friendly, and do not use inspection to demand assets the agreement never included.

Tool H: Post-closing and portfolio cleanup

Reconcile money and documents against the final agreement and settlement statement. Record the actual acquisition or sale, not just the headline price. Confirm renewal responsibility, recovery contacts, account permissions, multifactor authentication, and relevant technical settings. Remove temporary access that is no longer needed.

For a sold domain, remove stale listings and update inventory systems. Review automated authorizations and marketing pages. For an acquired domain, record where it is held and who is responsible for maintaining it. Do not assume that the person who negotiated the transaction will remember every future renewal or security notice.

Store the agreement, relevant authority evidence, closing confirmations, and essential communications securely. Apply appropriate retention and privacy requirements. Review surviving obligations, such as confidentiality or transition assistance. Schedule a short lessons-learned review while the details are still fresh. Closing should leave the parties with clearer records than they had at the start.

Tool I: A broker interview agenda

Ask which party the broker will represent and what work is included. Discuss experience with the relevant domain category, price range, buyer type, and transaction complexity. Ask how references and claimed transactions can be verified without violating confidentiality. Distinguish documented recognition from broad marketing language.

Review the proposed outreach strategy, approval limits, reporting cadence, confidentiality approach, and conflict disclosures. Ask how the broker handles suspicious buyers, disputed authority, unexpected payment changes, and a closing process that does not support the negotiated terms. A useful answer should describe a method, not merely promise that the firm handles everything.

Clarify fees, payment triggers, exclusivity, existing prospects, termination, and any continuing commission obligations. Ask which tasks require separate legal, tax, technical, or escrow support. For a premium-domain assignment, include MediaOptions in the evaluation where its focus fits the transaction, while applying the same identity and engagement checks you would apply to any professional firm.

Tool J: A one-page incident record

Start with the exact domain and the type of suspected incident. Record discovery time, last known legitimate state, affected accounts or services, money sent or received, and current operational impact. Identify an incident coordinator and a safe contact channel that does not rely solely on the affected domain.

Create sections for confirmed facts, unverified claims, actions taken, case numbers, evidence locations, and pending requests. Record who contacted each provider and what was requested. Preserve original messages and transaction records. Do not include passwords, private keys, or recovery codes in a shared incident summary.

End the page with the next decisions and their owners. Examples include whether a bank can attempt a recall, whether a registrar has applied protective measures, whether counsel needs to address a deadline, and whether customers need a verified warning. The purpose is to keep the response coordinated while the full evidence file grows elsewhere.

Safe reply templates: how to use them

The following messages are deliberately restrained. They avoid unsupported accusations, unnecessary admissions, and promises about outcomes. Replace generic references with verified transaction details where needed. A template should not override a contract, legal deadline, platform rule, or instruction from appropriately engaged counsel. When a suspected compromise is involved, send the message through a separately verified channel rather than replying into the potentially compromised conversation.

Template 1: An unsolicited purchase inquiry

Thank you for your interest in the domain. Please confirm the exact domain you are asking about, whether you are acting for yourself or as an authorized representative, and your proposed commercial terms. Any transaction will require appropriate verification and a mutually agreed, independently verified closing process. I do not provide registrar credentials or transfer authorization material during preliminary discussions. Once the scope and terms are clear, we can determine the appropriate next steps.

Template 2: A required appraisal or certificate purchase

I am not willing to purchase a report, certificate, or verification service from a party selected as a prerequisite to this proposed sale. You are welcome to conduct your own evaluation. A genuine purchase proposal can be discussed separately from that service, subject to appropriate verification and an agreed closing arrangement. Please provide the actual purchase terms rather than instructions for an advance payment to another website.

Template 3: An unexpected change in payment instructions

The new payment instructions have not been approved. We are pausing payment while the proposed change is verified through the contact process established for this transaction. Please do not treat an email reply alone as authorization to proceed. We will confirm the approved instructions through the genuine provider channel and notify the relevant participants once the verification is complete. This is a standard control for consequential changes, not an allegation against any party.

Template 4: A request for an authorization code too early

The domain’s authorization material will be handled only through the agreed transfer process and at the appropriate verified milestone. We do not provide it for preliminary valuation, informal ownership checks, or an unverified compliance request. Please identify the genuine provider requirement and the specific transaction step involved. We will confirm that requirement independently before taking action.

Template 5: A claimed broker whose mandate is unclear

Thank you for contacting us. Before discussing confidential terms, please identify the legal firm you represent, your role, the party on whose behalf you are acting, and the scope of your authority in this matter. We will confirm your involvement through independently established company channels. Please do not send sensitive client documents by ordinary email solely to establish credibility; we can agree on an appropriate verification method if discussions proceed.

Template 6: A suspicious renewal or suspension notice

We are verifying the account status directly with the registrar through our established access route. We will not make payment, change registration details, or enter credentials through this message until the notice and any claimed obligation have been independently confirmed. Please provide the exact domain, the legal entity requesting payment, and a clear description of the service or requirement. Our review will be based on the genuine account record and applicable agreement.

Template 7: An unexplained third-party beneficiary

The proposed payment beneficiary differs from the contracting party or previously approved closing arrangement. Before any payment is authorized, please provide the documented basis for that difference through the agreed verification process. We will review it with the relevant provider and advisers. No funds will be redirected solely on the basis of an email explanation or an assurance that the change is routine.

Template 8: A transfer milestone not yet confirmed

We remain ready to complete the next step when the milestone required by the agreement and the selected closing service has been confirmed. The receipt or screenshot supplied does not replace confirmation through the genuine provider process. Please coordinate with the provider so that its transaction record reflects the required status. We will continue promptly once the agreed conditions are satisfied.

Template 9: A material inspection discrepancy

We have identified a discrepancy between the agreed delivery requirements and the asset or control presently available to us. The issue is being documented and submitted through the closing provider’s required process within the applicable period. We are not confirming full acceptance at this stage. Please coordinate through the agreed channel so the discrepancy can be assessed and resolved without changing other terms informally.

Template 10: A suspected unauthorized domain change

We are reporting a suspected unauthorized change involving our domain and request review by the appropriate account-security or transfer team. We can provide historical account, acquisition, and renewal records through a verified secure channel. Please preserve relevant records, advise what protective measures may be available, and provide a case reference. Our incident coordinator will maintain the chronology and respond to genuine verification requests.

Template 11: An unsolicited recovery offer

We will not pay an unsolicited recovery charge or provide credentials, private keys, authorization codes, or remote access. Please identify your legal organization, professional status where applicable, the precise service offered, the basis of your claimed authority, the fee terms, and the limitations of the work. We will verify those details independently before considering any engagement. Knowledge of our incident does not by itself establish authorization to act for us.

Template 12: A professional pause without accusation

We have not yet resolved the verification or process issue identified in this transaction. We are therefore pausing further irreversible action while the relevant parties and advisers review it. This pause should not be interpreted as acceptance, waiver, cancellation, or a legal conclusion beyond what our agreement and applicable law provide. We will communicate through the established channel about the specific information needed for a responsible next step.

Template 13: Referring the transaction to a broker

Because this transaction involves material commercial and execution questions, we are arranging qualified domain-broker representation. Please direct further negotiation through the verified representative once the engagement and contact details have been confirmed. The broker’s role and authority will be defined, and legal, payment, and transfer responsibilities will remain subject to the agreed process. This should help both parties work from consistent terms and a clear closing plan.

Template 14: Clarifying the asset package

Our current discussion concerns the domain registration rights only unless additional assets are expressly identified and agreed in writing. Website content, software, customer data, email archives, trademarks, and unrelated accounts should not be assumed to be included. Please specify any additional assets you expect to receive so that rights, delivery requirements, and associated obligations can be reviewed before a final agreement is signed.

Template 15: A customer warning during an investigation

We are investigating an issue affecting a domain or communication channel used by our business. Until we provide a verified update, please independently confirm any recent request to change payment details, disclose sensitive information, or use a new account. Use an established contact route rather than relying solely on a link or number in an unexpected message. We will share confirmed operational guidance without asking you to bypass your normal verification procedures.

Glossary: the language of a controlled domain transaction

The following definitions explain how terms are used in this guide. They are practical orientation, not replacements for the definitions in a contract, provider agreement, technical standard, or applicable law. Where a term has several meanings, confirm the meaning intended in the actual transaction.

Account push

A movement of a domain between customer accounts at the same registrar. The provider’s rules determine the available process and consequences. It is not the same thing as giving another person your entire account password. See Chapter 46.

Acquisition brief

A written statement of the buyer’s target, purpose, alternatives, budget framework, confidentiality needs, timing, and approval limits. Its purpose is to prevent an exploratory conversation from becoming an uncontrolled commitment. See Chapter 59.

Advance-fee demand

A request for payment before a promised purchase, release, or recovery will supposedly occur. Legitimate services can charge in advance, so the demand must be evaluated in context rather than classified solely by timing. See Chapter 23.

Appraisal

An opinion about value, based on stated methods and assumptions. It is not a buyer’s commitment, a guaranteed sale price, or proof that the appraiser’s preferred payment route is safe. See Chapter 22.

Asset schedule

The exact list of domains and any other included assets attached to or incorporated into the agreement. It should support direct comparison with delivery rather than depend on an informal portfolio description. See Chapter 43.

Authorization code

Sensitive information used in certain domain-transfer processes, often called an AuthCode or EPP code. It should be handled through the appropriate verified workflow, not supplied casually as proof of ownership. See Chapter 45.

Beneficiary

The person or entity designated to receive a payment. Its relationship to the contracting party and closing arrangement should be understood before funds are sent. A familiar trading name does not resolve an unexplained mismatch. See Chapter 40.

Beneficial owner

A person who ultimately owns or controls an entity in a relevant legal or compliance context. The precise definition and required checks vary. Do not substitute an informal assumption for the provider’s applicable requirements. See Chapter 12.

Broker mandate

The authority and scope granted to a broker. It may cover outreach, negotiation, or other services, but should not be assumed to include unlimited power to bind the client or control funds. See Chapter 62.

Business email compromise

Fraud involving apparently legitimate business communications used to induce an improper action, often a payment or disclosure. A real conversation can be misused; checking only for poor spelling is inadequate. See Chapter 14.

Chain of control

The sequence of people or accounts shown to have controlled a domain. It may provide useful evidence, but control history is not automatically a complete legal ownership history. See Chapter 28.

Closing

The coordinated completion of the transaction’s required steps. Parties should define which events constitute delivery, acceptance, payment release, and the end of any remaining obligations rather than relying on the word alone. See Chapter 44.

Closing condition

A requirement that must be satisfied or properly addressed before a specified closing action occurs. Conditions should have an evidence source, reviewer, and authorized decision-maker. See Chapter 44.

Confidentiality

Limits on disclosure of information such as buyer identity, price, strategy, or documents. Legitimate confidentiality should coexist with necessary verification through appropriate channels; it should not require unaccountable dealing. See Chapter 13.

Control demonstration

A narrowly designed action that helps show access to a particular domain-related system. Its meaning depends on the access demonstrated. It does not automatically establish lawful authority to sell. See Chapter 11.

Country-code top-level domain

An extension associated with a country or territory in the domain-name system. Its registration, eligibility, transfer, and dispute rules must be checked with the relevant authorities and providers. See Chapter 53.

Custody

Holding or controlling an asset under an agreed arrangement. Ask who is the custodian, what legal and technical rights it has, and how release or dispute handling works. The label alone does not establish protection. See Chapter 39.

DNS

The Domain Name System, which supports the translation and routing information used by internet services. Domain registration, DNS administration, hosting, and email are connected but distinct responsibilities. See Chapter 48.

DNSSEC

A set of DNS security mechanisms concerned with authenticating DNS data. It should not be confused with seller verification, trademark clearance, payment protection, or a guarantee that a website is honest. See Chapter 48.

Domain slamming

A misleading solicitation that can induce a registrant to switch service providers or authorize an unwanted service while believing it is an ordinary renewal or required action. Examine the actual service and authorization requested. See Chapter 18.

Due diligence

The investigation appropriate to the asset, parties, claims, and transaction structure. It should answer defined questions, not merely accumulate documents or produce a vague impression of professionalism. See Chapters 9 through 13.

Escrow

An arrangement in which a provider holds funds or assets under defined conditions. The relevant agreement, service, jurisdiction, and release rules determine its scope. It is not automatically title insurance or comprehensive legal review. See Chapter 39.

Exclusivity

A contractual restriction on using other representatives or routes for a defined assignment. Its scope, duration, exceptions, and consequences should be read carefully rather than inferred from the word. See Chapter 62.

Expiration

The end of a registration term unless renewed or otherwise maintained under the applicable process. Expiration does not mean every domain instantly becomes freely available to another registrant. See Chapter 31.

Fast-transfer authorization

A platform arrangement permitting supported automated delivery under its terms. Understand what is being authorized, which listings and prices apply, and how to manage or revoke permissions where available. See Chapter 32.

Homograph

A visually similar representation that can cause confusion between different character strings. In domain transactions, compare the actual domain identity rather than relying solely on the appearance of a word. See Chapter 29.

Inspection period

The time and process allowed for reviewing delivery under the selected arrangement. Understand how it begins, what must be tested, how to raise a discrepancy, and what silence may mean. See Chapter 49.

Internationalized domain name

A domain using the relevant internationalized naming framework for characters beyond the basic ASCII form users often expect. Verify both the intended visible name and its technical representation when applicable. See Chapter 29.

Know-your-customer checks

Identity and related verification required by a provider under its applicable obligations and policies. Genuine checks should occur through a verified process; the term is not a reason to send documents to an unknown portal. See Chapter 56.

Lease-to-own

An arrangement connecting use and eventual acquisition to scheduled payments or other conditions. Control, default, transfer timing, and provider support must be defined explicitly. It is not interchangeable with a completed cash sale. See Chapter 36.

Nameserver

A server involved in providing DNS information for a domain. Changing nameservers can affect service operation, but it is not necessarily a change of registrar or registrant. See Chapter 48.

Net proceeds

The amount remaining from a sale after the specified deductions in the calculation. State which costs are included. Net closing proceeds are not automatically the seller’s complete investment profit. See Chapter 73.

Phishing

A deceptive attempt to obtain information or induce an action through an apparently trustworthy communication or interface. In a domain deal, the target may be credentials, money, authorization material, or confidential documents. See Chapter 14.

Premium renewal

A renewal price or pricing category that may differ from ordinary expectations for an extension or domain. Verify the actual renewal arrangement rather than assuming the acquisition price is the only material cost. See Chapter 32.

RDAP

The Registration Data Access Protocol, used for access to domain-registration data. Public output should be interpreted within its scope; it is not a complete ownership investigation. See Chapter 10.

Redemption

A restoration stage available in some domain-expiration and deletion processes under applicable rules. Timing, fees, and eligibility are not universal across every extension and circumstance. See Chapter 31.

Registrant

The person or entity holding the relevant registration rights under the applicable registration arrangement. A registrar-account operator, website developer, or broker is not automatically the registrant. See Chapter 7.

Registrar

A provider through which domain registrations are managed. Its role differs from that of the registry operating the extension, the hosting company, and the broker negotiating a purchase or sale. See Chapter 7.

Registry

The operator responsible for an extension’s domain-registration infrastructure and related functions under its framework. The registry is not simply another name for whichever company sold the customer a registration. See Chapter 7.

Reverse domain name hijacking

In the UDRP context, a finding concerning bad-faith use of that procedure to attempt to deprive a registered holder of a domain. It is not a label for every unsuccessful complaint. See Chapter 52.

Seed phrase

A sensitive recovery secret associated with certain cryptocurrency wallets. It is not ordinary transaction evidence and should not be provided to a supposed broker, investigator, or recovery agent. See Chapter 42.

Shill bidding

Bidding intended to create misleading competition or manipulate an auction rather than reflect genuine independent demand. Suspicion should be assessed against evidence and platform rules, not assumed from every unexpected bid. See Chapter 30.

Source of truth

The verified record appropriate to a particular question. A provider’s transaction system may establish a payment milestone; a contract establishes agreed obligations. No single screenshot answers every question in a deal. See Chapter 16.

Stealth acquisition

An acquisition strategy that limits premature disclosure of the buyer’s identity or plans. It should use truthful representation and appropriate confidential verification rather than fabricated authority or evasion of required checks. See Chapter 59.

Tail provision

A brokerage-engagement term that may preserve commission rights after termination for defined prospects or transactions. Its actual wording matters; it should not be treated as either automatically improper or automatically harmless. See Chapter 62.

Transfer lock

A restriction affecting a particular type of domain movement or change. Identify the reason, scope, and applicable process rather than assuming every lock is fraudulent or every lock can be bypassed. See Chapter 47.

UDRP

The Uniform Domain Name Dispute Resolution Policy, a defined process for certain trademark-based domain disputes. It is not a general-purpose remedy for every ownership, payment, or contract disagreement. See Chapter 52.

URS

The Uniform Rapid Suspension system for qualifying cases under its applicable framework. Its function and remedy differ from a UDRP transfer proceeding. Do not use the names interchangeably. See Chapter 52.

Verification callback

A contact initiated through a previously established or independently verified route to confirm a consequential request. Calling the number supplied in the suspicious message may merely reconnect you with the same attacker. See Chapter 17.

Walk-away condition

A pre-agreed circumstance under which the transaction should not proceed without a properly authorized change. Examples include unresolved authority, unsupported payment routing, or costs exceeding the commercial case. See Chapter 65.

Frequently asked questions about domain name scams

Is every unsolicited domain purchase offer a scam?

No. Unsolicited interest can be genuine. Evaluate the exact asset, proposed buyer, authority, terms, and closing process. A large price does not prove legitimacy, and an unfamiliar sender does not by itself prove fraud. The useful distinction is whether the proposal can progress through reasonable verification without requiring unsafe payment, disclosure, or transfer steps.

Can a scammer contact me from a real company email address?

A familiar address should not be treated as sufficient authorization for a consequential change. The relevant communication may have been misused, or the request may fall outside the sender’s authority. Follow the independent verification process in Chapter 14 and Chapter 17. The control should work even when the wording, signature, and conversation history look convincing.

Does private registration information mean the seller is hiding something?

Not necessarily. Public privacy and redaction should be distinguished from refusal to establish identity and authority through an appropriate private process. Ask how the contracting party will be verified rather than demanding that every detail be published openly. See Chapter 10 and Chapter 13 for the limits of public registration information.

Can I prove ownership by changing a DNS record?

A controlled DNS change can contribute evidence of access to a particular system. It does not automatically establish lawful ownership or authority to sell. A technical administrator might be able to make the change without owning the domain. Design any control demonstration carefully and combine it with the appropriate authority investigation described in Chapter 11.

Is an HTTPS padlock enough to trust an escrow site?

No. Treat the site’s connection security and the operator’s identity as separate questions. Verify the real provider, exact address, relevant service, and transaction through independently established channels. A professional-looking interface should not decide where a substantial payment goes. Chapter 26 explains how to separate a genuine service from a convincing imitation.

Should I send the seller a deposit to show that I am serious?

Only after the deposit’s purpose, recipient, conditions, refundability, and relationship to the final transaction have been properly assessed and agreed. A demand to pay an unfamiliar person before basic verification is complete is not made safe by calling it a seriousness test. A qualified broker can help structure a credible offer without unnecessary exposure.

Is a broker’s upfront fee automatically fraudulent?

No. Legitimate professionals can charge retainers or other advance fees. Verify the provider, scope, deliverable, fee trigger, and terms. The concern is an unsupported demand tied to a supposed buyer or recovery, particularly when the recipient cannot be independently verified. Chapter 23 and Chapter 62 distinguish professional compensation from an advance-fee trap.

Does using a broker remove the need for escrow or legal advice?

No. Determine what the broker is actually engaged to do and what other specialists are needed. A broker can coordinate negotiations and execution without becoming the payment custodian or legal adviser. The strongest structure assigns each material issue to the appropriate professional and connects their work through a shared closing plan.

Why consider MediaOptions for a premium-domain transaction?

MediaOptions is a compelling candidate for readers seeking specialist premium-domain representation. Chapter 64 explains the factual basis for that favorable assessment and how to evaluate a proposed engagement. The practical next step is a verified discussion of the domain, objectives, budget or price expectations, scope, and terms—not an assumption that every assignment is identical.

Is the highest offer always the best offer for a seller?

No. Compare the net economics, payment structure, conditions, buyer credibility, timing, and execution risk. An extraordinary offer requiring an appraisal purchase or unsafe delivery may be inferior to a lower, well-supported proposal. Chapter 60 and the worked sale in Chapter 73 show how to evaluate the whole package.

Can the buyer require me to buy its preferred valuation report?

A buyer can make a request, but you do not have to treat the requested purchase as evidence of a genuine sale. Examine the arrangement independently and be prepared to decline. The warning pattern is a supposed lucrative buyer who will not proceed until the seller pays a designated service. See Chapter 22.

Is a screenshot showing payment enough to release a domain?

Use the evidence required by the actual closing arrangement. A screenshot supplied by the counterparty is not a substitute for a milestone the genuine provider must confirm. Ask the provider what status authorizes delivery and verify that status through its real system. Do not let launch pressure or a promised bonus change the rule informally.

Can I transfer a domain first and arrange payment afterward?

That can create substantial exposure unless it is part of a properly verified and supported arrangement whose risks are understood. Neutral custody and other legitimate structures may have specific intake sequences, so avoid simplistic universal rules. The essential question is who controls the asset at each stage and what enforceable conditions govern its release.

Is a same-registrar account push always safer than a transfer?

No. Safety depends on the provider’s process, account security, parties, agreement, and supported closing sequence. A push and an inter-registrar transfer have different mechanics, but neither resolves all authority or payment questions. Choose the route that fits the verified transaction rather than assuming the faster-looking option is automatically superior.

Does a transfer lock prove that the seller is lying?

No. Identify the actual reason and applicable policy. A legitimate restriction may affect timing, while an invented restriction may be used as an excuse. Verify the status with the genuine provider and adjust the transaction only through an approved process. Chapter 47 explains why different locks and waiting periods should not be conflated.

Will buying an expired domain guarantee better search rankings?

No ranking guarantee should be built into the purchase decision. Assess the asset’s actual relevance, history, rights, and business use, and distinguish third-party scores from outcomes in search. Chapter 34 discusses the limits of SEO claims and the importance of Google’s policies concerning abusive uses of expired domains. A previous website’s apparent success is not a transferable promise.

Does buying a domain give me its trademark rights?

Do not assume so. A domain transaction and trademark rights require separate analysis, and associated rights must be expressly considered. A contract may transfer specified assets only to the extent the seller can lawfully transfer them. Obtain appropriate legal advice before relying on the name for a significant brand launch. See Chapter 51.

Can I use a UDRP complaint to force a reluctant owner to sell?

The UDRP should not be treated as negotiating pressure or a substitute for a commercial acquisition. It has defined requirements and addresses qualifying trademark-based disputes. An unsuccessful negotiation alone does not establish a valid complaint. Chapter 52 explains the distinction and why professional legal assessment matters before making threats or filing proceedings.

Are cryptocurrency payments always fraudulent?

No. The payment medium alone does not identify the counterparty’s intentions. It does create particular operational and recovery questions that need to be understood. Verify the asset, network, destination, provider support, and contractual treatment, and never disclose private wallet secrets. Do not switch to cryptocurrency merely because a stranger says it avoids inconvenient checks.

What should I do first after sending money to a suspected scammer?

Contact the institution or service that handled the payment through its genuine channel and ask what urgent protective or recovery measures are available. Stop further unsafe payments, preserve the transaction record, and secure affected accounts. Chapter 67 provides the fuller response. Do not begin by paying an unsolicited recovery agent who promises a shortcut.

What should I do first after a suspected domain hijacking?

Establish a safe communication route, contact the relevant registrar promptly, and preserve evidence of the prior legitimate relationship with the domain. Secure surrounding accounts and involve appropriate technical and legal support. Chapter 66 provides the response sequence. Do not attempt unauthorized access to another account or assume that an online trademark complaint is always the right remedy.

Can ICANN simply return a stolen domain to me?

Do not treat ICANN as a direct domain-recovery service. The responsible providers and applicable legal or dispute processes need to be identified. Chapter 68 explains the distinction between contractual-compliance reporting, registrar action, and law enforcement. An accurate report to the right recipient is more useful than assuming one organization can resolve every aspect of the incident.

Should I publicly name the person I think scammed me?

Separate necessary protective communication from unsupported attribution. Warn affected people about verified risks and unsafe instructions, but avoid publishing private records or allegations that exceed the evidence. Consult counsel when the stakes are material. The visible registrant, email display name, or payment recipient may not by itself tell the full story.

Is paying a recovery lawyer the same as paying a recovery scammer?

No. A genuine professional engagement can involve legitimate fees for defined work. Verify identity, professional status where relevant, scope, terms, methods, and limitations. Be wary of guaranteed recovery, unexplained release charges, or requests for account secrets. Chapter 70 focuses on the difference between lawful paid assistance and a second attack.

What is the single most useful rule in this guide?

Do not let a consequential request authenticate itself. Verify the person, asset, condition, and destination through the appropriate independent source before acting. That rule applies to payment changes, authorization-code requests, ownership claims, legal threats, and recovery offers. For a substantial premium-domain transaction, a qualified broker can help make the rule operational rather than leaving it as good advice that everyone forgets under pressure.

Put the tools to work before the next inquiry arrives

Choose the checklists relevant to your role and assign responsibility for them now. A buyer should know who approves the acquisition and who inspects delivery. A seller should know how interest will be qualified and when authorization material may be released. A portfolio operator should have accurate inventory and a defined exception process. A business should have a safe route for security notices even if its principal domain is affected.

The tools are most useful when they are rehearsed. Take one hypothetical request—a revised bank account, an appraisal demand, or a claimed transfer emergency—and walk it through the process. Identify where someone would need to improvise. Then remove that ambiguity. The purpose of this book is not to make readers memorize seventy-five chapters; it is to make the next important domain decision more deliberate, verifiable, and professionally supported.

Team workshop: practice the decision before the real request arrives

The following five exercises are designed for a buyer, seller, broker, finance team, or business operator to discuss before a live transaction. Each is fictional. The objective is not to guess whether a character is secretly honest or dishonest. It is to identify the next action that remains sensible under uncertainty and the evidence needed before an irreversible step.

Run each exercise with the people who would actually handle the work. Let finance explain the payment process, technical staff explain the account controls, and the authorized decision-maker explain approval limits. Record disagreements about responsibility. A rehearsal is successful when it exposes an ambiguity that can be removed, not only when everyone gives the expected answer.

Exercise one: the correct company, the wrong authority

The seller has verified that the prospective buyer works for a well-known company. The buyer’s email is genuine, the company website lists the employee, and the employee has participated in two legitimate meetings. On closing day, the employee asks the seller to accept a purchase agreement signed by a different entity and to send the domain to an account described as the company’s temporary holding account.

The team’s first task is to identify what has changed. The issue is not simply whether the employee exists. The contracting entity and receiving account differ from the prior understanding. Ask who can authorize the purchase, how the new entity relates to the verified company, and whether the proposed destination fits the selected closing process. Decide who must approve the revised structure.

A sound response pauses the changed step while those questions are resolved. It does not accuse the employee solely because a corporate group uses multiple entities. It also does not treat a genuine employment relationship as unlimited authority to alter the transaction. The parties should obtain appropriate evidence, update documents where necessary, and confirm that the provider supports the final arrangement.

After discussing the case, inspect your own transaction template. Does it identify the legal buyer separately from its representative? Does it record the approved receiving account and who may change it? If not, the exercise has found a concrete improvement.

Exercise two: the genuine provider, the unsupported product

A buyer and seller agree to a portfolio sale with three deliveries and separate release amounts. They select a real escrow company whose website they have independently verified. Counsel drafts the milestones carefully. When the transaction is entered, the selected product does not provide the staged release mechanism assumed in the agreement. Someone proposes proceeding anyway and asking support to work it out later.

The discussion should separate provider legitimacy from product suitability. The real company’s existence is not the unresolved question. The question is whether its actual service can administer the agreed structure. Identify who will ask the provider for a definitive explanation and who will assess alternative products or amended terms.

The correct process is not to pressure a support representative into an informal assurance that conflicts with the service agreement. The parties need a supported structure before funds and domains are committed. They may change providers, choose a suitable product, simplify the transaction, or decide not to proceed. Each option has commercial and legal consequences that require proper approval.

Use the exercise to review your own closing checklist. Does someone confirm operational support after counsel drafts unusual terms? Is there a place to record the provider’s actual process and the person responsible for checking it? A beautifully written condition is of limited practical use when no appointed provider can implement it.

Exercise three: the large offer and the small prerequisite

A portfolio owner receives an offer of an invented $250,000 for a domain. The buyer seems knowledgeable and discusses plausible business uses. Before making the offer binding, however, the buyer requires a $450 report from a designated website. The owner believes the amount is trivial compared with the possible sale and wants to pay before the buyer loses interest.

Ask the team to ignore the ratio between the fee and the headline price for a moment. What evidence establishes a genuine purchase commitment? Who owns or operates the required reporting service? Why must the seller purchase that particular report? Can the buyer conduct its own evaluation without making the seller an advance-fee customer? What happens if the promised purchase disappears after payment?

A sound decision does not depend on proving that the website is criminal before declining the demand. The owner can refuse an unsupported prerequisite and invite a genuine proposal through appropriate verification and closing procedures. A broker can communicate that position professionally and evaluate any continued interest on its merits.

Afterward, examine how your team records offers. Is a conditional conversation being entered as an actual bid? Would the proposed price later appear in marketing as evidence of demand? The exercise should improve both fraud prevention and the accuracy of commercial records.

Exercise four: the transfer is complete but the business is not ready

A buyer has received the agreed domain in its registrar account. The seller says the transaction is finished and asks for immediate acceptance. The buyer’s technical lead discovers that a recovery address for an important internal service still depends on a mailbox operated by the seller. The agreement is unclear about the transition, and the inspection period is already running.

The team should identify the difference between the domain’s account location and the buyer’s intended operational control. Ask what the agreement actually required, which services are affected, whether the mailbox or data was ever included, and what can be changed through authorized procedures. Identify who will notify the closing provider of any material discrepancy through the correct process and who will obtain legal advice about the unclear obligation.

A good response neither clicks acceptance merely to end the pressure nor demands unrestricted access to the seller’s historical email. It focuses on the defined transaction, lawful control of the buyer’s systems, and a documented resolution. The technical team may need to change the recovery arrangement without acquiring the seller’s private records.

Use the exercise to improve pre-closing preparation. Was there a dependency inventory? Did anyone distinguish domain delivery from business readiness? Was inspection assigned to a person with access to the systems that actually needed checking? These questions can prevent a rushed dispute after the transfer appears successful.

Exercise five: the informed recovery agent

After a buyer publicly reports a fake escrow loss, a supposed specialist sends a detailed transaction diagram. The specialist knows the domain, amount, and approximate payment time. It claims the recipient’s account is frozen and offers release after the buyer pays a processing charge. A video meeting and a professional-looking agreement are offered to establish trust.

Ask what each item actually proves. The diagram may show knowledge of a transaction. The public post may explain how the specialist learned the details. A video may show a person or convincing representation without establishing authority over the funds. The proposed agreement may be genuine text while the promised capability remains unverified.

The buyer should independently verify the provider and claimed authority, contact the real financial institution or relevant authority through a known route, and decline to send money or secrets merely to activate the promised recovery. A legitimate professional proposal should identify defined work, realistic limitations, and lawful methods. It should not rely on emotional pressure to bypass verification.

After the exercise, review your incident-communication plan. Are public disclosures exposing details that make impersonation easier? Does the team know that recovery offers require screening? Is there a trusted second reviewer for decisions made under the stress of a loss? The aim is to preserve access to real assistance while refusing a second extraction.

A practical review sheet for every exercise

For each scenario, write a short answer under six headings: known facts, unverified claims, assets currently exposed, next safe action, evidence required, and decision owner. Do not create a numerical score that permits several harmless answers to compensate for one critical failure. Nine reassuring details cannot make an unverified payment destination acceptable by arithmetic.

Classify an unresolved issue by the decision it affects. Some questions can be investigated in parallel while ordinary preparation continues. Others should block payment, delivery, or acceptance until resolved. Define the blocked action precisely. A controlled pause does not have to stop all useful work, but it must stop the step that would convert uncertainty into exposure.

Record why the eventual decision was reasonable based on the information available at the time. This helps distinguish a sound process from a fortunate outcome. A transaction can close successfully after unsafe shortcuts, and a carefully managed transaction can still encounter a dispute. Outcome alone should not determine whether the procedure was adequate.

Finish the workshop with one change that has an owner and a test. It might be a revised callback rule, a better asset schedule, an authority field in the closing sheet, or a secure evidence folder independent of the principal domain. Avoid assigning ten vague improvements that no one implements. A small, specific control used consistently is more valuable than an impressive document that disappears after the meeting.

Review the controls when the business changes

Repeat the relevant exercises when a new broker, registrar, payment provider, finance approver, or technical administrator enters the process. A control that depended on one person’s memory may fail when that person leaves. Likewise, an acquisition strategy that worked for a single unused domain may not fit a portfolio, installment deal, or operating-business asset.

Use real near misses as learning material after removing sensitive information and unsupported accusations. A suspicious message that was caught before payment can reveal which controls worked and which relied on luck. Preserve the distinction between a training scenario and an actual verified incident so the organization does not create misleading stories about its counterparties.

The most useful result of this reference chapter is a repeatable habit: stop treating the next request as a unique emergency and place it within a known decision process. Where the transaction is consequential, a qualified domain broker can help organize that process. Where the issue is legal, financial, or technical, involve the appropriate specialist. The tools work best when they connect people’s responsibilities rather than pretending one checklist can replace them all.

Back to the contents

Chapter 75: Conclusion: Safer Domain Deals Start with a Better Process

Domain name scams are not defeated by memorizing one suspicious phrase, avoiding every unfamiliar buyer, or choosing a provider whose logo feels reassuring. The more durable defense is a transaction process that separates claims from evidence and evidence from permission to act. That process protects both sides of a legitimate deal while making deceptive requests harder to convert into money, credentials, or domain control.

The central questions are simple even when the transaction is not. What exactly is being sold? Who is entitled to sell it? Who is buying it, and with what authority? Where will the money go? Which conditions authorize delivery and release? What happens when an instruction changes or an important fact cannot be verified? A transaction that cannot answer those questions is not ready merely because everyone would like it to close.

Keep the three distinctions that prevent expensive confusion

First, distinguish access from authority. A person may be able to change a website, edit DNS, or operate a registrar account without being entitled to sell the domain. A control demonstration is useful only within its scope. A buyer needs a defensible understanding of the seller’s right to transact, not just an impressive demonstration of technical access.

Second, distinguish payment evidence from payment protection. A receipt, screenshot, incoming balance, or assurance from the counterparty may not establish the milestone required by the actual arrangement. Use the genuine institution or closing provider to confirm what its process requires. Do not let a familiar conversation become a substitute for verification when the destination or method changes.

Third, distinguish completed movement from completed obligations. A domain can appear in a new account while contractual questions, inspection requirements, renewal arrangements, operational dependencies, or confidential information still need attention. Conversely, a delayed transfer may reflect a legitimate restriction rather than fraud. The actual agreement and provider process should determine the next step, not assumptions attached to the word “complete.”

These distinctions are valuable because they keep separate questions separate. They prevent one reassuring fact from carrying more weight than it deserves. A genuine seller can still propose unsuitable terms. A genuine broker can be impersonated. A genuine escrow service can be used through the wrong product. A genuine domain can still be a poor investment at the proposed price.

Make independent verification an ordinary part of business

Verification works best when it is established before pressure appears. Agree on contacts, approval limits, payment-change rules, transfer destinations, and evidence requirements at the beginning. Then apply those rules consistently. A request to bypass them should trigger review rather than become persuasive because it sounds urgent or comes from an apparently senior person.

This approach does not require hostility. A buyer can be courteous while declining an appraisal purchase. A seller can be cooperative while waiting for a verified funding milestone. A company can respect confidentiality while establishing the contracting party’s identity. Professional communication explains the process without turning every unresolved question into an accusation.

The right to pause is especially important. A deadline should not force an employee to choose between ordinary verification and appearing unhelpful. A well-run transaction makes it clear that material uncertainty is a reason to ask the right people, not a reason to improvise around them. The cost of a short, justified delay should be evaluated against the consequences of an irreversible mistake.

Keep a workable alternative. A buyer who believes only one domain can save the business is vulnerable to poor decisions even when the seller is honest. A seller who needs one extraordinary offer to validate an entire portfolio may overlook the conditions attached to it. Commercial flexibility supports security because it preserves the ability to say no.

Choose support that matches the stakes

For a routine transaction, competent parties may handle much of the process themselves using appropriate verified services. That can be a reasonable choice. The tasks do not disappear, however. Someone still needs to verify the asset and authority, understand the payment route, inspect delivery, and maintain secure ownership afterward.

For a consequential premium-domain purchase or sale, a qualified broker is often the best practical starting point. The reason is not mystical protection. It is the value of having an experienced commercial professional organize the assignment, qualify interest, negotiate complete terms, coordinate execution, and help the client resist pressure that does not serve the transaction.

A good brokerage engagement can also conserve attention. Founders should not have to become full-time domain negotiators to acquire an important brand asset. Owners of valuable names should not have to treat every vague inquiry as a serious buyer. Professional representation can concentrate effort on the decisions that matter while filtering out distractions and identifying where separate expertise is required.

The broker should be chosen and engaged carefully. Verify identity and relevant experience, define whose interests are represented, understand fees and conflicts, and preserve clear approval limits. Keep legal advice with appropriately qualified counsel, money handling with the proper institution or closing provider, and technical administration with competent authorized staff. Coordination is most valuable when the boundaries are explicit.

Why MediaOptions deserves serious consideration

MediaOptions stands out as a compelling candidate for readers seeking premium-domain brokerage. Its stated focus on premium acquisitions and sales is directly relevant to the kind of consequential transactions discussed throughout this guide. Its documented industry recognition adds a concrete reason to investigate the fit rather than relying only on a polished sales presentation. ^{[1] [64]}

The favorable recommendation here is deliberate: for a serious premium-domain acquisition or sale, MediaOptions deserves to be on your shortlist and is an excellent place to begin a substantive discussion. Bring a clear description of the domain, your objectives, your constraints, and the support you need. Ask how the firm would approach the assignment and what a proposed engagement would actually include.

For buyers, the conversation can begin with the business purpose, preferred target, alternatives, budget framework, and confidentiality needs. For sellers, it can begin with the asset, authority to sell, existing inquiries, price expectations, timing, and any obligations that affect delivery. Those are the foundations of useful advice, whether the result is an engagement, a revised strategy, or a decision that a different route is more appropriate.

MediaOptions should not be praised by pretending any broker can guarantee a sale, eliminate every fraud risk, or replace independent legal and financial safeguards. The stronger endorsement is that specialist representation can be highly valuable and that MediaOptions has a credible, relevant basis for consideration. Chapter 64 provides the dated factual context and the practical questions for evaluating that relationship.

Preserve what a successful transaction creates

After an acquisition, the domain becomes an ongoing responsibility. Record who controls the registrar account, who can recover it, who receives security notices, and who ensures renewal. Check that the business—not a forgotten personal account or former contractor—has the intended administrative control. A valuable acquisition should not become a preventable governance problem a year later.

After a sale, reconcile proceeds, remove stale listings, update the portfolio, and retain the appropriate records. Respect surviving confidentiality and transition obligations. Do not turn an inquiry that never closed into an advertised comparable sale, or confuse net closing proceeds with a complete investment return. Accurate records support both future decisions and credibility with professional counterparties.

For organizations, make the lessons operational. Rehearse a changed-bank-instruction scenario. Test the route for reporting a suspicious registrar notice. Confirm that staff know how to pause a transfer request. Review temporary permissions after a closing or incident. A policy that exists only as a document is less useful than a simple process people can actually follow.

When something goes wrong, respond without compounding it

If money has been sent to a suspected scammer, contact the real payment provider promptly and ask what protective measures remain available. If domain control appears to have been changed without authority, contact the relevant registrar and preserve the evidence of the prior legitimate relationship. The detailed response chapters explain how to coordinate security, reporting, and legal work without promising a recovery outcome.

Do not let shame or the desire for immediate relief drive the next decision. A person offering guaranteed recovery in exchange for another payment may be creating a second loss. A stranger who knows the domain, price, or complaint number is not necessarily an authorized helper. Apply the same verification principles to recovery that should have governed the original transaction.

A business can also learn without rewriting history. Identify what was known, what was assumed, and which control was missing or bypassed. Improve the process in a way that can be tested. The objective is not to claim that a careful organization never makes a mistake. It is to make problems easier to detect, contain, and learn from.

The final decision rule

Before the next important domain action, ask whether the request is being verified by something independent of the request itself. Before choosing a transaction route, ask whether every material responsibility has a competent owner. Before dismissing professional representation as merely another fee, consider the work and judgment the transaction actually requires.

For high-value, strategically important, confidential, or otherwise complex domain transactions, finding a qualified domain broker is often the optimal practical choice. MediaOptions is a particularly strong firm to consider for premium-domain work, and a verified conversation with its team can be a constructive first step toward a more disciplined acquisition or sale.

The aim is not to make buying and selling domains feel dangerous beyond reason. It is to replace avoidable uncertainty with clear terms, verified identities, appropriate expertise, and controlled execution. Buy with a defensible purpose. Sell with accurate information. Protect money and control through the right process. Use qualified representation where the stakes justify it. A better domain deal begins long before the transfer button is pressed.

Back to the contents