A mismanaged domain takes down more than your website. It takes down your email, your trust signals, and your organization's public name, all in one stroke, and it can hand all three to a stranger. I once watched a Fortune 500 client spend several thousand dollars and months of negotiation buying back its own name, because the domain had been registered years earlier under a departed employee's personal address. The renewal would have cost fifteen dollars.
Episode 4 of The Web Managers Podcast is about becoming a competent holder of your organization's most important lease, and this post is its companion: the takeaways, the myth the episode takes apart, and the fifteen-minute task to finish this week. If this week's Monday check and Tuesday's Emergency File felt like a lot of domain, this is the episode that explains why the domain deserves it. Nothing else you rent online outranks the name everything else is attached to.
You hold a lease, not a deed
You do not own a domain the way you own a laptop. You register the right to use it, one year at a time, through an accredited company, and everything else in your digital presence attaches to that right. If the hosting fails, the website goes down and the domain survives to point at a new host. If the email platform disappoints, the domain lets you move. Reverse the loss and nothing survives it. The lease on the property is worth more than anything built on the land.
The three landlords
The sentence the episode exists to cure is "my web company handles all that." Three separate roles keep a domain working, and they may or may not be the same company. The registrar runs the leasing office: it records your right to the name and collects the renewal. The web host owns the building: its computers store the site's files. The DNS provider maintains the directory in the lobby: its records tell the internet where to send your visitors and your email.
Knowing which is which tells you which company to call. Website down but email arriving: the host. Email broken while the website works: DNS, because the two are separate directory entries. The browser says the domain does not exist, or a renewal notice names a company you have never paid: the registrar.
The expiration ramp
Expiration is a ramp with four stages. The grace period, where renewal costs the normal ten to twenty dollars. The redemption period, roughly thirty days, where recovery costs a fee of eighty to two hundred dollars on top. A brief pending-delete stage with no recovery. Then release to the open market, where automated services register valuable names within seconds. The layered defense that keeps you off the ramp takes under an hour: auto-renew with a verified card and a backup payment method, calendar reminders at 60, 30, and 7 days that do not depend on the registrar, multi-year runway on the primary domain, and registrar lock.
DNS as a contact card
The episode's one metaphor for the Domain Name System (DNS) is the contact card on your phone. An IP address is the numeric address of a server, like a phone number; DNS is the card that spares you from memorizing it. You tap a name, the card supplies the number. Each record type is one line on the card with one job: an A record points the name at a server, a CNAME points one name at another name, MX records say where email should be delivered, and TXT records carry verification and email authentication. That is why email can break while the website works perfectly: they are different lines on the card. Before any DNS change, take a snapshot of the existing records, so every change is reversible.
The defensive-domain decision rule
Someone will eventually suggest buying every variant of your name, and registrars will cheer them on. The rule instead: own the dot-com pairing of your primary name if it is available, or the endings your audience would naturally guess, which is one or two domains. Add a specific misspelling only with evidence of real confusion, such as bounced email. Skip the rest.
Myth busted: "Our web company owns the domain; that's normal"
It is common. It is not normal in any healthy sense. A helpful vendor builds the site and registers the domain under accounts they control, because it was faster and nobody objected. Years pass; the arrangement is invisible. Then the vendor retires or the relationship sours, and the organization discovers it does not own its own name. If your organization's name is not on the registration, the lease on your name belongs to someone else, on terms you will discover only when the relationship ends.
Quick win: confirm the registrant
Look up your primary domain, by logging into the registrar or on ICANN Lookup, and confirm three facts. The registrant is your organization, not a person and not a vendor. The registrar is a company you recognize and can actually log into. The expiration date is at least ninety days out.
Done looks like all three confirmed and noted in your inventory, or a flag raised on whichever one failed. A failure is not a crisis; it is this quarter's most important task, and the worksheet walks through fixing it.
Get the worksheet. The M3.1 Domain Health Audit Checklist covers every setting in this episode and is worth running once a year. It is free an account, along with the weekly Web Managers letter.