How Domain Backorders Work (And Why You Should Doubt One in 2026)
By NorwegianSpark Editorial — written with AI assistance and reviewed by the NorwegianSpark SA editorial team
What a backorder actually is
A backorder is not a reservation. Nobody is holding the name for you. It is an instruction to a service: at the exact instant this domain becomes registrable again, try to register it on my behalf, faster than everyone else trying the same thing.
That distinction is the whole article. A reservation succeeds by default. An attempt succeeds if it wins a race, and on a name anyone else wants, it usually does not.
Understanding the timeline is what tells you whether you are placing a sensible bet or paying for a lottery ticket with good branding.
The clock, and the two parts of it that are actually fixed
Most of the expiry timeline is set per registry and per registrar, and the tables you see online that give exact day numbers for every stage are averaging across policies that genuinely differ. Two things are published by ICANN and are worth quoting rather than paraphrasing.
From ICANN's own description of the EPP status codes, checked at icann.org on 6 September 2026, the pendingDelete status "indicates that your domain has been in redemptionPeriod status for 30 days and you have not restored it within that 30-day period." And once in that state, "your domain will remain in this status for several days, after which time your domain will be purged and dropped from the registry database. Once deletion occurs, the domain is available for re-registration in accordance with the registry's policies."
So: thirty days of redemption, then several days of pending delete, then the drop. Those are the two stages closest to the moment you care about, and they are the ones with a published shape.
What is not fixed is the earlier part. After a registration lapses, there is typically an auto-renew grace period during which the registrar can still take the renewal — ICANN describes autoRenewPeriod as "a grace period provided after a domain name registration period expires and is extended (renewed) automatically by the registry", during which the registrar can delete the name and get a credit. How long that runs, whether the registrar auctions the name instead of letting it drop, and what restoring it costs are all registrar and registry decisions.
Read the status codes, not the countdown
The single most useful skill for a backorder buyer is reading the domain's current status directly rather than trusting a list. The codes are published and unambiguous:
| Status | What it means for you |
|---|---|
| autoRenewPeriod | Expired but auto-renewed by the registry. The owner can still keep it easily. Very early. |
| redemptionPeriod | Out of service, owner can still restore it for a fee. Thirty days from here to pending delete. |
| pendingDelete | Not in redemption any more. Drops in several days. This is the real countdown. |
| pendingRestore | The owner is taking it back. Stop. |
| clientHold / serverHold | Not resolving in DNS, but not necessarily expiring. Often a dispute or a payment problem. |
| clientTransferProhibited | A normal, healthy lock set by the registrant. Tells you nothing about expiry. |
pendingRestore is the one people miss. It means the previous owner has paid to get the name back and your backorder is dead. Owners restore far more often than expiry lists suggest, particularly on names that are actually good — which are, inconveniently, exactly the names you wanted.
What happens at the drop
When a name is purged from the registry, it becomes registrable again — globally, at once. What follows is not a queue. It is a burst of automated registration attempts hitting the registry within milliseconds of each other, submitted by systems built for this and connected for this.
That is why manual registration at the drop is not a strategy for anything desirable. By the time a person can type, it is over. Drop-catching services exist because the registry connection and the retry logic are the product.
The practical consequences:
- A backorder buys you a machine's attempt, not a human's. That is a genuine advantage over doing nothing.
- Different services have different registry access, and the one that catches a name is not always the one you paid.
- If nobody else wants the name, you get it easily. If several people do, you almost certainly end up in a private auction between the backorder holders — which means the price is not the backorder fee, and you should decide your ceiling before that starts.
- Many good names never drop at all. They are auctioned by the losing registrar during the expiry window and never reach the public drop.
Why you should doubt a backorder
Here is the counter-argument, and it is stronger than the industry likes to admit.
Most backorders fail. Not because the services are bad, but because the two failure modes are structural: either the owner renews or restores, which is common on names worth having, or several catchers compete and the outcome becomes an auction you may lose anyway.
The fee model varies and is easy to misread. Some services charge only on success, some charge upfront, some credit failed attempts toward a future one, and some do a mix. Whether your money is at risk on a miss is a per-service question, and it is the first thing to establish. We are not printing prices here: they change, they differ per extension, and the number you would act on has to come from the service's own current page.
Placing a backorder can be visible. On some platforms, backorder interest is public or semi-public. Interest attracts interest.
And the honest arithmetic: if you place backorders across a wide list of mediocre names, you will catch several and want none of them. If you place one on a genuinely good name, you will probably lose it. The strategy only pays where you have a specific reason to want a specific name that few other people have identified.
When a backorder is the right move
- The name is unusual to you and boring to everyone else — a niche term, a personal name, a term of art in a small field.
- You have checked the audit questions first and would actually want it. Catching a spam-history domain is a loss, not a win. Our expired-domain audit is the checklist.
- You are willing to wait years. Names come around again.
- You have decided, in writing, what you would pay at auction if it comes to that.
When it is not
- The name is short, generic and in a popular extension. Assume it is watched by professionals with better registry access than your service.
- The current owner has an active business on it. Expiry lists include names that are expiring on paper and being renewed in practice.
- You need the name on a schedule. Backorders have no schedule.
- The domain is a variant of somebody's trademark. Catching it is the beginning of a dispute, not the end of a search. See what happens in a UDRP dispute.
What to do instead, or as well
- Approach the current owner. For a name someone is actively renewing, buying it is far more likely to work than outliving them. How to buy a domain name that is taken covers the approach.
- Watch the auctions. Many expiring names are sold at auction before they ever drop. The domain auction guide covers the platforms.
- Spread across services if the name matters and you can afford it. Different catchers, different odds.
- Take a different name. The domain generator and how to choose a domain name are quicker and much more likely to end with you owning something.
If you are on the other side of this
If you are reading because your domain is on somebody's list, the fix is boring and total: auto-renew on, a payment method that is not about to expire, a contact address you actually read, and a calendar reminder as a human backstop. Names are lost to expired cards far more often than to anything dramatic. Renewing and protecting your domains covers the habits, and how to protect a domain from hijacking covers the rest.
The redemption stage exists precisely because people make this mistake — but a restore is expensive and the fee is set by your registrar, not by anyone you can argue with. Renewing on time means the whole timeline in this article never applies to you.
Last updated:
