for domainers · drop research

Domain drop-risk checker

See the abandonment signals a domain is showing — expiry, lifecycle status, parked nameservers, DNS, and TLS — read from the same registry data most drop checkers ignore.

What "drop-risk" actually means

When a domain isn't renewed, it doesn't vanish instantly. It moves through a fixed sequence of registry states over roughly 75–90 days before it's finally released back to the public — the "drop." Domainers watch valuable names through this sequence so they can backorder the moment one becomes available. This checker reads where a domain sits in that lifecycle, plus the softer signals of an owner who has stopped caring, and summarises them as a risk level.

Be clear about what this is and isn't. It is a transparent reading of abandonment signals — it shows you every factor it considered and why. It is not a prediction that a domain will drop, because whether it drops depends entirely on whether the owner renews, which no external tool can see until it happens. A domain can look thoroughly abandoned and still get renewed at the last minute. So treat a high score as "worth watching," never as a certainty.

The domain drop lifecycle, stage by stage

Every expiring gTLD domain follows this path. The status codes in the checker above map directly onto these stages, which is why they're such strong signals.

Day 0

Expiration

The registration reaches its expiry date. Many registrars auto-renew or give a grace period, so expiry alone doesn't mean the domain is being dropped — but it starts the clock.

~0–45 days

Auto-Renew Grace Period (autoRenewPeriod)

A window in which the registrar can still renew on the owner's behalf. The domain usually still resolves. If the owner intends to keep it, renewal happens here and the risk resets.

~30 days

Redemption Period (redemptionPeriod)

The strong signal. The owner has let the grace period lapse; the domain is deleted from the zone (stops resolving) but can still be restored for a hefty fee. A domain here has meaningfully signalled abandonment — though restoration is still possible.

~5 days

Pending Delete (pendingDelete)

The final stage. No restoration is possible; the domain is queued for release. A name in pendingDelete is, for practical purposes, dropping — this is when backorder services position to catch it.

Drop

Released to the public

The domain is deleted and becomes available for anyone to register — or is caught in milliseconds by drop-catch services with registry-level connections.

The signals this checker reads

Lifecycle status codes are the backbone — redemptionPeriod and pendingDelete are near-definitive, while autoRenewPeriod is a milder "in the grace window" flag. pendingRestore actually lowers the risk, because it means the owner is actively recovering the domain.

Expiry proximity adds weight as the date passes — a domain expired 40 days ago carries more risk than one expiring in 80 days. Parked nameservers are a telling soft signal: when a domain's NS reverts to a known parking host (Sedo, Bodis, ParkingCrew and similar), the owner has usually stopped running a real site on it. DNS resolution matters too — a domain that no longer resolves to any server, especially near expiry, looks abandoned. And TLS certificate state rounds it out: an expired or missing certificate on a domain that once served HTTPS suggests nobody is maintaining it anymore.

Crucially, the checker shows you which of these fired and how much each contributed. A sophisticated buyer doesn't want a black-box number — they want the evidence, so they can judge it themselves. That transparency is the point.

How domainers use this

The workflow is simple: identify a valuable name, check where it sits in the lifecycle, and if it's showing real abandonment signals, backorder it through a drop-catch service so you're positioned when it releases. This tool is for the research half — spotting and assessing candidates. It doesn't catch drops itself; the actual catching, at the millisecond the domain releases, is done by services with registry-level connections. Think of this as the radar, not the net.

One honest limitation worth knowing: for some country-code TLDs the registry doesn't publish an expiry date or full status codes, so the signals are thinner. The checker works best on gTLDs (.com, .net, .org, and the hundreds of newer ones) where the full lifecycle data is available.

Want the full picture? Run a complete lookup to see registration, DNS, nameservers, and these drop-risk signals together — the full context for a drop decision.