BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Registrar-Specific Drop Catching: How a Dropped Domain Is Won at the Registrar Level, Registry by Registry, in 2026
Registrar-specific drop catching is the part of the story the general guides skip. A dropped domain is not awarded to whoever clicks fastest in a browser. It is awarded to an ICANN-accredited registrar that sends a valid registration request to the registry in the instant the name releases, and the catch is decided entirely at that registrar layer, registry by registry.
That single fact reshapes the whole game. The reason a service like DropCatch wins names a lone bidder never touches is that it operates a reported 1,201 separate registrar accreditations, each a fresh channel of requests at the drop. The catch is won on accredited-registrar access, request quotas, and infrastructure scale, not on luck or a stopwatch.
This guide maps that registrar layer honestly. It explains how a registrar wins a release, why catchers run hundreds of registrar accounts, what the published research shows about which registrars dominate, and how the mechanics shift from .com to a ccTLD. The honest read runs through every section: the registrar race is a structural game that ordinary buyers are not built to win, which is why SEO Domains operates the curated marketplace where a screened aged domain is bought outright instead of raced for at the registry.
What “registrar-specific” drop catching means
Registrar-specific drop catching is the recognition that a dropped domain is captured by an ICANN-accredited registrar at the registry, not by an end user in a browser. The registry awards a released name to the first registrar whose valid registration request arrives, so the catch is decided at the registrar layer. Which registrar is racing, the count of accredited accounts it runs, and how directly it connects to the registry are the variables that decide who wins the name.
The general drop-catching guides describe the lifecycle and the backorder fee, then stop. They leave out the layer where the catch is genuinely won. A domain releases from the registry, and in that instant accredited registrars fire registration requests at it. The registry takes the earliest valid one. Everything a buyer experiences, the backorder, the auction, the win or loss, is downstream of that registrar-level race.
The registrar is the only party that can register the name
A registry, such as Verisign for .com and .net, does not sell domains to the public. It accepts registrations only from accredited registrars over the Extensible Provisioning Protocol, the machine language registrars use to talk to the registry. When a name drops, the registry is waiting for a registrar to claim it. No member of the public, no matter how fast their connection, has a seat at that table.
Why “registrar-specific” is the right lens
Framing drop catching as a registrar question changes the buyer’s whole calculation. The choice is not really which service has the nicest website. It is which registrar infrastructure stands behind that service, the number of accredited accounts it commands, and how cleanly it connects to the registry handling the name. A drop on a .com release favours different infrastructure than a drop inside a ccTLD with its own rules, a difference covered later in this guide. The lifecycle that produces the drop in the first place is set out in the expired domain fundamentals hub.
How a registrar wins the drop: EPP access, the registry race, and timing
A registrar wins the drop by holding direct EPP access to the registry and submitting a valid create request the instant the name deletes. Accredited registrars connect straight to the registry server, so their request arrives ahead of anyone routing through a third-party API, a latency edge reported in the range of 1 to 100 milliseconds. The registry awards the name to the earliest valid request, which makes raw connection speed and request volume the deciding factors in a contested catch.
The mechanics are physical, not magical. Three things separate the registrar that catches a name from the registrars that miss it: direct registry access, the timing of the request, and the number of requests in flight.
The name sits in pending delete. Accredited registrars and their catch systems are connected to the registry over EPP, primed to send a create request the moment the name frees. Source: ICANN registry lifecycle and registrar EPP operations.
The registry purges the name and it becomes registrable. Every primed registrar fires create requests at once. Because accredited registrars hold direct EPP access, their packets reach the registry server before any request routed through an intermediary API. Source: NamePros technical discussion of DropCatch architecture.
The registry accepts the earliest valid create request and registers the name to that registrar. A reported network delay of 1 to 100 milliseconds between a direct registrar and an indirect path is enough to decide the outcome. Source: NamePros, on the latency edge of accredited access.
If the catching registrar’s service had one backorder, that customer gets the name at the flat fee. If two or more customers backordered it, the service runs an auction between them. The registrar-level catch happened first; the customer-facing step follows. Source: DomCop and platform documentation.
Direct EPP access is the structural edge
The Extensible Provisioning Protocol is the registrar-to-registry channel. An accredited registrar opens an authenticated EPP session with the registry and submits create commands directly. As one technical discussion of the DropCatch model puts it, no party that is not an accredited registrar has direct access to that EPP communication, so an ordinary user has to send a request to a registrar’s API and wait for the registrar to relay it. That relay is the lost step. The user’s request is always at least one network hop behind a registrar racing the same name.
Why drop catchers run hundreds of registrar accounts
Drop catchers run hundreds of separate registrar accreditations to multiply their attempts at the release instant. A registry caps the rate of requests one registrar can send per second, so a single accreditation hits a queue. By holding hundreds of accreditations, a catcher fires from all of them at once and routes around any one registrar’s quota. TurnCommerce, which operates DropCatch, runs a reported 1,201 registrar accreditations beyond its main one. Replicating that scale is estimated to cost millions in ICANN fees alone, which is the moat that keeps the field small.
This is the economic heart of registrar-specific drop catching, and the part the general guides never quantify. The advantage is not a faster computer. It is a fleet of accredited registrars, each adding more shots at the name in the same fraction of a second.
The per-registrar request quota
A registry limits the rate at which any single registrar can submit requests, a per-registrar requests-per-second quota. Hit the cap, and that registrar’s further requests wait in a queue while the name is awarded to someone else. The published technical reasoning is direct: a catcher works around the bottleneck by using another one of its registrars when one nears its quota. Stack enough accredited registrars, and the effective number of valid requests at the drop scales with the count of accounts, not with the speed of one machine. WHOIS records on caught names reflect this, showing registrars labelled in numbered series such as DropCatch 1091 LLC.
One registrar account
A single quota of requests per second. Hit the cap and the rest queue. Against a fleet of accredited registrars firing in parallel, a single account lands few valid requests in the release instant.
Hundreds of registrar accounts
Each account carries its own quota. Firing from all of them at once multiplies valid requests at the drop and routes around any single account’s queue. This is the catcher’s real advantage.
The cost barrier
ICANN charges a flat fee reported near 4,000 US dollars per registrar each year, plus a share of a variable pie reported around 3.8 million US dollars. DropCatch is reported to carry roughly 45 percent of those variable fees.
Why the field stays small
Building a competitor at 1,252 registrars is estimated near 9.39 million US dollars in ICANN fees alone. The barrier keeps registry-level catching to a handful of operators, which is the structural reality buyers face.
The fees are a real, moving cost
The economics are not static. Domain Name Wire reported in 2025 that DropCatch pays roughly 8 US dollars of ICANN overhead per domain when its registrars catch 58 domains a month, and that figure climbs toward 18 US dollars when they catch only 25, raising the open question of whether the operator would shed accreditations if catch volume falls. The takeaway for a buyer is that the registrar race carries heavy fixed costs that only the largest operators can spread across enough catches to justify, and those costs ultimately sit inside the prices and fees the buyer pays.
What the research shows: which registrars dominate the drop
Published academic measurement confirms that drop-catch registrars, not ordinary ones, own the instant of the drop. In a large-scale study of the deletion process, 9.5 percent of deleted domains were re-registered at a zero-second delay, with drop-catch services such as DropCatch, SnapNames, and Pheenix dominating that first second. Other registrars peak hours later, and one registrar, Xinnet, was found to hold over 50 percent share in the 1-to-9-hour window after deletion. The behaviour at the drop is measurably distinct, and it belongs to a small set of registrars.
This is the evidence the brand roundups assert without sourcing. Two academic studies from the Northeastern University security group put numbers to the registrar race, and they are worth citing precisely because they replace forum opinion with measurement.
The zero-second finding
The 2018 study “Domain Registrar Behaviour During the Drop,” by Lauinger and colleagues at the Internet Measurement Conference, tracked deleted domains and their re-registration timing. Its headline measurement is that a meaningful slice of deletions, 9.5 percent, are re-registered with effectively no delay, the signature of an automated catch system and not a human. The companion 2017 study, “Game of Registrars” at USENIX Security, examined post-expiration takeovers across the registrar field. Together they establish that the catch is an automated, registrar-driven event, and that the registrars capable of a zero-second re-registration are a recognisable few.
Different registrars win at different moments
The research also shows that the registrar field splits by timing. Dedicated catchers own the first second. A registrar like GoDaddy, and a high-volume registrar like Xinnet, peak hours later when the contested catches are already settled. A registrar such as Dynadot shows both behaviours. For a buyer, the lesson is that the registrar handling a name shapes when and how it can be caught, and the sharpest catch behaviour is concentrated in the services built for the registry race. The broader question of which releases are reachable at all is examined in the drop-catching pillar.
Registry by registry: how the catch differs across .com, ccTLDs, and registrar auctions
The registrar race is not uniform across registries. For Verisign-run gTLDs like .com and .net, the name passes through a redemption grace period of roughly 30 days, then a 5-day pending-delete window, then a hard drop the registry purges, which is the classic registry race. Country-code registries set their own rules: Nominet, for example, publishes daily drop lists for .UK and exposes drop timing through EPP, and direct registry accreditation can grant early visibility. A third path never reaches the registry at all, because the registrar auctions the non-renewed name first.
Understanding which of these three paths a name is on tells a buyer whether a registry-level catch is even the right target, or whether the name is decided inside a registrar long before it would ever drop.
| Registry path | How the name releases | Where the catch is decided |
|---|---|---|
| Verisign gTLD (.com, .net) | Redemption grace near 30 days, then a 5-day pending delete, then a hard registry drop | The registry race: accredited registrars firing create requests at the purge instant |
| Other gTLDs (.org and newer extensions) | Similar ICANN lifecycle, with operator-specific timing and occasional expired-name auctions | Mostly the registry race, sometimes a registry or registrar pre-release auction |
| ccTLD with drop lists (Nominet .UK) | Registry publishes daily drop lists and exposes timing through the EPP check response | Registry race, but timing is published and direct accreditation can give early access |
| Registrar pre-release auction | The registrar auctions the non-renewed name before returning it to the registry | Inside the registrar, before pending delete; the name may never reach a public drop |
The gTLD registry race
For a .com or .net name, the lifecycle is well defined. After expiration and any renewal grace, the redemption grace period runs roughly 30 days, then a 5-day pending-delete window, after which the registry purges the name and it becomes registrable. That purge is the drop, and it is the moment the registrar race fires. Because Verisign runs the largest registries on a predictable schedule, this is where the dedicated catchers and their fleets of accreditations concentrate.
ccTLDs set their own rules
Country-code registries are not bound by the ICANN gTLD lifecycle and write their own deletion policy. Nominet, the .UK registry, publishes drop lists daily and surfaces drop timing in the EPP check response, so the timing is less of a secret than on a raw gTLD drop. A number of country registries shorten or skip the pending-delete stage entirely, and direct accreditation with a particular registry can grant visibility days ahead of the public release. The registrar handling a ccTLD name, and that registry’s own rules, change the shape of the catch.
Registrar pre-release auctions short-circuit the drop
The third path is the one buyers overlook the hardest. A large share of registrars place a non-renewed name into their own auction before it would ever reach pending delete, capturing the demand value while the name is still inside the registrar. On that path there is no registry race to win, because the name is resolved internally and never drops to the open registry. The mechanics of the registrar backorder and auction route are compared in Registrar backorder services compared.
Step by step: how a registrar-specific catch is genuinely won
Winning a registry-level catch is a six-stage sequence that happens almost entirely at the registrar layer: hold accredited-registrar access, identify the exact drop time, pre-connect EPP sessions, fire create requests from hundreds of accounts at the release instant, win the registry award, then resolve the customer-facing backorder or auction. Each stage has a failure mode, and the first five are unreachable for anyone who is not an accredited registrar with infrastructure at scale. Reading the sequence is how a buyer sees why the race is structurally lopsided.
The stages below describe what happens when a name is caught. They are written so a buyer can see, plainly, where they sit in this picture and why a single-account, single-machine attempt is a different contest from the one the catchers are running.
-
Hold accredited-registrar access to the registry
The catch begins with an ICANN-accredited registrar that holds a direct EPP connection to the registry running the name. This is the entry ticket to the floor, and it cannot be borrowed in the moment.
The trap: assuming a fast home connection substitutes for accreditation. Without direct EPP access, a request routes through a registrar’s API and is a hop behind from the start.
-
Identify the exact release time
For a gTLD, the drop follows the 5-day pending-delete window on a predictable registry schedule. For a ccTLD like .UK, drop lists and the EPP check response publish the timing. Knowing the instant is half the race.
The trap: guessing the drop time or relying on a stale list. A request that arrives a second early or late is a request the registry rejects or that loses to a primed competitor.
-
Pre-connect and prime EPP sessions
Before the release, the catch system opens authenticated EPP sessions across its registrar accounts and stages the create request, ready to send with no setup latency the moment the name frees.
The trap: opening a connection only after the drop. The handshake delay alone hands the name to a system that was already connected and waiting.
-
Fire create requests from hundreds of accounts at the instant
At the release, the system fires create requests in parallel from every accredited account, multiplying valid attempts and routing around any single registrar’s per-second quota. Account count, not machine speed, drives the odds here.
The trap: firing from one account against a fleet. A single quota lands a handful of attempts while a competitor lands hundreds in the same fraction of a second.
-
Win the registry award
The registry accepts the earliest valid create request and registers the name to that registrar. The catch is now settled at the registrar layer, and the name sits in the catching registrar’s account.
The trap: treating this as the finish line for a contested name. If two or more customers wanted it, the registry win only triggers the auction that decides the real price.
-
Resolve the customer-facing backorder or auction
If one customer backordered the caught name, they receive it at the flat fee. If two or more did, the catching service runs an auction between them. Compare that expected cost against buying a comparable screened name on the SEO Domains marketplace before committing to the race at all.
The trap: budgeting only the backorder fee. On any name worth catching, the auction premium is where the real money is spent, on a name the registrar still had to win first.
Common mistakes when you approach the registrar race: the checklist
The mistakes buyers make about registrar-specific drop catching all stem from one misread: treating the catch as a speed contest they can enter instead of a registrar-infrastructure contest decided above their layer. Each row below is a misconception, why it costs, and the correction. The fixes converge on one discipline: understand that the registry race rewards accreditation and scale, then decide whether to enter it at all or buy a screened name outright. Use this as the scannable reference.
The table consolidates the failure modes from the sections above. The left column is the mistake, the centre column is why it costs, and the right column is the correction.
| The mistake | Why it costs | The fix |
|---|---|---|
| Thinking a fast browser can win the drop | Only accredited registrars speak EPP directly to the registry; a browser is always a hop behind | Treat the catch as a registrar contest, and place a backorder with a service that holds the infrastructure |
| Believing one registrar account is enough | A single per-second quota lands few requests against a fleet firing in parallel | Recognise that account count, not connection speed, drives contested catches |
| Ignoring which registry runs the name | A .com drop, a Nominet .UK drop, and a registrar auction are three different contests | Confirm the registry path before choosing a catch route or backorder |
| Missing the registrar pre-release auction | The name may be resolved inside a registrar and never reach a public drop | Check whether the name is in a registrar auction before waiting for a registry race |
| Mistaking the registry win for the final cost | A contested caught name is priced by auction, not the advertised backorder fee | Budget for the auction, set a ceiling, and treat the fee as entry only |
| Skipping the spam and history check | A caught name with a toxic profile is a liability whichever registrar wins it | Screen the backlink profile and history before paying to catch |
| Racing on principle against a 1,201-account fleet | The infrastructure gap makes a contested registry win close to unattainable for an individual | Compare the expected cost of winning against buying a comparable screened name outright |
Frequently asked questions
The five questions buyers and SEOs raise about registrar-specific drop catching, answered against registry mechanics, published research, and industry reporting.
Q1Does it matter which registrar catches a dropped domain?
It decides the catch. The registry awards a released name to the first accredited registrar with a valid request, so the registrar racing the drop, its direct EPP access, and the number of accredited accounts it runs are what determine who wins. Which registrar catches the name also sets its initial home and the path to the backorder or auction. The general guides treat the registrar as a detail; at the registry layer it is the whole contest.
Q2Can an individual drop catch a domain without being a registrar?
Not directly at the registry. Only an ICANN-accredited registrar can submit registrations over EPP, so an individual has to route a request through a registrar’s API, which is at least one network hop behind a registrar racing the same name. For a contested name against a service running hundreds of accredited accounts, a manual attempt has effectively no chance. The realistic route for a non-registrar is a backorder with a catching service, or buying a screened name outright.
Q3Why does DropCatch run hundreds of registrar accounts?
To multiply its attempts at the drop. A registry caps the rate of requests one registrar can send per second, so a single accreditation hits a queue. TurnCommerce, which operates DropCatch, runs a reported 1,201 registrar accreditations beyond its main one, firing from all of them at once to route around any single quota. Domain Name Wire reports that ICANN charges roughly 4,000 US dollars per registrar each year, which makes the fleet a multi-million-dollar infrastructure and the field’s main barrier to entry.
Q4Is drop catching the same on a ccTLD like .UK as on .com?
No. A .com name follows the Verisign gTLD lifecycle, with a redemption grace near 30 days, a 5-day pending delete, and a hard registry drop. Country-code registries write their own rules: Nominet publishes daily drop lists for .UK and exposes drop timing through the EPP check response, and direct registry accreditation can give early visibility. A number of country registries shorten or skip pending delete entirely. The registry handling the name reshapes how and when a catch is possible.
Q5How fast does a dropped domain get caught?
For names with demand, effectively instantly. An academic study at the 2018 Internet Measurement Conference found that 9.5 percent of deleted domains were re-registered at a zero-second delay, with drop-catch services owning that first second. The names with no demand drop uncaught, while the contested ones are gone before a human reaction is possible. That speed is the signature of an automated, registrar-run catch system, not a person watching for the release.
The registrar race versus owning the name: where a screened domain wins
Registrar-specific drop catching is a registry-level contest decided by accredited-registrar access, request quotas, and a fleet of registrar accounts that costs millions to assemble. An ordinary buyer cannot enter that race on equal terms, and even a backorder is a bet on a name a registrar still has to win first. The names worth owning, aged and expired domains with clean profiles, are a screened catalogue, not a registry race. Sourcing from a curated marketplace replaces the EPP race, the fee, and the auction with a priced, vetted purchase. SEO Domains operates that marketplace.
Why the race is structurally the wrong default
Read the registrar mechanics and the research together and the conclusion is structural, not a matter of effort. The catch is decided above the buyer’s layer, on infrastructure measured in the millions of dollars, and the highest-value names are re-registered in zero seconds by a handful of registrars built for it. An individual racing a drop with one account is not in that contest. The investor goal, a quality aged domain, is reachable without entering the registry race at all, by buying a screened name directly.
What a screened catalogue removes
A curated marketplace collapses the registrar race into a listing. The name is already caught, owned, and transferable, the backlink profile is read, the history is checked, and the spam screen is run before the name is priced. A buyer reviews the profile shown on the listing and decides at leisure, with no EPP access to win, no backorder fee at risk, and no auction to be drawn into. The decision between racing a registry drop and buying outright sits at the centre of the comparison below.
| Dimension | Racing the registrar drop | Sourcing screened inventory |
|---|---|---|
| Who can compete | Accredited registrars with fleets of accounts | Any buyer who reviews a listing |
| Who wins the name | The earliest valid registrar request at the registry | The buyer who decides to purchase |
| Cost certainty | Backorder fee plus an open-ended auction | A listed price, fixed before purchase |
| Quality check | Done by you, after the catch | Done before listing, by the marketplace |
| Outcome | A registry race you cannot directly enter | A clean aged domain acquired by purchase |
Browse curated aged and expired domains with clean profiles
The goal behind every search for registrar drop catching is access to a quality aged domain. That is the product: a screened name, not an accreditation, not a catching subscription, and not a faster connection. SEO Domains operates the curated marketplace where aged and expired domains are screened across their backlink profiles and history before they are listed and priced, so the name worth owning is reached by purchase, not by a race against a thousand registrar accounts you cannot match.
