When using registrar modules like Namesilo, if a user’s domain is suspended (placed in ClientHOLD status) by the registrar due to illegal activities or failed email verifications, we, as the provider, aren’t notified of this suspension. Additionally, the domain doesn’t enter a suspended status in Blesta, which creates problems for providers managing hundreds or thousands of active domains. A significant percentage of these domains may end up suspended by the registrar, but still appear as active in Blesta. This leads to issues such as renewal notices being sent out and users submitting tickets asking why their domains are inaccessible while they still appear as active in their domains tab.

Users may also encounter an error message saying, “Domain is not managed by this user.” It’s challenging to manually go through each domain to cancel them, especially since most suspended domains are due to abuse, making them unlikely to be restored. These domains should ideally be set to suspended and then canceled later.

There’s also the issue of domains suspended due to Whois email verification failures, which can be restored. For these, we could suspend them initially and, if the user contacts us, manually restore them after the email verification is completed. This approach is more efficient than dealing with abuse-related suspensions.

To address this, we need a way to either automatically suspend/cancel domains in ClientHOLD status or set up a manual check to identify such domains. One solution could be performing a Whois check or detecting domains showing the “Domain cannot be managed by this user” error, with the option to bulk cancel those domains.