Why domains don't expire at random times
Domain deletion isn't instant the moment a registration lapses. Registries batch-process expired-domain deletions during maintenance windows rather than deleting continuously — the exact window and cadence varies by registry and can change without much notice, so treat any specific time below as a starting point to verify, not a guarantee.
The result: a batch of domains from the same registry tends to hit the public market close together, creating a short, high-contention window rather than a steady drip.
Roughly, by registry
.COM & .NET (Verisign): Verisign runs the largest deletion batches — this is the highest-volume, highest-competition window of any TLD, concentrated in the early-to-mid afternoon US Eastern time on most days.
.ORG (Public Interest Registry): Runs on its own schedule, generally with less competition than .COM simply due to lower volume and fewer specialized catchers watching it closely.
.INFO & .BIZ (Identity Digital, formerly Afilias): Smaller volume, earlier-morning US Eastern windows historically — mostly caught by catchers already working other time zones.
.US (GoDaddy Registry, formerly Neustar): GoDaddy Registry has operated .US since acquiring Neustar's registry business in 2020. Its own deletion schedule and volume differ from Verisign's .COM/.NET.
Country-code TLDs (.IO, .AI, .CO, etc.): Each is run by its own national or delegated authority, not a shared US-based registry infrastructure — schedules, grace periods, and even whether a domain re-enters the open market at all vary per ccTLD. Always check the specific registry's own policy before assuming a .COM-style drop process applies.
The connection-limit problem
Knowing roughly when a batch drops is only half the problem. Registries rate-limit how many requests a single registrar connection can make. Fire too early and you risk being throttled before the window opens; fire too late and the domain is already gone — competitive drop-catching for high-value names is decided in a very small margin of time, not by "checking a bit before the estimated window."
Retail registrars like GoDaddy or Namecheap have connection limits built for normal customer use, not industrial-scale catching. Dedicated drop-catching services work around this by running many registrar accounts in parallel to multiply their effective connection limit — which is most of why they win contested .COM catches that a single retail account never could.
Strategic implications by investor type
- Full-time professional: Track every registry's window, use dedicated catching infrastructure, and expect to compete on volume, not precise timing alone.
- Part-time investor: Focus on lower-competition registries (.ORG and smaller ccTLDs) where retail-level tooling still has a realistic shot.
- Beginner: Start with a retail drop-catching service on a lower-competition TLD. Expect a modest catch rate on any single contested name — this is a volume game, not a one-shot bet.
Key takeaways
- Deletion timing is registry-specific and batch-based, not continuous — verify the current window for whichever registry you're targeting rather than relying on a fixed schedule.
- .COM/.NET (Verisign) is the highest-volume, highest-competition window of any TLD.
- Connection rate limits, not knowledge of the schedule, are the real bottleneck for contested names.
- ccTLDs run on their own national infrastructure — don't assume .COM-style mechanics apply.