A domain marketplace brings discovery, communication, and transaction steps into one place. You still need to decide whether a name fits your project, whether its asking price fits your budget, and whether the handover is workable. Those decisions deserve attention before an attractive listing becomes a purchase.
Spaceship calls its domain selling platform SellerHub. This guide explains a practical way to approach buying or selling through that environment. Start with our Spaceship marketplace overview for orientation, then use the process below to prepare the details that matter in a real transaction.
1. Understand where SellerHub fits
Spaceship’s official SellerHub page describes domain importing, sale pages, search exposure, and transfers handled with its team. Sellers can import names individually or through a CSV file, including domains registered elsewhere. The page also explains that seller payment follows the transfer of domain ownership to Spaceship. Confirm the current transaction instructions for your particular sale before acting.
Treat the platform as the place where a domain transaction is organized. A domain purchase needs its own scope: the exact name, agreed price, payment terms, and transfer requirements. Website files, an email service, social accounts, trademarks, and a functioning business should only be treated as included when the agreement explicitly says so.
A useful first question is simple: what will each party receive, and what must each party do? Write the answer down before comparing a marketplace with another service.
2. Prepare a reliable domain record
For sellers, preparation starts outside the listing editor. Create a record containing the exact domain, current registrar, expiration date, asking price, and person authorized to approve a sale. Add notes about any active website, email, or other service using the domain. This becomes your reference when a buyer asks a question or the transfer team needs information.
Review spelling carefully, including the extension. Similar characters and an overlooked plural can change the asset being offered. Check that the domain is actually present in the account you control and that you can receive account notifications. Resolve missing access or unclear ownership before making a commitment.
Import a small, checked batch first if you manage a larger portfolio. Review the resulting records before uploading the remainder. A spreadsheet error repeated across many names can create inconsistent prices or descriptions. Our domain selling guide provides a broader preparation checklist that works alongside your marketplace account.
3. Build a buyer shortlist around a real use
Buyers should define the name’s job before browsing deeply. Is it the main address of a new company, a shorter address for an established business, or a specific campaign? Write down the audience, languages, acceptable extensions, and launch deadline. These requirements help distinguish an appealing word from a name you can use comfortably.
Shortlist several candidates and record the reason each belongs. Read them aloud, type them from memory, and place them in a sample email address. Ask someone unfamiliar with the project to repeat the spelling after hearing it once. This informal exercise reveals practical friction; it does not establish a universal quality score.
Keep your total budget visible alongside the asking prices. Include room for professional review, transaction charges where applicable, renewals, and the work needed to introduce the name. The domain buying guide explains how to turn that shortlist into a clear acquisition brief.
4. Set listing terms you can honor
A seller’s price should reflect a deliberate decision about an acceptable transaction. Start with the purpose of selling, the evidence behind the price, and the amount you would accept after applicable costs. Keep a private minimum separate from any public asking price. A name can be desirable while your preferred price remains out of reach for a particular buyer.
Review the price and offer options available in your current SellerHub account. If you publish an immediately purchasable price, be prepared to complete a sale on those terms. If the listing invites negotiation, decide who will respond and what information they need before accepting an offer.
Keep listings elsewhere consistent with your intended terms. Maintain a record of every place the domain is offered so you can update availability promptly when a transaction progresses. Avoid making claims about guaranteed traffic, search rankings, or future resale value. Describe the name’s language and possible applications without presenting hypothetical benefits as measured results.
5. Examine the name before committing
Due diligence should answer specific questions. Does the domain match the intended brand? Does its previous use raise concerns for the new project? Are there confusingly similar names in the same market? Is there a clear path to transferring control? Assign responsibility for each question so an assumption does not quietly become a decision.
Review available historical pages and relevant search results with their limitations in mind. An incomplete archive cannot prove that a domain has never been used. A clean looking current page cannot establish the absence of past problems. If a seller makes claims about visitors, revenue, or existing customers, request evidence that matches the exact claim and relevant period.
For a business naming decision, arrange appropriate trademark review before committing substantial resources. Separately, confirm the domain’s renewal price, expiration timing, and any transfer conditions with the appropriate service. Keep these checks proportionate to the transaction, but record unresolved questions. A marketplace listing gives you a place to begin that work; your approval should follow the evidence you obtain.
Keep a dated note of each check and the evidence you reviewed. If something needs clarification, turn it into a direct question for the seller or transaction team. This makes follow-up efficient and lets everyone distinguish a completed check from a task that still depends on an answer.
6. Keep negotiation and payment instructions connected
Communicate in a way that leaves a clear record. State the exact domain, proposed price and currency, and any conditions attached to the offer. Ask when a response is expected rather than assuming a deadline. If your offer depends on a review or a particular completion date, make that dependency explicit before acceptance.
When an agreement changes, restate the complete terms. A lower price combined with a new payment schedule is a different proposal. So is a request to include additional names or other assets. Each party should be able to point to the same written understanding without piecing it together from fragments.
Check the live fee schedule and transaction terms before calculating your final amount. Confirm payment or payout instructions through your authenticated account or the official support route. If a message requests a changed destination or an unexpected step, verify the instruction within that established process before proceeding. Keep transaction identifiers with your records.
7. Plan the transfer and the service handover
Agree on a realistic sequence with the transaction team. Identify the account that should receive the domain and confirm what the seller must do at the current registrar. Ask about any condition that could affect timing. Avoid promising a launch date based on a generic transfer estimate when the domain’s own situation has not been checked.
Domain control and service configuration need separate attention. If the name already supports a website or email, record the relevant DNS settings and decide which services should continue, change, or end. Share only the information necessary for the agreed handover. Keep account passwords and unrelated credentials private.
Once the receiving party has the domain, verify it in the intended account, check the displayed expiration and renewal settings, and confirm the contact details. Then test the website and email setup planned for the new owner. Sellers should retain the completion record and check the transaction’s payout status. An accepted offer, a payment notification, and a finished handover are distinct milestones.
8. Close the transaction with usable records
The final task is to make the result easy to manage. Buyers should file the agreed terms, receipts, transfer confirmation, and renewal information together. Assign responsibility for future domain administration and account recovery. Sellers should remove obsolete listings, update portfolio records, and preserve the documents needed to understand the completed sale.
Review what the transaction taught you. Which questions delayed agreement? Which records were missing? Improve that process before the next listing or purchase. A clear workflow matters more than treating any marketplace as a shortcut around judgment. Use our domain marketplace directory to compare other approaches while keeping the same standards for evidence, written terms, and a confirmed handover.
