Industries / Technology / Software and SaaS / Cloud and data centers / Web hosting
Customer support
Helping customers when something goes wrong: answering questions, telling them what is down, recovering lost data, accounts and lapsed domains, and moving them to another company.
5
Milestones achieved, from 2013 to 2026.
1
To watch for: announced, not yet confirmed outside.
3
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
2013
Rules for expired domains
From 31 August 2013 ICANN, the body that coordinates domain names, required every accredited registrar of generic domains such as.com to follow its Expired Registration Recovery Policy (ERRP). Registrars must remind the owner about a month and about a week before a domain expires, and again within five days after. For at least the last eight days that a lapsed domain can still be renewed, its website and email must stop working, so the owner notices, and any page shown there must say that the domain has expired and how to renew it. After deletion, most registries must hold the name for a 30-day Redemption Grace Period, during which the former owner can still restore it. Registrars must publish their renewal and restore fees. The policy began with a request from ICANN's At-Large Advisory Committee, which speaks for individual internet users, and a 2008 report. ICANN's compliance team handles complaints under it: in April 2026 it closed four after the registrar showed it had complied and one after the registrar corrected a breach.
Credit
ICANN (At-Large Advisory Committee; Generic Names Supporting Organization)
2016
Rules for moving a domain
ICANN's Transfer Policy, with which registrars had to comply by 1 December 2016, sets how an owner moves a domain from one registrar to another. The current registrar must hand over the domain's transfer code (called the AuthInfo code) and remove any transfer lock within five calendar days of the owner's request. It may not refuse just because the owner and registrar dispute a payment. If it does not answer the registry within five days, the transfer goes through. A change of owner can bring a 60-day lock on transfers unless the owner opts out beforehand.
Credit
ICANN
2020
Support staff tricked into handovers
In March 2020 a phone scam aimed at GoDaddy's support employees let attackers take control of at least six domain names, among them escrow.com; the callers could read notes that staff had left on customer accounts, KrebsOnSecurity reported. In November the same kind of attack hit cryptocurrency firms. The chief executive of the trading platform Liquid said GoDaddy had "incorrectly transferred control" of its account and domain, which let the attacker change its DNS records and take over internal email accounts. The mining service NiceHash froze customer funds for about 24 hours after its domain settings were changed, and said GoDaddy could not be reached at the time because a separate outage had taken down GoDaddy's phone and email. GoDaddy confirmed "social engineering of a limited number of GoDaddy employees".
LessonA help desk that can change a customer's domain is itself a way in, and an attacker needs to convince only one employee.
Credit
Brian Krebs, KrebsOnSecurity (reporting); GoDaddy (confirmation)
2022
Hosted email never comes back
On 2 December 2022 a ransomware attack took down Rackspace's Hosted Exchange email service, used by nearly 30,000 customers. Rackspace said the Play ransomware group got in through a flaw in Microsoft Exchange that Microsoft had listed as a privilege-escalation bug, without noting that it could be chained into a remote attack. Rackspace had held off installing Microsoft's patch for a related flaw, fearing it would cause sign-in errors, and relied on Microsoft's suggested workaround, which the new exploit got around. In January 2023 Rackspace said it would not rebuild the service and offered to move customers to Microsoft 365 at no higher price for the same features. It said more than half of the affected customers could download some or all of their old mail, but fewer than 5% had done so, which it took as a sign that many kept their own copies. Attackers had reached the stored mailboxes of 27 customers.
LessonA host can decide that a broken service is not worth restoring, so customers need their own copy of what it holds.
Credit
Rackspace Technology; reported by The Register and Dark Reading
2026
AI at the front desk
In July 2026 webhosting.today, a trade news site, wrote that most serious hosting companies now put an AI assistant in front of prospective buyers. Hostinger introduced its assistant, Kodee, in a post dated September 2024. That month webhosting.today put the same three questions about a busy online shop to the public assistants of six companies: Hostinger (Kodee), Hetzner, WordPress.com, Hosting.com (Orbi), WP Engine (Walter) and Bluehost. Hetzner's listed nine reasons not to choose Hetzner, each tied to its documentation. WordPress.com's was the most useful. Bluehost's chat window only offered a menu and never took up the question. Asked which rival would suit the shop better, without a list to pick from, every assistant that answered declined to name one.
LessonThe test asked each assistant once, and the site warned that the same question can get a different answer on another day, so a single test is a snapshot.
Credit
webhosting.today (test); Hostinger and the other hosts (assistants)
Watch for
AI closes most support chats
Hostinger says Kodee resolved 91% of roughly 1.5 million support conversations a month on its own. It says that since late June 2026 specialists advise the AI behind the scenes on the roughly one conversation in ten it cannot handle alone, and that in those cases the AI's resolution rate rose from 41% to 72% while requests for live chat fell from 10% to 4.5% of conversations. It gives a median of about three minutes to a solution with this guided AI, against more than 50 minutes in live chat. Its own June 2026 study of 914,300 conversations about virtual private servers shows how much the definition matters: Kodee resolved 91% of the conversations with a recorded outcome, and 69% of all of them if those without an outcome count as unresolved. Hostinger Agent replaced Kodee from mid-August 2026.
Achieved whenan outside party audits a random sample of conversations Hostinger counts as resolved, checks whether the customer's problem was fixed and whether they came back about it, and publishes the rate.
Claimed by
Hostinger, June and September 2026
Open
01
Testing registrars' expiry reminders
A public test of whether registrars do what ICANN's expiry policy requires. Register the same kind of domain at 15 or more registrars, turn off automatic renewal, let each one lapse, and log every reminder (date, channel and wording), when the website and email stop working, what page appears in their place, and the fee asked to restore the domain in the 30-day grace period.
The briefCredit · unclaimed02
An answer key for support
A fixed set of 30 everyday support tasks with checked correct answers, for example which DNS record points a domain at a new server, how to restore yesterday's backup, or why mail from the domain lands in spam. Put them to the support of 15 hosts through every channel each offers, AI and human, from paid accounts on each host's cheapest plan, and grade every answer against the key. Ask each AI assistant each question 20 times, to see how often it is right every time.
The briefCredit · unclaimed03
A stopwatch for moving hosts
A repeatable test of the free migration services that hosts offer. One reference site, a WordPress shop with a few hundred pages, a contact form, email accounts and scheduled jobs, is moved from the same starting host to ten hosts that offer free migration. Monitors in several countries record any downtime during the switch, and a script checks every page, link, form and mailbox afterwards.
The briefCredit · unclaimed
Open 01 · the brief
Testing registrars' expiry reminders
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public test of whether registrars do what ICANN's expiry policy requires. Register the same kind of domain at 15 or more registrars, turn off automatic renewal, let each one lapse, and log every reminder (date, channel and wording), when the website and email stop working, what page appears in their place, and the fee asked to restore the domain in the 30-day grace period.
Why it is still open
ICANN checks registrars by reviewing their documents, data and websites, and acts on complaints one at a time. In its audit round of September 2017 to May 2018 it found expiry-policy deficiencies at 21 registrars, 38% of those audited, without naming them in the results table. In November 2022 its compliance team reported that a common failure was resellers, the companies that sell domains on a registrar's behalf, not carrying out renewal duties. Its April 2026 dashboard lists expiry complaints closed after the registrar showed or restored compliance, and others closed as out of scope because "customer service issues are outside of ICANN's contractual authority". A search found no published side-by-side test of how registrars and resellers handle expiry, seen from the owner's side with real domains.
Built with what exists
domains bought by the builder at each registrar; one email inbox per registrar; dig and RDAP lookups run on a schedule to time-stamp each change; screenshots; a spreadsheet; the policy's text as the checklist.
First step
Register the test domains this month with automatic renewal off, for the shortest term each registrar sells, and record the renewal and restore fees each one publishes.
Done looks like
For each of at least 15 registrars, a dated log for one domain from 35 days before expiry to deletion, scored clause by clause against the policy (reminders at about a month, a week and within five days after; at least eight days of interrupted service while the domain is still renewable; a page saying the domain has expired; fees published), with all evidence published. Results arrive when the first registration terms end.
Open 02 · the brief
An answer key for support
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A fixed set of 30 everyday support tasks with checked correct answers, for example which DNS record points a domain at a new server, how to restore yesterday's backup, or why mail from the domain lands in spam. Put them to the support of 15 hosts through every channel each offers, AI and human, from paid accounts on each host's cheapest plan, and grade every answer against the key. Ask each AI assistant each question 20 times, to see how often it is right every time.
Why it is still open
Outside tests so far are snapshots or impressions. Pick Hosting, a review site, says it filed more than 80 tickets at 12 hosts in the six months before June 2026 and graded each host on "technical accuracy", but it publishes its verdicts, not the questions' correct answers or the transcripts. In July 2026 webhosting.today put three questions once each to six hosts' public assistants and warned that "the same question can draw a different answer from the same assistant on a different day". Hostinger publishes resolution rates for its own assistant with no outside check. A search found no published test that grades hosts' support against an answer key.
Built with what exists
the builder's own paid accounts and a small test site on each host; an answer key checked by two experienced administrators; for the AI assistants, repeated runs graded against the key by an AI model such as Claude or Gemini, with a person settling each disagreement (see the Note "All twenty times" on counting tasks passed on every attempt).
First step
Write the 30 tasks and their answers, have two administrators check the key, and run it against three hosts.
Done looks like
All 30 tasks graded for at least 15 hosts and published with full transcripts: the share answered correctly per host and channel, the time to a first useful answer, and for each AI assistant the share of tasks answered correctly on all 20 tries.
Open 03 · the brief
A stopwatch for moving hosts
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A repeatable test of the free migration services that hosts offer. One reference site, a WordPress shop with a few hundred pages, a contact form, email accounts and scheduled jobs, is moved from the same starting host to ten hosts that offer free migration. Monitors in several countries record any downtime during the switch, and a script checks every page, link, form and mailbox afterwards.
Why it is still open
Hosts promise much and publish no measurements. Kinsta says it will move sites "in less than a day with no downtime"; Cloudways promises "zero downtime". A search found no independent study that measured downtime or breakage across hosts' migration services. Review Signal, whose WordPress hosting benchmarks use outside uptime monitors, tests load, uptime and speed, not migrations.
Built with what exists
WordPress and WooCommerce with sample shop data; uptime monitors such as Uptime Kuma (self-hosted) and HetrixTools, two that Review Signal uses; a link checker; Playwright, a free browser-automation tool, to run the checkout and forms before and after; Browser Use, an open-source browser agent, to compare pages that change in layout (see the Note "Deleting 80% to start over").
First step
Build the reference site and its check script, and run one migration to a host that offers it free.
Done looks like
Ten migrations, each with measured downtime in seconds, the counts of broken pages, links, forms and lost emails, the time from request to finish, and the full logs published.