When a customer's website goes down, the first question is always: is it the domain or the hosting? If you automate the wrong recovery workflow, you could waste hours or even lose the domain. This guide shows you how to tell them apart and what to automate for each.

What is the difference between a domain renewal failure and a hosting payment failure?

A domain renewal failure means the domain name itself wasn't renewed, so the DNS stops resolving. A hosting payment failure means the server or hosting account wasn't paid, so the website files aren't served. They look similar from the outside but require different fixes.

Domain failures are managed by the domain registrar and the registry. Hosting failures are managed by your hosting provider. Knowing which one failed tells you where to send the recovery request.

How can you tell if a domain renewal failed?

Check the domain's RDAP or WHOIS record. After an expiry, a domain usually moves through the statuses autoRenewPeriod (the grace period), redemptionPeriod and pendingDelete, although some registrars put it on clientHold sooner. You can also run a DNS lookup: if the domain has no nameservers or returns NXDOMAIN, it's likely a domain issue.

Another sign: the customer's email still works but the website doesn't. That's because email might be hosted elsewhere or on a different server. If the domain itself is down, everything using that domain will fail.

How can you tell if a hosting payment failed?

If the domain resolves correctly (you can ping it or get an IP), but the website shows an error like 'connection refused' or 'server not found', the hosting is the problem. The domain is fine; the server isn't responding.

Check the hosting account's status in your billing panel. If it's suspended, that's a hosting payment failure. You can also check the server's error logs for suspension notices.

What are the recovery workflows for each failure type?

Domain renewal recovery

If the domain is in the grace period (often 30 to 45 days, depending on the registry and registrar), you can renew it at the regular price. In the redemption period (about 30 days for most generic TLDs) you can still recover it, but the registrar charges a redemption fee. After that, a few days of pendingDelete follow and the name is released.

Automate: send a payment reminder, automatically attempt renewal if payment method is on file, and escalate to a manual review if the domain enters redemption.

Hosting payment recovery

Most hosting providers suspend the account but keep the data for a period you set and state in your terms. You can unsuspend once payment is made.

Automate: send a payment reminder, suspend the account gracefully, and provide a self-service reactivation link. If payment isn't made, keep the data disabled for your retention period and ask a person before anything is deleted.

How can you automate these workflows to avoid service interruptions?

Run the two recoveries separately. Your billing system should check domain status through your registrar's API and account status through your hosting control panel. Teculiar does this through modules for Virtualmin, cPanel & WHM and Hetzner Cloud, and for the registrars Resell.biz and Dynadot.

Set up rules: if a domain's expiry date is close, trigger a renewal attempt. If a hosting account is suspended, trigger a payment reminder. Use webhooks to notify you when status changes.

Test your workflows regularly to ensure they work. For example, simulate a domain expiry and a hosting suspension in a test environment.

What should you do when both fail at the same time?

If both fail, fix the domain first because it's the foundation. If the domain is gone, the hosting doesn't matter. Renew the domain, then handle the hosting payment.

Communicate clearly with the customer: explain both issues and the steps you're taking. This builds trust and reduces support tickets.

What to do next

  • Check your current billing system: does it differentiate between domain and hosting failures?
  • Set up separate triggers for each failure type in your automation platform.
  • Document your recovery workflows and train your support team.
  • Review your domain registrar's API and hosting control panel's API to enable automation.

Now that you know how to distinguish the two, you can automate the right recovery workflows and keep your customers online.