Expired domains: How many drop per day and the daily domain drop pool size and cadence

What the daily domain drop pool is and what it is not

The daily domain drop pool is the registry-level aggregate of domain names that complete the pendingDelete stage on a single calendar day and return to first-come-first-served public registration.

It counts only the names crossing the final release threshold. It excludes the far larger count of names entering grace, redemption, or pendingDelete the same day. Conflating those stages inflates the perceived pool by a factor of five to ten.

The drop is the end of a fixed lifecycle defined by ICANN policy. The pool a buyer can act on is the narrow exit, not the wide entrance. The volume number means nothing without the stage definition behind it.

The drop pool is the lifecycle exit, distinct from the expiration and redemption pools.

Three pool measurements sit one inside the next:

• Expiration pool. Every domain whose paid term lapses on a given day.
• Redemption pool. Every domain entering the Redemption Grace Period that day.
• Drop pool. Only the names leaving pendingDelete for the registry’s available zone.

A name expiring today does not drop today. It travels through autoRenewPeriod and redemptionPeriod first. That journey runs roughly 75 to 80 days for a .com registration.

The disambiguation between the lifecycle stages is set out in Expired vs deleted vs dropped: domain lifecycle disambiguation across 5 RFC 3915 states.

ICANN policy fixes the pipeline that feeds the daily pool.

The pipeline is not arbitrary. ICANN’s Expired Registration Recovery Policy, in force since 31 August 2013, defines the recovery window, and the redemption mechanics fix the timing of the final exit.

After a paid term lapses, the registrant retains exclusive renewal rights through the Grace period and auto-renew grace, then through the Redemption period (RGP) explained at elevated recovery pricing.

Only after redemption does the name enter pendingDelete, the no-recovery stage covered in Domain pending-delete phase: Duration and mechanics. That stage lasts a fixed five days for .com and .net before the drop.

How many expired domains drop per day across the registries

Across all top-level domains, the daily drop pool runs between roughly 130,000 and 200,000 names. Verisign-operated .com produces the largest single-TLD share, drawn from a base of 161.0 million registrations at the end of 2025.

The .net stream adds a smaller volume from the combined 173.5 million .com and .net base. The remaining volume distributes across .org, the post-2013 generic extensions, and the country-code registries.

No registry publishes a unified daily drop count. The figure is an aggregator estimate, not an audited registry statistic.

The .com stream dominates because the .com base dominates.

Per-TLD drop share tracks registration share. The .com zone held 161.0 million registrations at the end of 2025, the largest single zone by a wide margin, so it produces the largest daily drop stream.

With roughly one in four .com registrations left to lapse instead of renew, the inflow into the lifecycle is steady, and the daily exit volume stays high year-round.

The .net stream is proportionally smaller, and .org runs on a separate Public Interest Registry lifecycle that shifts its timing without changing its underlying scale.

The pool aggregates from registries that never publish a single combined figure.

The 130,000-to-200,000 range is a reconstruction, not a registry disclosure. HumbleWorth states that roughly 130,000 domains drop into the available pool each day, while aggregated industry estimates place the all-TLD average nearer 200,000.

The gap reflects scope. A .com-and-.net count lands lower. An all-TLD count including country-code registries lands higher.

Two structural caveats apply to every published figure:

• No registry audits a unified daily drop count.
• Public aggregators double-count names that span overlapping lifecycle stages.

The honest framing is a range with a stated scope, not a single precise number.

When the daily drop happens at each registry

Verisign begins the .com and .net deletion run at approximately 2:00 PM Eastern Time. The batch completes over roughly two hours, five days after a name enters pendingDelete.

Public Interest Registry processes .org deletions on a registry-controlled schedule that does not match a single published batch start time. Post-2013 generic registries and country-code registries each publish their own drop windows.

The timing is the structural opening for drop catching. An accredited registrar knows the release moment in advance and positions registration requests against it.

The Verisign window is the most predictable registry-level event in domain operations.

Verisign runs the .com and .net deletion batch at a consistent daily time, beginning around 2:00 PM Eastern Time and clearing over roughly two hours depending on the day’s volume.

The systems iterate the dropping names and change each name’s EPP status from registered to available.

The release order is not strictly alphabetical, so a service positioning for a specific name plans for the full window instead of a fixed second.

The registry-by-registry timing for the highest-traffic extensions is mapped in Domain drop schedules by TLD: .com, .net, .org and Verisign mechanics.

Other registries set their own cadence and their own terminology.

Public Interest Registry handles .org on a 30-day Redemption Grace Period plus a 5-day Restore Hold Period. That 35-day post-deletion structure does not publish a single daily batch start time to match the Verisign convention.

The country-code registries each operate under national policy, each with a distinct release rhythm:

• .uk under Nominet.
• .de under DENIC.
• .eu under EURid.

The comparative timing across the major country-code extensions is covered in Domain drop schedules for major ccTLDs: .uk, .de, .au, .eu and country-code mechanics. The registry-by-registry status mechanics are tracked through the tools in Domain lifecycle tracking: WHOIS, RDAP, and the workflow tools that monitor every status code.

Why the daily drop volume fluctuates by day, month, and year

Daily drop volume fluctuates because a day’s drops mirror the registrations made one or more years earlier. The first quarter concentrates the highest drop counts, because January and the broader Q1 window carry the highest annual registration volume, and that cohort exits the lifecycle on a one-year lag.

Bulk promotional pricing produces proportional drop echoes one to three years later, when the unrenewed promotional registrations exit together. Day-of-week variance is smaller, because Verisign processes a drop run every calendar day, weekends included.

Today’s pool is a one-year echo of a past registration peak.

The cadence is deterministic at the cohort level. A domain registered for a single year on a given date enters its exit window about 75 to 80 days after the anniversary, once autoRenewPeriod and redemptionPeriod elapse.

Daily drop volume on any date therefore reflects the registration volume of the matching prior-year cohort.

The post-2013 generic-extension launches of 2014 and 2015 generated identifiable drop echoes through 2018 as the promotional first-year registrations lapsed. The same mechanism repeats with each new bulk-promotion wave.

The annual shape is stable enough to plan against.

Because the underlying registration calendar repeats, the drop calendar repeats with it. Q1 carries the heaviest concentration, summer runs lighter, and the year-end window reflects the prior year-end registration behaviour.

An operator sizing inventory plans against this annual shape instead of reacting to a single day’s number.

The cadence does not change the central problem. A larger pool in Q1 is a larger pool of low-value names. Volume timing matters far less than the quality filter applied to whatever the pool contains.

How registries execute the drop and how fast names are recaught

A registry executes the drop as a database operation. At the scheduled time, the registry’s EPP backend iterates the pendingDelete queue and writes each name’s status from registered to available.

Drop-catch services detect the status change and submit registration requests within milliseconds. Lauinger and colleagues measured the speed and concentration of that recatch:

• 9.5 percent of deleted .com domains are re-registered within zero seconds of release.
• More than 75 percent of accredited registrars are controlled by drop-catch services.
• More than 80 percent of creation attempts come from those services, which still account for no more than 9.5 percent of successful daily creations.

The drop is a status write, and the recatch is a connection contest.

Each registry maintains a queue of names in pendingDelete. At the scheduled drop time the EPP backend iterates the queue and writes each status as available.

The contest to recatch a released name is decided by the number of accredited registrar connections a service can fire at the registry gateway at once, which is why the field is dominated by a small set of high-connection operators instead of individual buyers.

The full registry-to-public walkthrough is covered in Domain drop catching: How dropped domains become available.

The Lauinger measurement remains the rigorous public read on drop speed.

The Game of Registrars study (USENIX Security 2017) and its follow-up, From Deletion to Re-Registration in Zero Seconds (IMC 2018), analysed deletion days at the registry level. The work documented four figures that define drop speed:

• 9.5 percent of deleted .com domains are re-registered at a zero-second delay.
• Drop-catch services hold more than 75 percent of accredited registrars.
• Those services generate more than 80 percent of all creation attempts while winning no more than 9.5 percent of successful creations.
• Over half of same-day .org re-registrations land within the first 30 seconds.

These figures frame the daily race as a capital-and-infrastructure contest, not a buyer skill contest.

The premium names that route to auction instead of the public drop are covered in Domain auction routing: Why expired domains skip the drop phase.

Where the daily drop pool is published and monitored

The daily drop pool is published through aggregator services that compile registry status data into searchable lists:

• ExpiredDomains.net publishes daily droplists across 676 supported TLDs, the leading public source.
• WhoisFreaks publishes a daily expired export refreshed at 03:00 UTC.
• DomCop indexes the inventory with multi-source SEO metrics.
• HumbleWorth layers valuation scoring on top.

Registry-published pendingDelete lists reach ICANN-accredited registrars five days ahead of the drop. That advance notice makes drop catching structurally possible.

Public aggregators stratify by audience and by filter depth.

ExpiredDomains.net is the breadth source for hand-search and filter workflows, covering 676 TLDs from .com to country-code and post-2013 generic extensions.

WhoisFreaks publishes a free daily export refreshed at 03:00 UTC with a capped headline list plus a quality-filtered subset.

DomCop indexes the pool with metrics drawn from multiple SEO data providers behind subscription tiers, and HumbleWorth adds a valuation-scored gems view.

Each source reads the same underlying registry status data and differs in the filter and metric layer placed on top.

The registry-published list is the advance signal the public list lacks.

Registry-level distribution operates one layer above the public aggregators. Verisign distributes the pendingDelete list to its connected ICANN-accredited registrars five days before the drop, through the EPP gateway.

That advance window is the structural foundation of drop catching: without it, no service can pre-position registration requests for a specific release moment.

The public list updates after the fact and flags drop-date confidence with reliability indicators, because no third party verifies the exact registry release timing for every name.

The buyer scanning a public list is reading a downstream copy of intelligence the catching services received five days earlier.

Which fraction of the daily drop pool holds investment value

A small slice of the daily drop pool, on the order of 5 to 10 percent, carries meaningful aged-domain SEO or investment value, and under 1 percent commands premium pricing.

The funnel narrows at every filter. Length and character-pattern filters remove the bulk of the inventory, TLD desirability cuts further, and penalty, backlink, and topical screens reduce what remains to a fraction.

The names worth owning are also the names a catching service or a pre-release auction is likeliest to intercept before they reach the open public drop.

The funnel narrows fastest at the quality filters that matter.

From a raw daily pool of 130,000 to 200,000 names, the first cuts are mechanical: length, character pattern, and extension remove the bulk of low-liquidity inventory. The decisive cuts are the inheritance reads.

A backlink-graph read separates genuine referring-domain equity from manipulated link patterns, and a penalty and topical read separates a clean carrier from a name that drags an inherited liability.

The risk side of that read, including Google’s expired domain abuse exposure, is covered in Risks of buying an expired domain: 7 costly mistakes and how to avoid them.

The best names rarely reach the open public drop at all.

The investment-grade slice is the contested slice.

Length-based premiums and dictionary-word names route to pre-release auction services through registrar partnerships before the public drop, and the names with real backlink equity are the ones the high-connection catching services target first.

The buyer scanning the open public list is therefore reading the residue after the premium and the high-equity names were already intercepted upstream.

The starting lifecycle state that precedes the whole journey is documented in Active registration status and what it signals for SEO.

How the curated catalogue replaces the daily drop-list scan

The daily drop pool is enormous, fast-moving, and overwhelmingly low-value. The efficient acquisition path is rarely a manual scan of the raw list.

The drop is a millisecond infrastructure race won by whichever service holds the highest count of registrar connections. The names worth owning are intercepted upstream before the public list updates.

SEO Domains operates above that race. The curated catalogue isolates the 5-to-10-percent investment-grade slice, scores it on Domain Authority, Domain Rating, Trust Flow, and Citation Flow, and applies a 7-vector inheritance screen. A buyer accesses sorted, screened inventory instead of competing for a flood that is 90 percent noise.

The catalogue is the sorting layer the raw pool never provides.

A raw drop list hands a buyer the full 90-percent-noise flood and the entire audit burden, name by name, against catching services that already pre-positioned for the names worth owning. A curated catalogue inverts that burden.

SEO Domains reads the penalty status, the backlink graph, the prior topic, and the registration continuity at ingestion, surfaces the metric profile on the listing, and lists only the names that clear the screen.

The buyer reviews a confirmed profile instead of racing a millisecond contest for unvetted inventory, which is the disciplined alternative to the daily list scan.