Pending delete

01

Pending delete, explained

For a typical generic extension the sequence after expiry runs like this. First comes a registrar grace period in which the owner can usually still renew. If the registrar then deletes the name, the registry holds it in a 30-day redemption period, when the owner can restore it for a fee. Next comes pendingDelete, typically for five days, and then deletion. ICANN's expired-registration policy requires registrars to interrupt an expired name's DNS before deletion, so the site and email have usually stopped working well before this stage.

At the end of pendingDelete the registry deletes the name in a daily batch; for .com and .net this is the daily drop. Drop-catch services and registrar backorder services send registration requests the moment names are released. If several people backordered a name at the service that catches it, an auction among them usually follows; a name nobody targeted may still be free to hand-register afterward.

For owners, pending delete is too late: the name typically cannot be saved, so renew before expiry or restore it during redemption. For buyers, a name in pending delete cannot be bought from the old owner or transferred, so a backorder is the only route. Many valuable names never reach this stage, because owners restore them or registrars sell them in expiry auctions, which at GoDaddy begin about 26 days after expiration. What arrives here is the leftover pool, so check any catchable name for trademarks, past use and the reason nobody wanted it.

Country-code extensions often follow their own expiry and deletion rules, so check the registry's policy before assuming the generic timeline. AI is useful for triage, ranking the long daily lists of names entering pending delete, but the catch itself is a contest of speed and registrar connections that individual investors join through backorder services.

Go deeper Expired Domains and Drop Catching: How the Domain Lifecycle Works