A hosting fault becomes much easier to solve when the exact message, time and last change are written down. For “WordPress site hacked through old hosting account”, protect the current data first and avoid deleting the evidence that support may need.
The immediate priority is to restore a stable service without making data loss more likely. On WordPress, normal operation involves themes, plugins, scheduled tasks and database-driven pages. Create or confirm a backup, keep the old working state where one exists and use logs or response details to narrow the cause before escalating.
Start with evidence, not random changes
With a problem such as “WordPress site hacked through old hosting account”, the safest first move is to preserve the current state. Take screenshots of the exact message, note when it began, export any logs available and create a backup before editing DNS, deleting files or disabling several components at once. Then decide which layer is failing: the visitor’s device, DNS, SSL, web server, application, database or email service. Check from a second connection and use the supplier’s status page before assuming the entire account is broken. For WordPress, remember that the site generates themes, plugins, scheduled tasks and database-driven pages. Change one variable, retest and write down the result. This slower-looking method is normally faster than making five simultaneous changes and losing the ability to identify which one helped. Escalate with a timestamp, affected address, error text, recent change and tests already completed; that gives support something concrete to investigate.
Narrow the cause without guesswork
If an old hosting account may have been used to compromise a site, preserve logs, place the affected site in a controlled maintenance state and rotate passwords, API keys and database credentials from a clean device. Remove obsolete DNS access and close the old account only after evidence and data are secured. Restore from a known-clean backup and patch the original entry point.
The named platform narrows compatibility requirements. WordPress creates themes, plugins, scheduled tasks and database-driven pages, so confirm managed updates, page caching, staging, security monitoring and restores. Also review supported versions and the process for logs, staging and rollback. A generic one-click installer is not the same as ongoing platform-aware support once themes, extensions or custom code are in use.
Last-change test: List every change since the last known successful use and place them in time order. Start with the one that best matches the first failure. Record the result before making the next change, and keep any successful recovery step for the incident notes.
Preserve the current state, verify an independent backup and locate the failing layer before making one reversible change. For WordPress, use logs and the exact timestamp rather than deleting files or changing several settings together.
Six checks that narrow the fault
External verification
Check from another network and device, and compare public DNS or certificate results. This separates local cache problems from a failure seen by all visitors.
Exact symptom
Record the failing address or action, exact message, timestamp and whether the problem affects every visitor, one device or one network.
Useful escalation
Give support the URL, time, error, recent change, log evidence and tests already performed. Ask what they can see at the account or server layer.
Last known change
List DNS, certificate, plugin, theme, code, password, PHP, database and account changes since the last successful use. Timing often narrows the cause.
Recurrence prevention
After service returns, document the root cause, add monitoring or alerts and record the tested recovery steps so the next incident is shorter.
Recovery consequence
Before restoring or rolling back, decide which newer orders, messages, uploads or edits could be lost and preserve them separately where possible.
A safe four-step diagnosis
- 1
Record the symptom
Capture the address, exact error, time, affected devices and last known successful use. Preserve logs and make a backup before changing configuration.
- 2
Locate the failing layer
Check another network, DNS result, SSL certificate, supplier status, server response and application logs in that order. This narrows the search without guesswork.
- 3
Make one reversible change
For WordPress, disable or alter one likely cause, retest the same action and record the outcome. Restore the previous state when it makes no difference.
- 4
Escalate clearly
Send support a concise timeline, evidence, tests and the result you expected. Ask for a ticket reference and avoid cancelling the service until data is safe.
What a recoverable setup looks like
Good recovery depends on a known-good copy and a known-good test. Keep dated exports outside the hosting account, use staging for risky updates and record which network, URL and action prove that service is working again. Monitoring should alert a person who knows the next step.
Common mistakes to avoid
- Changing DNS, nameservers, plugins and server settings together, then being unable to identify which change caused the result.
- Treating a backup as proven recovery without downloading a copy or completing a test restore.
- Cancelling the old host as soon as files are copied, before DNS, email, forms, redirects and live transactions have been verified.
- Assuming “unlimited” removes all restrictions while overlooking CPU, memory, database, process, mailbox or file-count limits.
Bottom line
Recovery is complete when the original visitor journey works, newer data is protected and the cause is less likely to recur unnoticed. Keep the incident notes with the backup and account-recovery details rather than relying on memory.
Important: Secure a backup and account access before cancelling or moving service. Provider links are affiliate links. Technical steps vary by platform, so check current provider documentation and preserve a rollback route. Read our editorial policy and affiliate disclosure.
Frequently asked questions
WordPress Site Hacked Through Old Hosting Account?
Begin by recording the exact symptom and checking from another device or connection. Review DNS, SSL, supplier status and application logs before making one reversible change at a time.
What information should I send to hosting support?
Send the affected address, exact error text, timestamp with timezone, when it last worked, the most recent change, results from another device or connection, relevant log lines and the reversible tests already completed.
When should I restore a backup?
Restore only after preserving the current state and identifying a suitable known-good copy. Test the restore away from the live site when possible, and take care not to overwrite newer orders, messages or account data.