Registry vs Registrar: Who Actually Deletes Your Domain?
When a domain dies, two different companies hold the knife at two different moments, and almost every confused support ticket about expiry comes from mixing them up. The registrar is the retailer you bought from; the registry is the wholesale operator of the entire TLD database. Understanding which one controls which stage explains why your registrar can be generous about renewal yet powerless about redemption length, and why no amount of pleading moves a name out of pendingDelete. Here is the division of labor, stage by stage.
What is the difference between a registry and a registrar?
The registry runs the authoritative database for a TLD: Verisign operates .com and .net, Nominet operates .uk, DENIC operates .de, and every domain in those zones is ultimately a row in their systems. Registries do not sell to the public. Registrars, such as GoDaddy, Namecheap and Dynadot, are the accredited retailers that create, renew and delete registrations in the registry's database on customers' behalf, adding their own pricing, support and policies on top. You have a contract with your registrar; your registrar has one with the registry; ICANN's framework binds the gTLD layers together. Every expiry event you experience is one of these two parties acting in its own lane.
The registrar controls everything before the delete command; the registry controls everything after it
Who controls each stage?
| Stage or decision | Controlled by | The detail |
|---|---|---|
| Renewal price and grace length | Registrar | Each registrar picks its own window inside the 0-45 day framework and publishes its own timeline |
| Expiry auction | Registrar (with its auction partner) | Listing your expiring name is registrar policy; GoDaddy alone lists 35,000+ newly expiring domains daily |
| The delete command | Registrar | The registrar decides when to submit deletion; this is the handover moment |
| Redemption period length | Registry | Fixed at 30 days for gTLDs; no registrar can shorten or extend it |
| Restore fee you pay | Both | The registry charges the registrar a wholesale restore fee; the registrar adds margin, landing at $80-200 typical retail |
| pendingDelete | Registry | Exactly 5 days, unstoppable by anyone, including the registry's own support staff |
| Drop timing | Registry | Verisign releases deleting .com/.net names daily starting around 2:00 pm US Eastern |
| Status codes in WHOIS | Both | client-prefixed codes are set by the registrar, server-prefixed codes by the registry; the registry side always outranks |
Why your registrar cannot save a name in pendingDelete
Because the registrar's authority ends at the delete command. Once it tells the registry to delete, the name moves into registry-side machinery governed by contract: 30 days of redemptionPeriod in which the registrar can still submit a restore on the original registrant's behalf, then 5 days of pendingDelete in which nothing whatsoever can intervene. Support agents are not being unhelpful when they say a pendingDelete name is unrecoverable; they genuinely have no button for it. The registry will not take the call either, and services claiming special access at this stage are selling a backorder for the coming drop, not a rescue.
Why registrar policies differ but registry timelines never do
The two layers optimize for different things. Registrars compete on retail experience, so grace generosity, recovery pricing and auction behavior vary house to house; comparing them is genuinely useful, which is what the registrar grace period table is for. Registries run infrastructure under uniform contractual rules, so redemption is 30 days and pendingDelete is 5 days for every gTLD name at every registrar, always. The exception that proves the rule is ccTLDs: their registries are not bound by the gTLD contracts and write their own lifecycles, from DENIC's near-instant deletes to Nominet's roughly 90-day suspension, detailed in the ccTLD quirks guide.
Where ICANN sits above both
ICANN is the coordination layer that makes the split work. It accredits every gTLD registrar, contracts every gTLD registry, and writes the baseline rules both must follow, including the expiry protections that force registrars to publish renewal terms and offer recovery routes. That is why the deletion conveyor looks identical from every retail counter: the uniformity is contractual, not cultural. What ICANN does not do is retail intervention. It will not restore your domain, speed up a drop or overrule an auction result, and threatening to complain to ICANN changes nothing about a lapsed renewal that followed the published process. Its complaint channels exist for genuine rule violations by registrars, not for unwinding the consequences of a missed invoice.
Reading the split in a WHOIS record
The client/server prefix on EPP status codes is the role split made visible. clientTransferProhibited means your registrar locked transfers, routine and reversible in your account settings; serverHold means the registry itself pulled the name from the zone, which no registrar toggle can undo. During expiry the sequence tells the story: registrar-side statuses give way to registry-side ones as the name moves down the conveyor, autoRenewPeriod to redemptionPeriod to pendingDelete. Buyers watching a target learn to read these transitions because each one reassigns who, if anyone, can still change the outcome. For hunters, aggregation platforms do the watching at scale: DomCop (paid, from roughly $68 per month on annual billing, 2-day money-back guarantee) tracks names through these registry stages alongside quality metrics, so a shortlist stays current without manual WHOIS checks.
Three support conversations, decoded
"My registrar deleted my domain early." Almost always the registrar exercised its published, shorter-than-45-days policy; the 45-day figure is the registry ceiling, not your personal guarantee. "I contacted Verisign and they refused to help." Registries do not offer retail support and have no contract with you; every recovery runs through the registrar that sponsored the name. "My registrar says the name is unrecoverable, but a service online says it can get it back." Both are telling a version of the truth: the registrar genuinely cannot restore a pendingDelete name, and the service is quietly selling a backorder on the coming drop, with the estimated 30-50% catch odds that implies. Knowing which lane each party occupies turns all three conversations from arguments into plans.
Frequently asked questions
Can my registrar restore a domain in pendingDelete?
No. Restores are only possible during the 30-day redemptionPeriod, and only for the original registrant through their registrar. Once pendingDelete begins, the registry's 5-day countdown runs to deletion no matter who asks.
Who actually charges the $80-200 restore fee?
Both layers take a share: the registry bills the registrar a wholesale restore charge, and the registrar adds its retail margin plus the renewal. That stacking is why the same restore costs different amounts at different registrars.
Who decides that .com domains drop around 2:00 pm Eastern?
Verisign, the .com and .net registry, processes deletions in its own daily batch. Registrars have no influence on release timing; drop catchers simply learned the registry's rhythm and race it.
Do ccTLDs use the same registry-registrar split?
The roles exist, but the rulebook changes: ccTLD registries set their own lifecycles rather than following gTLD contracts. Nominet, DENIC and SIDN all run expiry differently, so the fixed 30-plus-5 registry timeline is a gTLD guarantee only.