A locked domain name, a provider that doesn't answer and months of follow-ups. The story of a team that refuses to give up on its client.
Some calls you never forget. One morning, a client reaches out: their website is down. Then they add the detail that changes everything. No emails are coming in, none are going out. Their customers are writing into the void, and their team can no longer access their inboxes.
The cause: their domain name, the one they've been using for over 20 years, is locked with a provider, tied to an old account that no longer exists. The problem is simple to understand. Fixing it is another story. And above all, the solution isn't in our hands, it's in the provider's.
First, get the business running again
Before thinking about recovering anything, our client needed to be able to keep working. So the team handled the most urgent part first: getting our client back on their feet, which was done quickly. The provider heard us and unlocked the domain name. A first small win.
Then, the long fight
That said, the game isn't won yet. We still haven't received the invoice, and we don't have control of the domain. The account it's tied to no longer exists, the associated email address depends on the domain itself, and the provider doesn't seem in any hurry to get back to us.
So we did what we do in situations like this one: we documented. Every exchange, every date, every ticket number. We built the proof of ownership piece by piece, with the business registry, the domain's history and screenshots of the site. We rewrote our requests to make them clearer, more precise, harder to ignore.
One ticket. Then a second. A third. A fourth. We tried every possible route in the hope of talking to someone. In the age of chatbots, where are the humans who can actually help? Weeks of silence between replies, and replies that fixed nothing. What we thought would be a formality of a few days stretched out over several months.
And we keep following up. The countdown is on: the provider reactivated the domain for one year only, which gives us one year to take back control. Don't worry, our client isn't feeling any of it: since the domain was reactivated, everything works normally on their end. But we know it isn't settled yet.
Why we keep pushing
That domain is their company's identity. It's the address their customers know by heart, the one printed on their business cards, their invoices, their vehicles. It's over 20 years of online reputation. It's not a technical detail you can swap out without consequences.
And that's the whole difference between closing a ticket and supporting a business.
When we sit down with you, we're not only committing to delivering a tool.
We're committing to being there when things break, even when the solution is in someone else's hands, even when it takes months, even when the other side doesn't answer.
What we take from it
Let's be honest: if we ended up here, it's also because a detail slipped through the cracks. A domain that should never have stayed tied to an old account. That kind of mistake, we own it, and above all, we learn from it. Today, we come out of it stronger, and we keep moving forward.
We're still on it
As we write this, the case isn't fully closed. We don't know yet how many follow-ups it will take. What we do know is that we'll make every single one.
Because at Devsights, we never let go.
-ÈL
