The domain renewal that took the store down: boring failures that cost real money

A store owner once described the moment their site went down as feeling like a heart attack in slow motion. No error message on their end, no warning email they noticed, just a customer texting a photo of a browser security warning. The cause wasn't a hack or a code deploy gone wrong. It was a domain registration that had lapsed three days earlier while everyone's attention was on a product launch.

This is the category of failure that never makes it into a postmortem with a dramatic title. Domain expiry, SSL certificate lapses, hosting renewal lapses, payment processor account holds. None of it is complicated. All of it is 100% preventable. And all of it can take a profitable store offline for hours or days, because these systems fail silently until the moment they fail completely.

Why domain expiry is more dangerous than it sounds

A domain registration is a lease, not a purchase. Registrars typically send renewal notices to whatever email address was on file when the domain was registered, sometimes years earlier at a job you no longer have or an inbox nobody checks. If that notice bounces or lands in spam, the domain can lapse without anyone at the company knowing.

When a domain expires, most registrars put it into a short grace period before it becomes available for anyone to register. During that window, the domain typically stops resolving properly. DNS records tied to it, including the ones pointing to a Shopify, WooCommerce, or BigCommerce storefront, stop working. Visitors get a "this site can't be reached" error. Search engines that try to crawl the site during that window may register it as gone, which can affect indexing even after the domain is restored, a problem covered in more detail in the guide to crawl errors that hurt stores.

The fix is unglamorous: set the domain to auto-renew with a payment method that won't expire mid-cycle, and put the renewal date on a calendar independent of the registrar's own reminder emails. If a domain was registered under a former employee's account or a marketing agency's account rather than the business's own, that's worth untangling now, not during a crisis.

SSL certificates: the warning that scares customers away

An SSL certificate is what makes a browser show a padlock instead of a warning page. Certificates issued through Let's Encrypt, which powers a large share of the web's HTTPS traffic, typically last 90 days and renew automatically if the underlying automation is working. Certificates purchased separately, often through a hosting provider or a legacy setup, can run on 1-year cycles and require manual renewal.

When a certificate lapses, the browser doesn't just show a small icon change. Chrome, Safari, and Firefox all show an interstitial warning telling the visitor the connection isn't private, with a button they have to click through to proceed. Most visitors don't click through. They leave. For a store mid-checkout, that's an abandoned cart with no error logged anywhere except the customer's browser.

The usual cause on WooCommerce and BigCommerce sites is a hosting or CDN configuration where certificate auto-renewal quietly stopped working after a plugin update, a DNS change, or a provider migration, similar in spirit to the plugin conflicts covered in the WooCommerce plugin update guide. Shopify handles SSL automatically for stores on its own domains and for most custom domain setups, but a custom domain migration or a DNS provider switch can still interrupt it temporarily. Checking that the padlock is present, and that the certificate's expiration date is more than a few weeks out, takes under a minute and is worth doing on a recurring basis rather than only when something looks wrong.

Hosting renewals and the accounts nobody remembers to check

Self-hosted WooCommerce stores depend on a hosting plan that has its own renewal cycle, separate from the domain and separate from WordPress itself. A hosting account can lapse because a credit card expired, because an old admin left the company and took institutional memory with them, or because the plan was on a free trial that quietly converted to paid and then failed to bill.

BigCommerce and Shopify remove some of this risk since the platform itself is the host, but the underlying principle doesn't disappear: any third-party service a store depends on, a CDN, an app subscription, a payment gateway, a translation service, has its own billing cycle and its own failure mode if that cycle breaks. A translation app that lapses on a multilingual store can silently revert pages to a default language, a subtler but related failure to the ones covered in guides on WooCommerce migrations that break quietly.

The practical defense is keeping a short list, even a simple spreadsheet, of every paid service the store depends on: what it does, when it renews, and which card is on file. Reviewing that list quarterly takes fifteen minutes and eliminates most of the surprises.

Payment processor holds: the failure that looks like a slow day

Payment processors and merchant accounts occasionally place holds or require reverification, sometimes triggered by a sudden spike in order volume, a change in business details, or a routine compliance check. Unlike a domain or certificate lapse, this failure doesn't take the storefront offline. It takes checkout offline, or makes a subset of transactions fail, while the rest of the site looks completely normal.

This is a particularly dangerous failure because a slow sales day looks identical to a broken checkout for the first few hours. A store owner glancing at analytics sees traffic arriving normally and assumes it's just a quiet Tuesday, when in fact every third checkout attempt is failing silently. The mechanics of this kind of quiet checkout failure are explored in the piece on where stores silently bleed at checkout.

Keeping a secondary payment method active, even if rarely used, and periodically running a real test transaction rather than just checking a dashboard, closes most of this gap. Some payment providers will email about holds, but those emails deserve the same suspicion as domain renewal notices: assume the email might get missed, and verify independently.

Building a renewal calendar that actually works

None of these failures require sophisticated tooling to prevent. They require a system that doesn't depend entirely on a human remembering, because humans are busy running the actual business. A workable version looks like this: a shared calendar with every renewal date for domain, SSL (if manually managed), hosting, CDN, and any app with billing tied to store uptime, each with a reminder set 30 days and 7 days out, and a backup payment method on file everywhere that matters.

Continuous, external monitoring is the other half of the safety net, because it catches the case where a renewal reminder was missed anyway. A monitoring service that checks a store from the outside, the way a real customer would arrive, notices an expired certificate or an unreachable domain within minutes rather than whenever someone next happens to visit the site. Cassian™ runs uptime checks alongside SSL and domain health checks as part of the same continuous monitoring that watches order flow, pricing, and stock, and rolls the overall picture into the Cassian Score™ so a lapsed certificate shows up as a score drop rather than a customer complaint. It won't renew anything automatically, but it will say something the moment a renewal was missed, which is often the difference between a five-minute fix and a lost weekend.

The boring stuff is the important stuff

None of this is exciting, and that's precisely the point. Domain expiry, SSL lapses, hosting renewals, and payment account holds don't announce themselves with dramatic error messages. They just quietly stop working, and the store finds out from a customer, a support ticket, or a sudden drop in orders that looks like a mysterious sales decline rather than an expired credit card on file.

A short list of renewal dates, a backup payment method, and a monitoring layer that watches the store from the outside cover almost all of it. None of that requires new technical skills. It just requires treating renewal dates with the same seriousness as a product launch, because to a customer standing at checkout, an expired certificate and a broken site are the same thing: a store that isn't there.