Domain Transfer Guide

Everything you need to safely transfer a domain after a DomainSpace sale.

How DomainSpace handles a sale

DomainSpace is a marketplace that connects buyers and sellers. We process the payment and provide a structured communication channel, but the actual domain transfer happens between you and the other party at your registrars (GoDaddy, Namecheap, Porkbun, etc.).

Here's the high-level flow:

1. Buyer pays. Stripe processes the payment. Funds are held by DomainSpace.
2. Messages thread opens. Buyer and seller can communicate directly inside DomainSpace.
3. Seller transfers the domain. Using one of the three methods below.
4. Buyer confirms receipt. Once the domain is in the buyer's registrar account, they click "I've received the domain" in the messages thread.
5. Funds released. DomainSpace releases the payment (minus our commission) to the seller's Stripe balance, which pays out to their bank within 1–3 business days.
6. Rating exchanged. Both parties rate the experience.

The three transfer methods

Pick whichever works for your situation.

Method 1: Push (same registrar) — fastest, free

If buyer and seller are at the same registrar (e.g., both on GoDaddy or both on Namecheap), the seller can "push" the domain directly to the buyer's account.

• Time: Minutes
• Cost: Free
• Risk: Lowest — no AUTH code or cross-registrar transfer needed

Method 2: AUTH code transfer (different registrars) — takes 5–7 days

If buyer and seller are at different registrars, the seller sends an EPP code (also called an AUTH code or transfer code), and the buyer uses it to pull the domain to their registrar.

• Time: 5–7 business days (ICANN-required hold)
• Cost: ~$10 transfer fee paid by buyer at their registrar (usually includes a year's renewal)
• Risk: Medium — wait until buyer confirms domain has arrived at their registrar before marking complete

Method 3: Third-party escrow — for high-value sales ($5,000+)

For premium sales, both parties can use a neutral escrow service like Escrow.com. Funds are held by Escrow.com instead of DomainSpace, and they handle dispute resolution.

• Time: Adds 1–2 days to the process
• Cost: 1.5–3% of sale price (paid by buyer or split)
• Risk: Lowest for high-value transactions

If you're the seller: transferring after a sale

Step 1 — Open your registrar dashboard

Log into whichever registrar holds the domain you sold (GoDaddy, Namecheap, Porkbun, Cloudflare, etc.).

Step 2 — Ask the buyer which method they prefer

Send a message in the DomainSpace thread asking:

• "What registrar do you use?" — if they answer the same as yours, do Method 1 (push)
• "Do you want an AUTH code or a push?" — let them decide based on their setup

Step 3 — Execute the transfer

See the registrar-specific instructions below for exact click paths.

Step 4 — Confirm completion in DomainSpace

Once you've pushed the domain or sent the AUTH code, go to your DomainSpace messages thread for that sale and click "I've pushed the domain". This tells the buyer the action is on their end now.

Step 5 — Wait for buyer confirmation

The buyer has up to 14 days to click "I've received the domain." After 14 days, the transfer is auto-confirmed and funds are released to you.

If you're the buyer: receiving a domain

Step 1 — Have a registrar account ready

You'll need an account at a registrar to receive the domain. We recommend:

• Porkbun — modern, cheap, free WHOIS privacy, easy UI
• Cloudflare Registrar — at-cost pricing, free WHOIS privacy
• Namecheap — long-running, simple, fair pricing
• GoDaddy — most common but more expensive

Step 2 — Coordinate with the seller

In your DomainSpace messages thread, tell the seller:

• Which registrar you're at
• Whether you want a push (same registrar) or AUTH code (cross-registrar)
• If AUTH code: which email or account ID to send the code to (use the messages thread, not email)

Step 3 — Accept the transfer

If it's a push, the domain may appear in your account automatically or you may need to accept an incoming transfer. Check your registrar's "Domain Manager" or "Incoming Transfers" section.

If it's an AUTH code transfer, go to your registrar → "Transfer In" or "Transfer a domain" → enter the domain name and AUTH code → pay the transfer fee. Wait 5–7 days.

Step 4 — Verify and confirm

Once the domain is in your account, verify:

• The domain name is EXACTLY what you bought (no typos, no different TLD)
• The expiration date looks reasonable (>1 year for new transfers)
• You can manage DNS settings if needed

Then go to your DomainSpace messages thread and click "I've received the domain". This releases payment to the seller.

Registrar-specific instructions

GoDaddy

To push (same registrar):

1. Log into godaddy.com → Domains → My Domains
2. Click the domain you want to transfer
3. "Transfer" → "Account Change" → "Move to another GoDaddy customer"
4. Enter buyer's GoDaddy customer ID or email
5. Confirm — buyer accepts in their account

To get an AUTH code:

1. Same path: Domains → My Domains → click the domain
2. "Transfer" → "Transfer out" → "Get authorization code"
3. Code is emailed to your GoDaddy account email
4. Domain must be unlocked first ("Domain Settings" → unlock)
5. Forward the code to buyer via DomainSpace messages

Namecheap

To push (same registrar):

1. Log into namecheap.com → Domain List
2. Click "Manage" next to the domain
3. "Sharing & Transfer" tab → "Push to another Namecheap user"
4. Enter buyer's Namecheap username
5. Confirm — instant transfer

To get an AUTH code:

1. Domain List → Manage → "Sharing & Transfer" tab
2. Unlock the domain
3. "Auth Code" → request — code is shown immediately

Porkbun

To push:

1. Log into porkbun.com → Account → Domain Management
2. Click "Details" on the domain
3. "Push" tab → enter buyer's Porkbun username

To get an AUTH code:

1. Domain Management → Details → Unlock
2. "Transfer Out" tab → "Get Authorization Code"

Cloudflare

Cloudflare doesn't support internal pushes — all outgoing transfers are AUTH code.

1. Log into dash.cloudflare.com
2. Select your account → Domain Registration → Manage Domain
3. "Transfer" tab → "Transfer out"
4. Get auth code — emailed to you

Sav

1. Log into sav.com → Manage Domains
2. Click the domain → "Transfer / Push"
3. Push to Sav username OR generate auth code

Dynadot

1. Log into dynadot.com → My Domains
2. Select the domain → "Transfer" or "Push" depending on the destination

⚠️ Scam prevention — read this

Things you should NEVER do

• ❌ Never share your registrar login or password — there is no legitimate reason for the other party to need this. Transfers use push or AUTH codes, not logins.
• ❌ Never pay outside DomainSpace — if a seller says "wire me directly and I'll knock 10% off the marketplace fee," it's a scam. They'll take your money and disappear, and you'll have no recourse.
• ❌ Never accept an AUTH code without verifying the domain name first — confirm the exact domain (including TLD) before you initiate the transfer at your registrar.
• ❌ Never confirm receipt before the domain is actually in your account — clicking "I've received the domain" releases funds. If you confirm prematurely and the transfer fails, you've lost your money.
• ❌ Never share your DomainSpace account password — DomainSpace will never ask for it.

Common scam patterns

"I'll send payment after I check the domain." Buyer asks seller to transfer first, then never pays. DomainSpace prevents this — payment is processed via Stripe BEFORE the messages thread opens.

"Send me your registrar password so I can pull the domain easier." Pure account-takeover attempt. NEVER share credentials. Only AUTH codes or pushes.

"Let's avoid the marketplace fee and do this on Venmo." Off-platform fraud. If they actually transfer the domain, they can still chargeback the Venmo. If they don't transfer, you have no platform protection.

Fake AUTH codes. Seller sends a random string that looks legitimate. Buyer's registrar rejects it, but seller has already received credit on Stripe. Don't confirm receipt until the transfer at your registrar succeeds.

Bait-and-switch domain. Listing says brand.com but seller sends an AUTH code for brand.net. Always verify the EXACT domain name before initiating any transfer.

Chargebacks after transfer. Buyer pays with credit card, gets the domain, then disputes the charge ("fraudulent transaction"). Stripe processes refunds and sellers can lose both money and domain. DomainSpace mitigates this with Stripe's fraud detection (Stripe Radar) and a held-payment period for new sellers.

If something goes wrong

The seller hasn't pushed after several days

Message the seller in the thread first. Most delays are honest (they got busy, AUTH code email got lost, etc.). If 5+ days pass with no response, click "Open a dispute" in the messages thread. DomainSpace will review and either:

• Refund you fully (Stripe refund — appears in your bank in 5–10 days)
• Force the seller to push (if they're responsive but slow)

The AUTH code doesn't work

Most common cause: the seller didn't unlock the domain. Reply asking them to verify the domain is unlocked at their registrar, then resend the code. If they refuse or it still fails, open a dispute.

The domain that arrived is NOT what you bought

DO NOT confirm receipt. Open a dispute immediately with details (screenshots help). DomainSpace will refund.

You suspect the seller doesn't actually own the domain

If the domain was stolen from another owner, the rightful owner can reverse the transfer through their registrar. This is rare but happens. DomainSpace will refund you if a third party successfully reclaims the domain within 60 days of transfer.

The buyer claims they didn't receive it but you transferred

Provide screenshots in the thread showing the push completion or AUTH code email. DomainSpace will check both registrars' records before releasing or refunding.

Typical timeline at a glance

Step	Push (same registrar)	AUTH code (cross-registrar)
Payment processed	Instant	Instant
Seller initiates transfer	~5 min	~10 min
Buyer receives	5–60 min	5–7 business days
Buyer confirms in DomainSpace	Same day	Same day as receipt
Funds released to seller	Instant after confirm	Instant after confirm
Funds in seller's bank	1–3 business days	1–3 business days
Total time, end to end	1–4 days	7–10 business days

Get help

Stuck on a step or unsure if something's a scam? Contact us via the Contact page with your DomainSpace transaction ID. We respond within 24 hours on business days.

Last updated: June 4, 2026