Scanning a daily domain drop list for expired domains: The workflow

What scanning a drop list for expired domains involves

Scanning a drop list for expired domains is the fixed, time-boxed sequence an operator runs each day to convert the 130,000 to 200,000 raw drop pool into 1 to 10 acquisition-ready aged domain candidates.

The sequence runs five jobs in order: sourcing, quantitative filtering, spam and penalty screening, manual audit, and acquisition routing. The order carries the leverage, not any single step.

The workflow repeats on a fixed cadence rather than reacting to tips.

A drop list aggregates names finishing pendingDelete and re-entering first-come-first-served availability. That is the same pool sized and timed in The daily drop pool: size and cadence.

The workflow runs against that pool on a daily schedule. It applies progressively stricter criteria across distinct tiers. Each day’s result feeds back into the next day’s thresholds.

An operator working from ad-hoc tips evaluates one name in isolation. An operator running the workflow evaluates the whole list against a consistent bar, which is what makes the output repeatable instead of lucky.

Scanning a drop list is a separate routine from monitoring an auction.

Drop list scanning targets pending-delete and freshly released names where speed of capture decides the outcome. Auction monitoring tracks open bidding windows where deliberation and budget decide it.

Both belong in an aged domain program, and each carries its own routine and its own tooling.

The workflow described here is the scanning routine: the daily reduction of a raw list to a small set of names worth a catch attempt or a watch.

How the workflow proceeds through five tiers

The workflow proceeds through five tiers ordered cheap-fast to expensive-slow. The five tiers are:

• Source the list.
• Apply quantitative threshold filters.
• Run a spam and penalty screen.
• Audit backlinks and Wayback history by hand.
• Route survivors to acquisition.

Each tier hands a smaller pool to the next. Manual hours land only on names that already cleared every automated test.

Pool reduction follows a defined shape. Tier 1 sourcing assembles and deduplicates 130,000 to 200,000 raw names. Tier 2 quantitative filtering cuts that to the low hundreds of candidates in minutes through tooling.

Tier 3 spam and penalty screening trims the survivors to a low-tens shortlist. Tier 4 manual audit qualifies 1 to 10 finalists. Tier 5 routes each finalist to a catch service, an auction bid, or a direct registration.

Reversing the order collapses throughput without improving precision. A manual Wayback read applied to an unfiltered list burns hours and surfaces nothing extra.

The cadence holds across operator types. The day runs in a fixed order:

• Sourcing happens shortly after the daily feeds publish.
• Filtering follows within minutes of the pull.
• The spam screen runs immediately after.
• The manual audit runs during working hours, before competing buyers consume the same survivors.

Mass drop events multiply the raw pool. Registry sweeps and post-holiday backlogs are the usual triggers. The response is a proactively stricter tier 2, not a longer manual read.

The mechanics of those flood days are covered in Mass drop events and what triggers them.

How operators source and deduplicate the daily list

Tier 1 ingests drop lists from ExpiredDomains.net, WhoisFreaks, SpamZilla, GoDaddy Auctions, and registry feeds, then deduplicates names that appear across multiple sources.

ExpiredDomains.net covers 676 TLDs and publishes no official API. The pull is a CSV download or a scrape. WhoisFreaks publishes a free daily list of up to 10,000 names updated at 03:00 UTC.

Source coverage shapes the entire downstream funnel. The four primary feeds each cover a different slice:

• ExpiredDomains.net aggregates daily lists across 676 TLDs through its filter UI and CSV export, not a programmatic API.
• WhoisFreaks publishes a free daily expired and dropped feed of up to 10,000 names with TLD data, refreshed at 03:00 UTC, as JSON or CSV.
• SpamZilla processes 350,000 domains daily across 16 sources and layers its own scoring at ingestion.
• GoDaddy Auctions lists 10,000 or more expiring names daily with auction context.

The export format differs by source. ExpiredDomains.net hands back a CSV export, while WhoisFreaks returns JSON or CSV that a script ingests after the 03:00 UTC refresh.

Pulling from one source alone leaves coverage gaps. Competitors fill those gaps from the sources skipped.

The ICANN ERRP sequence makes the daily cadence predictable.

ICANN’s Expired Registration Recovery Policy, effective 31 August 2013, standardizes the post-expiration sequence of renewal grace period, redemption period, and pending delete that produces a predictable daily release rhythm across gTLD registries.

Operators time their pulls against that published sequence to capture pending-delete and dropped inventory at maximum freshness, since the highest-value names resolve within hours of release.

Verification of any individual name’s current status runs through WHOIS and its RDAP successor, the lookup tooling catalogued in Domain lifecycle tracking: WHOIS, RDAP, and the workflow tools that monitor every status code.

Deduplication compresses the working set before any filtering begins.

A single dropped .com surfaces on ExpiredDomains.net, GoDaddy Auctions, and SpamZilla at the same time, and running three duplicate records through tier 2 and tier 3 triples the cost for no gain.

Hash-based deduplication against the registered domain string collapses the multi-source pull into one clean working set.

On mass drop days the duplication overhead climbs sharply, which is the point at which an automated dedup step stops being optional and starts paying for itself.

How quantitative threshold filters cut the pool fast

Tier 2 applies quantitative thresholds to cut a six-figure list to the low hundreds of candidates in minutes. The thresholds cover referring-domain count, Domain Rating or Domain Authority, Spam Score, name length, and TLD selection. These filters run across the full list at near-zero per-name cost through tooling, which is why they run first.

A practical starting threshold set combines five dimensions:

• Referring domains: a floor of 20 or more unique sources eliminates lone-link names.
• Authority floor: Domain Rating above 15 to 25 from Ahrefs, or Domain Authority above 20 from Moz.
• Spam Score cap: flags obvious manipulation.
• Name length: a ceiling near 18 characters favours brandable assets.
• TLD selection: .com, .net, .org, and operator-relevant ccTLDs over novelty extensions.

The Ahrefs Domain Rating and the Moz Domain Authority set the authority floor at this stage. The mechanics of the Majestic trust metrics that tier 3 leans on are detailed in Trust Flow and Citation Flow.

Threshold strictness trades pipeline volume against shortlist quality.

Loose thresholds surface 800 to 1,200 candidates a day and demand longer audit hours downstream. Strict thresholds surface 80 to 150 candidates and constrain monthly acquisition volume.

The right calibration tracks the operator’s own historical conversion rate. That rate is the share of tier-2 survivors that became worthwhile acquisitions. A weekly review of the decision log against win and loss data refines it.

ExpiredDomains.net processes its filter set in seconds. SpamZilla and similar aggregators apply scoring at ingestion. Custom scripts in Python or Node run tier-2 logic against a CSV pull in under a minute. The cheap-fast designation is literal.

Tier-2 filters exclude, they do not endorse.

A name clearing all five thresholds earns a tier-3 screen, not acquisition status.

The quantitative pass removes the structural majority of a list. Those are the empty and machine-generated names that never accumulated equity. The low hundreds of plausible candidates pass to the screen that catches what raw numbers miss.

On mass drop days, an unchanged threshold set against a multiplied pool floods the manual stages with a multiplied survivor count. Operators tighten tier 2 proactively when a scheduled flood approaches.

How the spam and penalty screen removes contaminated names

Tier 3 screens the low-hundreds pool of quantitative survivors for spam residue and penalty exposure using a SpamZilla score, the Majestic Trust-to-Citation ratio, and an anchor-text scan. The screen reads three signals together because the dangerous tier of a drop list inflates any single headline number in isolation.

The Trust-to-Citation ratio is the fastest spam tripwire. Trust Flow weights links by proximity to a curated trusted-seed set; Citation Flow weights raw link influence.

A Trust Flow of 10 against a Citation Flow of 50 records link volume unsupported by trust, the classic spammed-profile fingerprint, and triggers rejection before any manual time goes in.

A ratio at or above 0.50 reads as a practical minimum and 0.70 or higher as stronger.

SpamZilla’s proprietary 1-to-100 score compounds this read across seven inputs:

• Domain age
• Archive.org active history
• Redirect status
• Parked-page intervals
• Anchor text
• Website history
• Backlink history

That spread is why the score functions as a screening layer instead of a single metric. The Moz screen it complements is covered in Domain Spam Score.

Anchor-text scanning audits the language attached to inbound links across the survivor set. A natural profile skews toward branded, naked-URL, and generic anchors.

Pharma, casino, adult, forex, and replica anchors are auto-disqualifiers regardless of surface metrics, because their presence records a prior abuse cycle that travels with the name.

Foreign-language anchor anomalies that mismatch a domain’s history signal link injection or hijack residue.

The signals that separate genuine value from engineered noise at this stage are catalogued in Spotting value in drop lists: signal vs noise, the companion piece on what to look for once the workflow tells where to look.

How manual backlink and Wayback review confirms value

Tier 4 reserves the expensive manual hours for the low-tens shortlist and reduces it to 1 to 10 finalists at minutes to half an hour per name. The hand audit runs four checks:

• A hand audit of the backlink profile in Ahrefs or Majestic.
• A Wayback Machine continuity read.
• A trademark check.
• A redeployment-fit verification against current abuse policy.

Backlink review moves beyond the referring-domain count that cleared tier 2. The auditor opens the strongest referring pages and confirms two things.

The links are contextual in-content placements, not sitewide footers or sidebars. Each link is still indexable, with no noindex tag or robots block.

A healthy referring-domain trend grows gradually across years. A sharp spike followed by a collapse signals a paid campaign or an injection.

Domain age on its own carries no weight here. The SEO Domains analytical desk treats that as settled: a technically old name with a manipulated link history loses to a younger name with a clean editorial profile. The audit reads continuity and source quality, not the registration year.

Wayback continuity converts a domain’s past into a pass-or-fail filter.

The Wayback Machine, operated by the Internet Archive, preserves snapshot copies of a domain’s content across its registration years.

The auditor opens one representative snapshot per year, ideally seeking ten or more years of coherent history, and flags any topical pivot, spam interval, parked-page stretch, or hacked-content episode.

A name that ran accountancy content and held that identity passes; a name that pivoted into casino content during its final two years carries inherited residue that survives the transfer.

A real organic-traffic record and a site: indexation check close the read, since a name with metric strength but zero indexed pages is a profile without a pulse.

Redeployment fit is a mandatory checkpoint, not an optimisation.

Google’s expired domain abuse policy, launched 5 March 2024, designates as spam any domain repurposed primarily to manipulate ranking off its prior reputation, and site reputation abuse enforcement followed on 5 May 2024.

Tier 4 verifies that the planned deployment continues the prior topical context: an accountancy domain rebuilt as accountancy content respects the policy, the same name redirected to fitness violates it.

A trademark check against USPTO TESS, EUIPO TMview, and the WIPO Global Brand Database closes the audit. A name matching an active mark exposes the buyer to a UDRP filing and forfeiture, one of the Risks of buying an expired domain: 7 costly mistakes and how to avoid them.

When redeployment fit fails, the name exits the funnel regardless of metrics. That is the condition under which a strong-looking name underperforms a fresh registration, set out in When an aged domain is worse than a new one.

How the shortlist routes to a catch or auction

Tier 5 routes each qualified finalist to its acquisition channel. Three channels match the name’s lifecycle position:

• Drop-catch attempt for a pending-delete name.
• Auction bid for a name already on a marketplace.
• Direct registration for a name that fell clean.

The route is decided before the window opens, with a written bid ceiling. The highest-value catches resolve in seconds.

Channel selection follows the name’s lifecycle position. A name approaching pendingDelete routes to a drop-catch service. DropCatch runs Dropped, Pre-Release, and Private Seller auctions typically in the $20 to $500-plus range.

A name already listed routes to its auction. GoDaddy Auctions lists 10,000 or more expiring names daily. It opens an expired auction on day 26 that runs 10 days, then a Final Closeout on day 37 for 5 days as a reverse auction where the price falls daily.

GoDaddy phased out new backorder purchases on 8 August 2024, directing buyers to its auctions or broker services. That shift moves more pending-delete capture onto dedicated catch infrastructure. A name that drops clean without competition registers at standard cost.

The decision log turns each run into a feedback loop.

A standard log captures seven fields per name:

• Domain name
• Source list
• Audit note
• Bid ceiling
• Acquisition channel
• Win or loss outcome
• A 30, 60, and 90-day post-acquisition performance read

A weekly review reads the log against the tier-2 thresholds. It tightens the cutoffs against win rate and average acquisition value. This discipline distinguishes a professional pipeline from random catches drawn from the same daily pool.

Pipeline economics frame the stakes. Operator labour at typical rates runs against a 30 to 60-minute daily routine. Catch-service fees apply per attempt with partial success rates, and auction prices climb with metrics. All of it is measured against acquired-domain resale or deployment return.

The names worth this whole sequence are documented across niches in Aged domain case studies by niche.

How the curated catalogue runs the workflow once

The expired domain workflow rewards order: cheap-fast filters first, expensive manual audit last, run the same way every day.

Done by hand on a 130,000 to 200,000 name list, it costs hours daily and still loses catches to faster infrastructure.

SEO Domains has already run this exact workflow at scale across a 220,000+ catalogue. The team scores Domain Authority, Domain Rating, Trust Flow, and Citation Flow, and runs a 7-vector inheritance screen. A buyer reviews the already-sorted slice instead of grinding the daily list one name at a time.

The catalogue runs the funnel once so the buyer does not repeat it daily.

A raw drop list hands a buyer the full five-tier burden every morning. The contaminated tier is engineered to defeat a one-metric glance, and the catch window is measured in seconds. The curated catalogue inverts that burden.

SEO Domains sources, deduplicates, filters, spam-screens, and manually audits at ingestion. Each listing surfaces Domain Authority, Domain Rating, Trust Flow, and Citation Flow. Only the names that clear the 7-vector inheritance screen reach the catalogue.

The buyer reviews a confirmed profile, the same convergence a disciplined daily workflow would produce, without running the workflow at all.