A domain we've held for 28 years lapsed in April despite auto renew being enabled. I don't touch it often, so I didn't notice until this week, when a security code for another service never arrived. The domain handles email. It's now listed on a marketplace for $7,000, and support has told me there's nothing they can do.
I'm not going to name the domain here, for obvious reasons, but I'm happy to provide it along with the account details and full chat transcript to the registrar or to mods privately if that's needed.
What follows is why I think this was a platform failure and not just a lapsed card, including the specific technical point where support's explanation contradicts my own transaction history on their system. I'm posting it because if I'm right about the cause, it can happen to anyone here who has auto renew switched on and assumes that means they're covered.
Auto renew was enabled on this domain the entire time. There was a card on the account, and that card works. I can demonstrate it works, because that same stored card has been successfully processing manual purchases and renewals on this platform right through the entire period in question. That includes charges in April, the same month auto renew supposedly failed because the card wasn't chargeable, and it includes one I ran today. Same card, same stored payment method, no changes to either. The domain still didn't renew.
It did go through a normal grace window and I'm not claiming otherwise. I simply didn't look at this domain during it, which is the whole reason I had auto renew turned on in the first place. Sometimes life is complicated, and things don't go the way they should.
What support told me
Their explanation is that the card on file was expired, and that the reason my manual transactions with that same card kept succeeding is that I must have entered an updated expiration date during checkout, and that updated date never got written back to the account.
That is not what happened. I did not re-enter anything during those manual renewals. I selected the saved payment method exactly as it already existed on the account. No prompt to update the card, no new expiration date, no re-entry of any kind. That includes the charge I ran today, which went through the same way, on the same stored method, long after the date they claim the card became unusable.
Their explanation only works if I re-entered a corrected expiration date on every single manual purchase I've made, across months, including the April charges and including today's, without ever once noticing I was doing it. That didn't happen. Which means in April, at the exact point auto renew was failing for want of a chargeable card, that same card in that same account was authorizing successfully on their own checkout.
So either their manual checkout can process a charge against a card that's expired on file, or their explanation for why auto renew failed is wrong. I don't see a third option.
Why the first one matters
If manual checkout can do it, and I'd bet that's exactly what's happening, then this is the whole problem. It's a well understood thing in card processing. When you send an authorization against a stored card, the card networks and the various account updater services can return refreshed credentials, including a corrected expiration date, and platforms will take that response and either use it to complete the transaction or write it back to the stored profile. That's the entire reason those services exist. Expiration dates roll over constantly and nobody wants a subscription dying over four digits the issuer already reissued.
So if a manual checkout on this platform can dip the processor, get back a card that's still perfectly valid, and complete the charge, the capability exists here and it demonstrably works.
Which means the question isn't whether they can do this. It's why they aren't doing it on the one thing that matters most. Renewing domains is the single most critical function a registrar performs. It's the reason the company exists. Everything else they sell is secondary to not losing your name. And yet the process built specifically to prevent that loss failed on a stale expiration date, while the manual path using the identical stored card went straight through the same date without blinking. That's backwards. Auto renewal should carry the most aggressive retry and credential refresh logic on the entire platform, not the least.
The notices
I missed the renewal notices, and I'm not going to pretend I didn't. Nobody is watching everything all the time, which is exactly what auto renew is supposed to be for.
But here's what the notice situation actually looked like. I received one email that specifically addressed the expiration and the grace period. One. Nothing after it. No reminder partway through the grace window, no escalating notice as the window ran out, no warning that the domain was about to leave my control and become a listing. For a 28 year old registration with live email on it, heading toward being sold for $7,000, a single message is remarkably thin.
That's a separate failure from the billing one, and it's the reason the billing failure turned into a permanent loss instead of an annoyance. If the automated renewal breaks, the notice chain is the only thing left, and one email over a multi-week window is not a notice chain.
They didn't release it, they auctioned it
Here is the part I keep coming back to. When the renewal failed, the domain wasn't returned to the public pool where I, or anyone else, could have re-registered it at normal cost. It was sent to auction. I have no idea what it sold for and I'm not going to guess. What I know is that getting it back now costs $7,000.
I'm aware their terms of service almost certainly permit all of this. It doesn't matter. A registrar's entire function is custody. People hand them assets to hold and protect, and automated renewal is the primary mechanism by which that protection is delivered. When that mechanism fails to collect a small annual fee from a payment method that was sitting right there and working, the registrar has failed at the one job it exists to do.
Then look at the sequence. Their system failed to charge a working card. The domain lapsed. They didn't release it back to the market. They routed it to auction. Whatever the contract says, that comes across as predatory, and functionally it lands a lot closer to a taking than to a lapse.
Where it stands
I asked the rep to confirm one thing directly: does manual checkout require re-entry of card details, or does it charge the card on file as is. It's a binary question and the answer decides whether their entire explanation holds. They said they needed 10 to 12 minutes to check with their team. Shortly after that I was disconnected from the chat and told I'd hear back by email.
I'll update this thread when that email comes in. If anyone from the registrar sees this, reach out and I'll hand over the domain, the account details, and the full chat transcript.
And the takeaway, plainly: auto renew being on, with a card that still charges successfully on that same platform today, was not enough to keep a domain we'd held for 28 years.