BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Handling a Domain Transfer Dispute: The Four Routes, the ICANN Policies, and How to Get Your Domain Back
A domain transfer dispute is what you have when a name moved, or failed to move, and you believe that outcome is wrong. The seller took your money and never released the domain. The transfer was refused for no reason you understand. Worse, the domain left your account entirely without your say-so. Each of those is a different problem with a different remedy, and the single biggest mistake is treating them as one.
This guide sorts a transfer dispute into the four routes it can take, then walks the path for each one. It is written for the buyer and the registrant, not for a registrar legal team, and it cites the real ICANN, WIPO, and National Arbitration Forum policies so you know which clock you are on and what relief is realistic.
One theme runs through all four routes: the cleanest dispute is the one that never happens. A documented, escrow-backed acquisition from a vetted source leaves a clear chain of custody, which is exactly what a contested transfer lacks. SEO Domains operates the curated marketplace where aged and expired domains change hands through that documented, ICANN-accredited process, so the handover is recorded before it is ever questioned.
What is a domain transfer dispute?
A domain transfer dispute is a disagreement over whether a domain was correctly moved, or correctly kept, between two parties or two registrars. It covers a seller who will not release a domain you paid for, a transfer that was refused, and a transfer that happened without the owner’s permission. The remedy depends entirely on which of those you are facing.
The phrase trips people up because “domain dispute” gets used for two unrelated things. One is a fight over who holds a name on trademark grounds, which is a name-ownership dispute. The other, the subject of this guide, is a fight over a transfer event itself: the act of moving a domain from one account or registrar to another, and whether that act was correct.
The two senses, and why you landed here
Search the term and the results split down the middle. Half are ICANN policy pages and registrar forms about contested transfers. Half are law firms writing about cybersquatting and trademarks. If your problem is “the name is mine by right because of my brand,” that is the trademark route, covered in Route 4 below. If your problem is “the transfer was handled wrongly,” you are in the right place for the other three routes.
Why the distinction decides everything
Picking the wrong route wastes the one resource a dispute punishes hardest, which is time. Filing a trademark case when what you really have is an unauthorized transfer means paying thousands of dollars to the wrong process. Waiting on your registrar when the only body that can reverse a registrar-to-registrar transfer is a dispute panel means missing a deadline. The next section is the map that keeps you on the correct path from the first day.
The four kinds of transfer dispute, and which one is yours
Transfer disputes fall into four routes: a marketplace or escrow transaction dispute between a buyer and a seller, an unauthorized or fraudulent transfer handled through your registrar and ICANN, a registrar-level dispute resolved under ICANN’s Transfer Dispute Resolution Policy, and a trademark dispute resolved under the UDRP. Match your situation to one before you act.
Read the four cards below and find the one that describes your situation. The route name tells you which section to jump to and, more importantly, which body holds the power to fix it. Almost every wasted week in a transfer dispute comes from someone working the wrong card.
Route 1
Marketplace or escrow transaction dispute
You bought a domain and the seller will not transfer it, or you sold one and the buyer claims it never arrived. The dispute is between two people, and the marketplace or escrow agent that held the money is the referee.
Route 2
Unauthorized or fraudulent transfer
The domain left your account without your consent, typically after an account compromise or a hijacked email. Speed matters more here than anywhere else. Your registrar is the first call, and ICANN compliance is the escalation.
Route 3
Registrar-level dispute (TDRP)
A transfer between two registrars is itself contested, either because it was allegedly fraudulent or because it was wrongly refused. Only a registrar can file this one, under ICANN’s Transfer Dispute Resolution Policy.
Route 4
Trademark dispute (UDRP)
The real argument is over who has the right to the name, not how it moved. This is a trademark matter for the UDRP, decided by WIPO or the National Arbitration Forum, not a transfer matter at all.
Notice the pattern. Route 1 is a private transaction settled by a marketplace. Route 2 is an emergency you escalate. Route 3 is a registrar-only legal proceeding you can only ask your registrar to start. Route 4 is a different category entirely. The rest of this guide takes them one at a time, in the order you are likeliest to need them.
First moves: what to do in the first 48 hours
In the first 48 hours of any transfer dispute, document everything, lock down your accounts, contact the registrar in writing, and only then choose your route. These steps apply across all four routes and protect your position before any formal process begins.
Before you decide which route is yours, take five protective actions that help in every case. They cost nothing, they preserve evidence, and a panel or a compliance officer later will ask whether you took them.
-
Capture the evidence before it changes
Screenshot the WHOIS or RDAP record, the registrar account, every confirmation email, the transfer authorization email, and any marketplace or escrow message thread. Save the timestamps. A dispute is won on a record, and records get overwritten as a transfer completes.
The mistake: waiting a week, by which point the registration record has updated and the original email trail is buried. Evidence collected after the fact carries far less weight.
-
Secure every account immediately
If the transfer was unauthorized, assume the attacker still has access. Reset the registrar password and the email account tied to it, enable two-factor authentication, and revoke any active sessions or API keys. The transfer is the visible symptom of a wider compromise.
The mistake: chasing the domain while leaving the breached email open, so the attacker re-initiates the next move while you argue about the first one.
-
Contact the registrar in writing, on the record
Open a support ticket and state the facts plainly: the domain, the dates, and what you believe went wrong. ICANN guidance is explicit that the registrar is the first place to go for an unauthorized transfer, because the registrar is the only party that can act on the registration directly.
The mistake: relying on a phone call with no paper trail. If it is not in writing, it did not happen as far as a later proceeding is concerned.
-
Decline a pending transfer while you still can
If the transfer has not yet completed, the major registrars include a Decline option in the transfer-approval email, and refusing it stops the move before it finishes. A transfer that is still in its pending window is far easier to halt than one to reverse.
The mistake: ignoring the approval email, letting the auto-approval timer run out, and turning a five-minute decline into a multi-week reversal fight.
-
Identify your route, then escalate to the right body
With the evidence saved and the bleeding stopped, match your situation to one of the four routes in Figure 1. Only now do you choose between the marketplace, an ICANN complaint, a registrar TDRP request, or a UDRP filing. The right body is the one with power over your specific problem.
The mistake: firing off a UDRP complaint or an ICANN form before you know which route fits, paying fees or burning a deadline on the wrong process.
Route 1: a marketplace or escrow transaction dispute
A marketplace or escrow transaction dispute is a disagreement between a buyer and a seller over a domain sale. The escrow agent or marketplace that held the funds is the referee, and the standard remedies are releasing the domain, refunding the buyer, or cancelling the transaction. Escrow exists precisely to make this route rare.
This is the commonest transfer dispute for anyone buying domains in the aftermarket, and it is the one the search results almost entirely ignore. The setup is plain: money changed hands, or sat in escrow, and now the handover has stalled. The seller drags their feet, the buyer claims the domain never arrived, or one side stops responding mid-transfer.
How escrow is meant to settle it
An escrow service holds the buyer’s funds until the domain is verifiably in the buyer’s control, then releases the money to the seller. That structure removes the trust problem from the deal. DomainSherpa and the major marketplace escrow services describe the same flow: the buyer deposits, the agent verifies, the seller transfers, the buyer confirms control, and only then are funds released.
The refund window and the chargeback trap
The mechanics matter when a deal goes wrong. On a major marketplace such as Sedo, a buyer who raises a dispute can be refunded within a fixed window, reported at roughly 14 days, which protects the buyer but can leave a seller exposed if the domain has already been handed over. A marketplace also reserves the right to cancel an escrow and reverse a transfer when one party will not cooperate after repeated requests. For sellers, this is why a credit-card chargeback after delivery is the nightmare scenario, and why escrow services advertise chargeback protection as a core feature.
Each platform sets its own fees and timelines for this. Sedo charges a 3 percent commission with a 60 US dollar minimum on a sale, and Afternic, part of the GoDaddy family, charges a 20 percent commission that bundles the sale and escrow handling. Read the dispute terms of the platform you used, because the platform’s own policy is the rulebook that governs Route 1.
What to do, in order
- Open the dispute inside the marketplace or escrow platform, not over private email, so the agent has jurisdiction and a record.
- Provide the transaction reference, the dates, and proof of payment or proof that the domain never reached your control.
- Let the agent mediate. The agent holds the funds and the leverage, which is the entire reason to buy through escrow rather than a direct wire.
- If the platform cancels the deal, confirm the domain returns to the correct party and the funds return to yours before you close the case.
The lesson of Route 1 is structural. A transaction dispute is only solvable when a neutral party held the money. A direct, off-platform wire to a stranger has no referee and no refund window, which is where this route turns from a mediation into a loss. Sourcing through a marketplace that builds escrow into every sale is what keeps a transaction dispute small.
Route 2: an unauthorized or fraudulent transfer
An unauthorized transfer is a domain that left your account without your permission, usually after an account or email compromise. Contact your registrar first, file an ICANN Unauthorized Transfer Complaint if the registrar does not resolve it, and understand the hard limit: ICANN cannot order a registrar to hand the domain back.
This is the route that feels like an emergency, because it is one. A domain you owned is suddenly registered to someone else, and the clock is running while the new holder races to sell or move it again. The good news is that ICANN has a defined registrant path. The hard news is that the path has a ceiling, and the honest guides say so plainly.
The registrant path, step by step
ICANN’s own registrant guidance is clear about the order of operations. Contact the registrar immediately, because the registrar is the only party that can act on the registration. If the registrar does not put it right, you escalate to ICANN by submitting an Unauthorized Transfer Complaint through ICANN Contractual Compliance. ICANN reports that the bulk of contractual compliance complaints reach a resolution in roughly 17 days. In certain cases the registrar can also initiate a registrar-level dispute on your behalf, which is Route 3.
The hard limit you need to hear up front
Here is the line every fear-free guide needs to state and the law-firm guides omit. ICANN says directly that it does not have contractual authority to require a registrar to transfer a domain name back to a different registrar or registrant, even when the transfer resulted from unauthorized access to your email account or login credentials. A compliance complaint enforces the registrar’s contractual obligations. It does not guarantee the domain comes home.
What that leaves you
The realistic toolkit for an unauthorized transfer is therefore a stack, not a single button:
- The registrar. The fastest and the direct lever, and the place to start. A registrar that recognizes a fraudulent transfer can coordinate with the gaining registrar to reverse it inside the early window.
- ICANN Contractual Compliance. The enforcement lever. It compels the registrar to meet its obligations and is resolved on a roughly 17-day cadence, but it cannot itself force a return.
- A registrar-initiated TDRP. Where the transfer was registrar-to-registrar and allegedly fraudulent, your registrar can file under the Transfer Dispute Resolution Policy. That is the one process that can order a reversal, covered next.
- A court. The backstop when policy runs out, and the only authority that can compel a return against a holder who will not cooperate.
Route 2 is the strongest argument in this entire guide for prevention. A locked domain with two-factor authentication and a clean registrar account is rarely stolen in the first place, and a domain acquired through a documented, escrowed handover starts its life under your control with a record to prove it.
Route 3: the registrar-level dispute and ICANN’s TDRP
ICANN’s Transfer Dispute Resolution Policy, the TDRP, resolves disputes between two registrars over a transfer. Only a registrar can file it, within a 12-month statute of limitations, and a panel can order a contested transfer reversed. The registrant cannot file directly, but can ask their registrar to.
The TDRP is the policy the top search results point to, and it is widely misunderstood because of one fact: it is a registrar-versus-registrar process, not a registrant tool. You cannot file a TDRP yourself. What you can do is understand it well enough to ask your registrar to use it and to know what a successful outcome looks like.
Who can file, and on what grounds
A TDRP complaint is brought by one registrar against another. ICANN’s policy frames two main triggers. A Losing Registrar files when it alleges a transfer away was fraudulent. A Gaining Registrar files when it alleges a transfer was wrongly refused, which the policy calls an improper NACK, short for a negative acknowledgment, the technical term for a denied transfer.
The two levels of a TDRP proceeding
The process has two possible levels, and a registrar can use one or both. At the first level, a registrar files with the relevant registry operator, and the registry’s decision can be appealed to a dispute resolution provider. At the second level, a registrar files directly with an ICANN-approved dispute resolution provider, but doing so forfeits the right to appeal that provider’s decision. The approved providers include the National Arbitration Forum and the Asian Domain Name Dispute Resolution Centre.
Every clock in one place
The deadlines are the part worth memorizing, because a transfer dispute lives and dies on them. The statute of limitations to file a TDRP complaint is 12 months, raised from the earlier 6-month window. Once filed at the first level, the non-filing registrar has 7 days to respond, with the registry able to grant no more than 5 additional days in special circumstances. The registry operator then has 14 days to review the documentation and decide. At the second level, the arbitrating panel has 30 days to reach a decision.
| Stage | Clock | Who acts |
|---|---|---|
| Statute of limitations to file | 12 months from the transfer | Filing registrar (Losing or Gaining) |
| First-level response window | 7 days, plus up to 5 more by extension | Non-filing registrar |
| First-level review and decision | 14 days | Registry operator |
| Second-level panel decision | 30 days | Dispute resolution provider panel |
| Right to appeal | Preserved at level one, forfeited at level two | Filing registrar’s choice |
What it can order, and what it costs
The relief is the reason a registrant cares. A TDRP panel can order a contested transfer reversed, returning the domain to the registrar that was the registrar of record immediately before the disputed transfer. That is the one mechanism in this guide that can force a registrar-to-registrar reversal, which is why an unauthorized transfer that crossed registrars routes here through your registrar.
The cost is not trivial and is borne by registrars. ICANN warns that TDRP fees can be substantial. The National Arbitration Forum publishes a fee band reported in the range of roughly 1,150 to 4,000 US dollars and above, depending on whether one or three panelists hear the case and the number of domains in dispute. Treat that as a third-party reference figure from the provider, and confirm current fees with the provider directly. The depth of the underlying transfer mechanics that feed a TDRP claim lives in the inter-registrar domain transfer walkthrough.
Route 4: when it is really a trademark dispute (UDRP)
The Uniform Domain-Name Dispute Resolution Policy, the UDRP, resolves trademark disputes over who has the right to a domain name. It is not a transfer dispute. A trademark owner files with WIPO or the National Arbitration Forum, must prove a three-part bad-faith test, and a win results in the domain being transferred or cancelled, with no monetary damages.
This route is here because the search results fold it together with transfer disputes, and a reader who arrived with the wrong problem needs to be sent to the right office. If your complaint is “someone registered a domain that infringes my trademark,” that is a UDRP matter, and it is governed by a completely separate policy from anything in Routes 1 through 3.
The three-part test
To win a UDRP case, a complainant must prove all three elements. First, the domain is identical or confusingly similar to a trademark in which the complainant has rights. Second, the registrant has no rights or legitimate interests in the name. Third, the domain was registered and is being used in bad faith. Miss any one element and the complaint fails, which is why a UDRP is a trademark argument and not a transfer argument.
Cost, time, and outcome
The UDRP is a paid arbitration with published fees. WIPO, the leading provider by volume, lists 1,500 US dollars for a single-panelist case and 4,000 US dollars for a three-panelist case for a standard dispute. The National Arbitration Forum runs a comparable band, reported at 1,300 US dollars for a single panelist and 3,000 US dollars for three. A case typically completes in 60 to 75 days, and after a decision a losing registrant has 10 business days to file a lawsuit before a registrar implements a transfer. WIPO processed 6,614 cases in 2024 and handles around 60 percent of all UDRP disputes.
| Dimension | TDRP (Route 3) | UDRP (Route 4) |
|---|---|---|
| What it resolves | A contested transfer between registrars | Who has the right to the name on trademark grounds |
| Who can file | A registrar only | A trademark rights-holder |
| Decided by | Registry operator or DRP panel (NAF, ADNDRC) | WIPO or NAF panel |
| The test | Was the transfer fraudulent or the NACK improper | The three-part bad-faith test |
| Reported cost | ~1,150 to 4,000 USD and up (NAF band) | 1,300 to 4,000 USD by provider and panel size |
| Typical outcome | Transfer reversed to prior registrar of record | Domain transferred or cancelled, no damages |
The practical takeaway is the same as the opening fork. If the wrong is in how the domain moved, you are in Routes 1 through 3. If the wrong is that the name was never the other party’s to register because it carries your brand, you are in Route 4. Diligence on a name’s history and prior use before you buy it, the kind documented in the expired domain fundamentals hub, is what keeps you from ever inheriting a trademark fight with an aged domain.
Transfer dispute frequently asked questions
The five questions buyers and registrants raise the moment a transfer goes wrong, answered against the ICANN and WIPO policy record and the four-route map this guide draws.
Q1Can ICANN force my domain to be returned after an unauthorized transfer?
No. ICANN states directly that it does not have contractual authority to require a registrar to transfer a domain back to a different registrar or registrant, even when the transfer followed unauthorized access to your accounts. ICANN Contractual Compliance can enforce a registrar’s contractual obligations and resolves the bulk of complaints in roughly 17 days, but the actual return runs through your registrar, a registrar-initiated TDRP, or a court.
Q2Can I file a TDRP myself as the domain owner?
No. The Transfer Dispute Resolution Policy is a registrar-versus-registrar process. Only an ICANN-accredited registrar can file, within the 12-month statute of limitations. As the registrant, your move is to ask your registrar to initiate a TDRP on your behalf when a registrar-to-registrar transfer was fraudulent or wrongly refused. The TDRP is also the one process that can order a contested transfer reversed.
Q3What is the difference between a TDRP and a UDRP?
A TDRP resolves a dispute over a transfer event between two registrars, deciding whether a transfer was fraudulent or a refusal was improper. A UDRP resolves a trademark dispute over who has the right to a name, decided on a three-part bad-faith test by WIPO or the National Arbitration Forum. One is about how the domain moved; the other is about who holds it by right. They are separate policies with separate filers and separate remedies.
Q4A seller took my payment and will not transfer the domain. What do I do?
That is a Route 1 transaction dispute, and your remedy depends on how you paid. If you bought through a marketplace or escrow service, open the dispute inside that platform, because the agent holding the funds is the referee and can refund you or cancel the deal. If you wired a stranger directly with no escrow, there is no referee and recovery is far harder, which is the core reason to buy through an escrow-backed marketplace in the first place.
Q5My transfer was refused. Is that a dispute?
Not always. A refusal, technically a NACK, can be entirely valid. A domain inside its first 60 days, under a transfer lock, or flagged for fraud is refused for cause, and that is the system working. It only becomes a dispute when the refusal was improper, in which case the gaining registrar can raise it under the TDRP. Check whether a legitimate lock applies first, a topic covered in transfer locking and when to unlock and the ICANN’s 60-day transfer rule.
Prevent the dispute at the source: a clean, escrowed acquisition
The cheapest transfer dispute is the one that never happens. A documented, escrow-backed acquisition of a clean aged or expired domain leaves a clear chain of custody, which is exactly what every contested transfer lacks. SEO Domains operates the curated marketplace where that clean handover is built into every sale.
Look back across the four routes and one pattern repeats. A transaction dispute is solvable only because escrow held the money. An unauthorized transfer is preventable with a locked account and a documented handover. A registrar dispute and a trademark dispute both grow from a murky purchase, a domain bought from an unverified seller or with a tainted history. The common thread is the quality and the cleanliness of the acquisition itself.
Why a documented handover changes the odds
A dispute is an argument about what happened, and the side with the record wins it. When a domain changes hands through a verified marketplace with escrow, an authorization-code handover, and an ICANN-accredited transfer, every step is logged. There is a payment record, a release record, and a transfer record. That documentation is the difference between a five-minute clarification and a multi-week proceeding.
The acquisition checklist that keeps you out of a dispute
The same discipline prevents all four routes. Source clean, transfer documented, lock the result:
| Do this at acquisition | The dispute it prevents |
|---|---|
| Buy through a marketplace with escrow built in | Route 1: the seller cannot take payment and vanish |
| Verify the seller and the chain of custody before paying | Route 1 and Route 3: no contested or murky ownership |
| Lock the domain and enable two-factor authentication after transfer | Route 2: a locked, secured name is rarely hijacked |
| Screen the domain’s history and prior use before buying | Route 4: no inherited trademark fight on the name |
| Keep the full transfer record: payment, auth code, completion | All routes: the documented side wins the argument |
Source domains with a clean, documented chain of custody
The legitimate demand behind every transfer dispute is a domain you can own and move without a fight. That is the product. SEO Domains operates the curated marketplace where aged and expired domains are screened across their history and backlink profiles, then sold through escrow with an ICANN-accredited transfer, so the handover is recorded and clean from the first day you own the name.
