Suspended does not always mean the same thing
A hosting subscription, mailbox, domain registration or individual website can each be restricted independently. Check the service status and notices in Client Area before changing DNS or reinstalling anything.
Common causes
Match the notice to the affected service
- Invoice overdue
- Open the related invoice and complete payment. UKC never automatically charges a stored card.
- Storage or resource limit
- Remove unnecessary data safely or upgrade the service. Check mailboxes, backups, logs and website files.
- Malware, spam or abuse
- Stop the unsafe activity and preserve evidence. A compromised site must be cleaned before restoration.
- Registrant email not verified
- Complete the ICANN verification request and use the Client Area check-again action.
- Domain expired
- Renew through the domain-renewal cart if the registry still permits recovery.
- Application maintenance mode
- The hosting may be active while WordPress or another application intentionally displays a holding page.
Recovery sequence
Resolve the reason, then verify every dependent service
- Open Client Area and identify the exact domain, hosting or mailbox status.
- Read the associated invoice, resource or security notice.
- Complete only the stated action; do not move DNS as a substitute for resolving suspension.
- Allow the control panel to update, then test the website, Plesk and mail separately.
- If the account is paid but remains suspended, give support the invoice and service IDs.
Resource suspension
Reduce usage without deleting business data blindly
Check which resource is actually full. Old local backups, cache files, logs and deleted-mail folders may be removable; website databases, active mail and current backups may not be. Download a safe copy before destructive cleanup.
Hosting limits explainedSecurity suspension
Restoration comes after containment and cleanup
Changing a password alone does not remove malicious files or spam scripts. Secure account, mailbox and application credentials, update vulnerable software, clean the site and explain the corrective action when requesting review.
Confirm the service is genuinely restored
Check the public website from another network, send and receive one email if mail was affected, and confirm Plesk reports normal resource use. DNS and browser caches can briefly retain an earlier result.
Suspension reason still unclear?
Send the affected domain or service ID, exact status and notice, invoice number if relevant, first observed time and corrective action already completed. Never include passwords.
Request a service review