How it works

Overview

A domain sale is really two separate things happening in parallel: a payment, and a transfer of control over a domain name at its registry/registrar level. Most bad experiences in the domain aftermarket come from those two things being disconnected — a buyer pays and hopes the seller transfers, or a seller transfers and hopes the buyer pays. Our process keeps them linked: payment is held until transfer is confirmed, on both marketplace-brokered sales.

Buying a domain

1. Browse and evaluate. Review the listing, check any traffic or usage claims, and message the seller if you have questions.
2. Offer or buy now. Submit an offer or pay the listed price. Funds are collected but held by domaining.id, not sent directly to the seller.
3. Seller initiates transfer. Depending on the TLD, the seller either pushes the domain to your registrar account, provides an authorization/EPP code for you to redeem, or updates account contact details if the domain stays at the same registrar.
4. You confirm receipt. Once the domain shows up under your control — visible in your registrar account, or via a WHOIS/registrant check we help verify — you confirm receipt on your order.
5. Funds release. Once confirmed, held funds are released to the seller and the order is marked complete.

Selling a domain

1. List the domain. Add the domain, set a price or enable offers, and describe anything relevant (traffic, backlink profile, prior use, whether it's currently live).
2. Review. We do a quick check that you control the domain before the listing goes live.
3. Accept an offer or a buy-now purchase. Once a buyer pays, you'll see the order move to "awaiting transfer" in your dashboard.
4. Initiate transfer. Unlock the domain, obtain the auth code, and either push it to the buyer's account or hand over the code depending on the TLD and registrar.
5. Get paid. Once the buyer confirms receipt, held funds are released to your payout method, minus any applicable marketplace fee.

The transfer process, honestly

The transfer step is the part of a domain sale most people have the least experience with, so it's worth being specific about what actually happens:

• Same-registrar transfer (push). If both buyer and seller use the same registrar, the seller can usually push the domain directly into the buyer's account within minutes to a few hours, once both accounts are ready.
• Cross-registrar transfer (auth code). For most gTLDs (.com, .net, .org, .co, etc.), the seller unlocks the domain, disables privacy if enabled, and retrieves an authorization (EPP) code. The buyer submits that code at their registrar of choice, which triggers a transfer request that the seller (or the losing registrar) must approve. ICANN rules build in an approval window, and registrars vary in how quickly they process it.
• .id domains. .id domains sit under PANDI (Pengelola Nama Domain Internet Indonesia) and are managed via PANDI-accredited registrars rather than the standard ICANN transfer flow. Some second-level .id categories (like .co.id or .biz.id) require the registrant to hold a valid Indonesian business or personal ID, so a transfer to a buyer who doesn't meet that requirement may need a local proxy/nominee arrangement, disclosed on the listing.
• Domains with active use. If a website, email or app is attached to the domain, transferring DNS too early can cause downtime. We recommend agreeing on a cutover plan with the other party (e.g., updating DNS after content or a redirect is in place) before finalizing.

Realistic timelines

• Same-registrar push: usually a few minutes to a few hours once both accounts are ready.
• Standard gTLD auth-code transfer: typically 1–7 days, depending on how quickly the losing registrar approves the request.
• .id domain transfer: typically 3–14 days, since it depends on the specific PANDI-accredited registrars involved and, for restricted categories, verification of the buyer's eligibility documents.
• Payment settlement: card payments are typically available for release as soon as transfer is confirmed; bank transfers can take 1–3 additional business days to clear before funds show as available to the seller.
• Lease-to-own plans: the domain (or usage rights, depending on the seller's terms) transfers on the schedule set out in the plan — sometimes immediately, sometimes only once the balance is fully paid.

These are typical ranges, not guarantees — registrar processing times and registry requirements are outside our control.

What can go wrong

We'd rather tell you upfront what can slow things down or derail a transfer:

• Domain lock or privacy left on. A seller forgetting to unlock the domain or disable WHOIS privacy is the most common cause of a stalled auth-code transfer.
• Wrong or expired auth code. Auth codes can expire or be regenerated; if a code doesn't work, the seller needs to issue a fresh one.
• Registrar-side delays. Some registrars are slower than others to approve outgoing transfers, and 60-day post-transfer or post-registration locks on some TLDs can block a further transfer attempt.
• Eligibility mismatches on restricted TLDs. A buyer who doesn't meet a restricted TLD's registrant requirements (as with some .id categories) may need extra steps or a different arrangement.
• Disputed representations. If a domain's traffic, backlink or usage history turns out to be materially misrepresented, that's a dispute we'll help mediate using the order's messages and listing history, per our terms of service.
• Buyer or seller unresponsiveness. Transfers need both sides to take action (unlocking, redeeming a code, confirming receipt); an unresponsive party is the main reason an order runs past its expected timeline.

If a transfer stalls, support can step in to help coordinate between both parties before any funds are released or an order is cancelled.