Every Friday in October, this blog takes one chapter of Strategic Web Management: First Steps for the Accidental Web Manager and argues its central idea, paired with the podcast episode and the worksheet built from it. This week is Chapter 3, domains, and the idea at its center is one that most people only learn at the moment they are paying for it: expiration is not a cliff. It is a ramp, with stages, and every stage of it is visible in advance to anyone who knows the date.
The chapter opens on a question I ask across the desk more often than any other in this part of the work. If your domain expired quietly tonight, how many days without a website and without email could your organization absorb, and what would each of those days cost in orders, donations, or trust? For most organizations the answer runs to hundreds or thousands of dollars a day. The renewal that prevents it costs ten to twenty dollars a year.
The ramp
On the expiration date, the domain name stops resolving. The website vanishes and inbound email starts bouncing, immediately or within hours. A grace period typically follows, during which the owner can renew at the normal price; its length varies by registrar and can be as short as zero days. Then the redemption period, roughly thirty days at most registrars, where the domain can still be recovered, but only for a redemption fee that commonly runs eighty to two hundred dollars on top of the renewal. Then a brief pending-delete stage, and then release to the open market, where automated drop-catching services register valuable names within seconds and list them for resale at whatever the previous owner's desperation will bear.
Nobody has ever enjoyed learning what a redemption fee is at the moment they are paying one.
Why careful organizations end up on it
The chapter's argument is that nobody in the pattern acts carelessly. A domain is registered years ago under one person's account, with one payment card and renewal notices going to one address. Time passes; the card expires, the person changes roles or leaves, the address goes dead. Auto-renew tries the old card, fails, and sends its warnings to an inbox nobody reads. The first anyone hears of it is a customer asking why the website is gone.
Every stage of that story was visible in advance to anyone holding the inventory from Chapter 2. That is the real claim of the chapter: the expiration disaster is not a technology failure. It is a documentation failure wearing a technology costume, and documentation is the part an accidental web manager is already good at.
The layered defense
While auto-renew is essential, it fails silently the day the card or the email behind it dies. So the chapter recommends layers, and the whole set costs less than an hour. Auto-renew on for every domain, with the card verified annually and a backup payment method where the registrar supports one. Renewal reminders on the organization's own calendar at 60, 30, and 7 days before each expiration, independent of the registrar's notices, because the failure being defended against is precisely that those notices go unread. The registrar account on a role-based address the organization controls. The primary domain renewed years ahead; registrars allow up to ten, and two to five years of runway on the name everything depends on is cheap insurance. And registrar lock on, a free setting that blocks transfers until the account holder explicitly unlocks it.
Each layer catches a different failure. Together they mean the ramp stays theoretical.
The lease, not the deed
The reason the chapter spends this much care on a fifteen-dollar line item is the thing a domain actually is. You do not own it the way you own a laptop; you hold the right to use it, one year at a time, and everything else in your digital presence attaches to that right. If the hosting fails, the name survives to point at a new host. If the email provider disappoints, the name lets you move. Lose the name and nothing survives it. The lease on the property is worth more than anything built on the land, and the chapter's job is to make you a competent holder of that lease.
Hear it, read it, do it
Episode 4 of The Web Managers Podcast, Domains: Your Most Important Digital Property, walks the ramp stage by stage and builds the defense on the air. Chapter 3 gives it the full treatment, including DNS in plain English and what to do when ownership is disputed. The worksheet turns the defense into an annual audit, because settings drift and cards expire, and the annual pass catches the drift while it is still harmless.
Get the worksheet free. The M3.1 Domain Health Audit Checklist is free with an account in the Web Managers Portal. Get the book: Strategic Web Management: First Steps for the Accidental Web Manager.