A hosting suspension creates two immediate business questions: who can restore the website, and what must happen before the host will allow it back online? Start by getting the host’s requirements in writing. If you need a developer to coordinate the technical work, our hacked website repair service explains how an assessed recovery scope can be organised.
The suspension notice is a starting point for investigation. It may describe malware, harmful redirects, abuse, or a different account issue. A website being unavailable does not, by itself, establish what caused the problem.
Ask the host for an actionable handover
Send one organised request rather than several separate support messages. Ask for the incident reference, the reason for the restriction, and the evidence the host can share with your appointed repair provider.
Useful questions include:
- Which domain or hosting account is affected?
- Does the restriction cover only the website, or also email and other services?
- What indicators were found, and when were they detected?
- Can your developer review the affected environment through the host’s approved process?
- What evidence must be supplied before reinstatement is considered?
- Who makes that decision, and where should the repair summary be submitted?
Keep the answers together. They help a repair provider distinguish work they can perform from decisions controlled by the hosting company.
WordPress recommends involving the host because a suspected compromise can involve the wider hosting environment, and the provider may help distinguish a security incident from a service interruption. Its official hacked-site guidance provides useful context for that conversation.
Agree on the business priorities before repair starts
Tell the repair provider which parts of the site matter most: enquiry forms, bookings, product information, or customer account access. Explain whether the website and business email share a provider. These details affect the verification plan and the people who need to be involved.
Agree on one person who can authorise changes, one person who communicates with the host, and a place for progress notes. If your team already has a developer, clarify whether the repair specialist will investigate, implement changes, or review someone else’s work.
Our first steps after a suspected website hack can help you prepare a clear brief without making speculative changes.
Check the proposed recovery scope
A useful proposal should describe what will be assessed, what evidence will be preserved, how changes will be checked, and what happens if the investigation discovers a wider problem. Ask how the provider will evaluate a backup before treating it as a recovery option. A backup can contain the same infection or an unresolved weakness.
Avoid accepting a proposal solely because it promises to put the homepage back online. Ask about the important page types and business functions that will be checked, the limits of any scanner, and how findings and unresolved questions will be documented.
Use our WordPress malware removal quote checklist to compare proposals on the same basis.
Separate repair, reinstatement, and search warnings
Agree on three separate outcomes: the repair work completed by the developer, the host’s decision about reinstatement, and any outstanding warning review with the relevant provider. An update from one party should not be presented as approval from another.
Google’s guidance on dangerous-site warnings explains that warnings may appear in search results or a browser. A hosting suspension notice is a different piece of evidence and should be tracked separately.
Where Search Console lists security issues, Google’s Security issues report guidance says the issues must be addressed throughout the site before a review is requested. A host reopening access does not complete that process.
If a security warning remains after the repair, our guide to Google security warnings after cleanup explains the next review questions.
Ask for a handover you can use
Request a written summary of the work, verification performed, remaining limitations, and recommended follow-up. If the original entry point cannot be established from the available evidence, the report should say so.
Then decide who owns routine checks and recovery testing through a website maintenance plan. Ongoing care is a separate decision from the immediate repair.
ARKIELLO is based in Tagaytay and works with local and international clients. Send us the website address and the host’s notice, with sensitive details removed. We can discuss an appropriate hacked website repair assessment before a repair scope is agreed. Do not include passwords or secret keys in the enquiry.