Domain backorder: how the drop catching process works

The reality is a high-speed infrastructure race measured in milliseconds, where the difference between catching a domain and losing it comes down to registrar network size, EPP (Extensible Provisioning Protocol) API access, and the precise timing of when a registry actually processes its daily drop queue. After placing hundreds of backorders over the years—and winning far fewer than I'd like to admit—I can tell you the gap between "I tried to backorder a domain" and "I caught a domain" is enormous.

The drop isn't a moment. It's a queue, and your backorder is competing against hundreds of registrar connections trying to claim the same name at the same millisecond.

If you want to stack the odds in your favor, you need to understand four moving parts: the lifecycle from expiration to release, the infrastructure that professional drop catchers actually use, the realistic math behind your win rate, and the auction mechanics that kick in the moment a catch succeeds. I'll walk through each one based on what I see across my own portfolio and what the data shows about how the major services operate.

The 75-Day Lifecycle: From Expiration to Pending Delete

Every generic TLD domain follows a predictable countdown before it becomes available again. Understanding this timeline is the first thing any serious backorder strategy depends on, because each stage offers a different opportunity—and a different set of competitors.

When a domain expires, it doesn't immediately drop. The registry gives the original owner a 30 to 45-day Renewal Grace Period to recover it at standard pricing. If that window closes without a renewal, the domain enters the Redemption Grace Period (RGP), which lasts 30 days. During RGP, the original registrant can still reclaim the domain, but only by paying a substantially higher redemption fee on top of the renewal cost. Once RGP closes, the domain moves into Pending Delete status for exactly 5 days, during which no one—not the original owner, not a registrar, not a backorder service—can touch it. At the end of those five days, the registry releases the name to the public.

For.com and.net, that release happens in a daily batch controlled by Verisign, typically between 11:00 AM and 2:00 PM Pacific Time. Anyone who has tried to manually register a fresh drop at 2:00 PM PT knows exactly how that plays out: the page hangs, refreshes, and tells you the domain was just registered. The bottleneck isn't your internet speed—it's that you're competing against automated systems that have already fired off their registration requests before your browser even loads the page. The same kind of millisecond-level race that defines execution quality in crypto derivative markets—where regulators like Brazil's central bank now impose brokerage firm standards on crypto service providers—plays out every day in the domain drop window. Speed isn't a feature; it's the entire game.

The full timeline from expiration to drop runs roughly 75 to 80 days for generic TLDs. Some of those days are useful windows (renewal grace, RGP), and some are dead zones (Pending Delete). Strategically, you want to set your backorder early enough that the catcher has time to configure its queue, but not so early that you forget about it by the time the drop actually happens.

The Pending Delete phase is the one most new investors misunderstand. They assume the domain is "available" by then. It isn't. It's frozen for five days while the registry prepares to release it. Any registrar or backorder service that claims to have caught a domain during Pending Delete is either confused or lying.

How Drop Catching Services Leverage EPP API Networks

Here's where most mental models of backordering break down. People picture a service that refreshes a registrar's "available domains" page faster than anyone else. That's not how it works at all. To catch a dropping.com or.net, you need direct access to the registry's EPP (Extensible Provisioning Protocol) API, and that access is restricted to ICANN-accredited registrars. You can't just write a faster script and connect to Verisign yourself.

The way professional drop catchers solve this is by operating networks of accredited registrar accounts. DropCatch, the largest player in the space, is reported to run connections through more than 1,200 ICANN-accredited registrars. When the registry's drop queue processes a name, DropCatch fires off simultaneous registration requests through hundreds of those registrar connections at the same millisecond. Even if 99% of those requests fail or arrive slightly too late, the sheer volume of parallel attempts dramatically increases the probability that at least one wins the queue.

The math is unforgiving for the small operator. If you have a single registrar account and you're hitting the registry's API at the moment of release, you're competing against services that have hundreds or thousands of parallel connections. Your single request might be fast, but if it arrives a few milliseconds after another catcher's request, it loses. That's not a knock on your setup—it's just the structural reality of the drop process.

The second layer of advantage is geographic and network proximity. Drop-catching services co-locate their servers in the same data centers as the registries, reducing latency to single-digit milliseconds. When the daily batch opens at 11:00 AM PT, every microsecond of network distance matters. For a retail investor running a backorder through a consumer-facing platform, you're effectively renting access to this infrastructure—your fee is paying for the catcher's EPP connections, not for any wizardry on your end.

You don't beat a drop-catching service by being clever. You beat it by backing the one with the most registrar connections, the lowest latency, and the smallest queue of competing backorders.

This is also why manual registration attempts at the drop time are essentially useless for any competitive name. By the time your browser fires a request, the catcher's automated system has already fired thousands of requests. The domain is registered before your page even loads.

The Reality of Success Rates and Competitive Bidding

Now the uncomfortable part: success rates. The industry rule of thumb is that a single backorder on a competitive domain has a win probability under 10%. That's not a typo, and it's not specific to any one service—it's the structural reality when 50, 100, or 200 other investors have also placed backorders on the same name through the same service.

The flip side is that the risk-reward profile is unusually friendly. Every major backorder service operates on a no-catch, no-pay basis. If the service fails to register the domain, you don't owe the fee. You only pay if the catch succeeds. That makes backordering one of the few asymmetric plays in domain investing: you can place 50 backorders at zero risk, and only pay for the ones you win.

The typical backorder fee at the moment of a successful catch runs $59 to $99, depending on the service and the TLD. After the catch, the domain usually goes to auction, which is where the real price discovery happens. If no one else bid, you can sometimes acquire the domain at your flat fee or a modest markup. If multiple investors are competing, the auction determines the final price.

The bid-versus-buy dynamic has shifted recently. In October 2025, SnapNames and NameJet rolled out a "Bid or Buy" / "Position" feature that lets you either commit to a maximum bid upfront or accept a fixed purchase price the service sets during the catch window. This is worth tracking because it changes how you express conviction on a name. If you're willing to pay a hard ceiling, the new position-based pricing can save you from getting dragged into a bidding war you didn't want.

Auction Dynamics: Public vs. Private Post-Catch Rules

Catching the domain is step one. Step two is what happens immediately after: the auction. The mechanics differ materially between services, and understanding the difference matters for your strategy.

When DropCatch successfully registers a domain, it routes the name to a 3-day public auction that anyone can join, even if you didn't place a backorder. The opening bid is typically the catch fee, and from there it's a standard ascending auction. The public format means more potential bidders, which sometimes pushes prices higher—but it also means more liquidity, which can help if you're trying to flip a name quickly.

SnapNames and NameJet, by contrast, run 3-day private auctions that only invite participants who placed a pre-release backorder. If you didn't backorder the domain before it dropped, you generally can't bid on it after the catch. This restricts the buyer pool but also means the competition is limited to other committed investors, which can keep prices more rational.

There's an important structural change to know about: SnapNames and NameJet have shared the same domain inventory and auction pool since their 2020 integration. A backorder placed on one platform is visible on the other, and their auction systems are now effectively merged. If you're placing backorders across both, you're not diversifying your chances—you're adding names to the same combined queue.

For most of my portfolio work, the choice between these services comes down to the type of domain I'm targeting. If I'm chasing a name that I expect will attract broad end-user interest—something generic, brandable, or keyword-heavy—DropCatch's public auction can actually work in my favor by surfacing the right bidder. If I'm chasing a more niche name where the buyer pool is small, a private auction on SnapNames or NameJet often leads to a cleaner acquisition at a fairer price.

Internal Registrar Liquidation: Why Some Domains Never Drop

Here's a frustrating truth that catches a lot of new investors off guard: many valuable expiring domains never reach the public drop at all. They get intercepted earlier in the lifecycle.

When a domain enters the Renewal Grace Period or Redemption Grace Period, the registrar that currently holds it has the option to auction the name off internally. GoDaddy and Network Solutions are the two biggest players doing this at scale. They list the domain on their own auction platform, run a 5-to-10-day bidding window, and transfer it directly to the winner as soon as the existing registration can be moved. The original owner still has the right to renew during the grace period, so the registrar is essentially hedging—running an auction in parallel and keeping the highest bid active until the very last moment.

This means that if you're using a backorder service like DropCatch or SnapNames to chase a domain registered at GoDaddy, you're often competing against GoDaddy's own internal auction, which may have already closed before the domain ever enters Pending Delete. GoDaddy's backorder service is, by industry consensus, most effective for domains registered within its own registrar network—because that's where it has the structural advantage. For names at other registrars, your chances of catching it through GoDaddy's system are notably lower.

The practical implication for your portfolio strategy is this: don't place a backorder on a name without first checking where it's registered and whether the registrar is running its own auction. If GoDaddy is already holding a 10-day auction during the grace period, your backorder through another service is essentially a fallback that will only activate if the registrar's auction fails. By that point, you're paying for a long shot.

This is also why I keep a tight watchlist of domains in the Renewal Grace Period. If I see a name I want sitting at a registrar with an active internal auction, I'd rather participate in that auction directly than wait for a drop that may never come. The 75-day timeline is a useful map, but the real action often happens in the first 30 days, not the last 5.

What This Means for Your Portfolio

If you've been treating backorders as a "set it and forget it" tool, the mechanics above should reset your expectations. The realistic picture is this: you're paying a low fee to participate in a high-speed auction against professionals who have spent years optimizing their infrastructure. That's not a reason to avoid backordering—it's a reason to be selective about which names you backorder and where you place them.

A few rules I follow in my own portfolio:

• Place backorders only on names where the end-user value clearly exceeds the typical auction premium. A backorder on a $200 domain is rarely worth the time and attention.
• Diversify across services only when the inventory is genuinely separate. SnapNames and NameJet share a pool; placing on both doesn't double your chances.

-