If you’re wondering what to do if your business website is hacked, start by treating unusual redirects or a security warning as a possible incident, not a confirmed diagnosis. The priority is to protect visitors, avoid destroying evidence, and get help from your hosting provider or a qualified response professional.
A warning can also stem from a certificate, DNS, hosting, or configuration problem. Avoid assumptions and rushed cleanup. The steps below can help you respond methodically, including when your site runs on a Linux server or redirects only for certain visitors.
Protect visitors and contain the problem
Record what you see before changing the site. Note the affected page, the exact destination or warning, when it happened, and how you reached the page. Save a screenshot if you can do so safely. Don’t ask employees or customers to keep clicking a suspicious link to reproduce the behavior.
If visitors are being sent to an unexpected or potentially harmful destination, contact your hosting provider promptly. Ask about temporarily restricting public access or placing the site in maintenance mode while the issue is assessed. If you do not know how to do that safely, ask the host or a qualified incident-response professional to guide the change.
Containment should reduce risk without unnecessarily erasing evidence. Avoid deleting unfamiliar files, restoring a backup, reinstalling the website, or rebooting the server before discussing the situation with the host or responder. A hasty change can make it harder to understand what happened or whether the problem is resolved.

Identify what kind of warning or redirect you’re seeing
Write down the exact browser message and the address shown in the browser. A website security warning does not automatically mean malware is present. Certificate problems, domain or DNS changes, and hosting configuration issues can also affect access. Ask your host to check the certificate status and relevant domain, DNS, CDN, and hosting configuration.
Redirects can be conditional. The behavior may differ by device, browser, network, or the page that referred the visitor. Record any differences you have already observed, such as whether the issue appeared on a phone or after following a search result. Do not repeatedly visit a suspicious destination just to test it. Share the observations with your host so they can investigate in a controlled way.
If your site is listed in Google Search Console, review its Security Issues report for reported security problems and the instructions for addressing them. A report is one useful source of information; it does not replace checking the website, hosting environment, and exact browser warning.
Preserve logs and other useful evidence
Before cleanup begins, ask your host or responder how to preserve relevant records. Depending on your setup, useful evidence may include web-server access and error logs, authentication records, hosting control-panel activity, DNS and CDN logs, and content-management-system audit records. On a Linux-hosted site, the relevant records and locations depend on the server and hosting configuration.
- Record when the issue was first noticed and the time zone used.
- Save the affected URLs, warning text, screenshots, and observed redirect destinations.
- Note which devices, browsers, networks, or referring pages were involved, if known.
- Ask the host to preserve relevant logs and snapshots before making changes.
- Keep a record of who made changes and when, including any action taken by the host.
Limit access to saved evidence to the people handling the incident. If you need to learn more about maintaining Linux systems safely, see our guidance on planning Linux security patches. During an active incident, though, coordinate changes with the host or responder rather than starting routine maintenance on your own.
Contact the host before attempting malware removal
Tell your web host what visitors experience, when it began, and what you have already observed. Ask whether it can preserve logs, check for unauthorized changes, and help determine whether the issue involves the website, server, DNS, CDN, or certificate configuration. If the host cannot investigate the incident, ask who should handle response and evidence preservation.
Do not rely on a quick scan or a single removed file as proof that the site is clean. A responder may need to investigate accounts, website files, server configuration, and other connected components. Follow an agreed cleanup and restoration plan, then verify that the original issue no longer appears before returning the site to normal use.
If the site runs on Linux, its support status and patching approach matter to follow-up security work. Our articles on checking whether a Linux server is supported and business network security practices offer related background, but they are not substitutes for incident-specific help.
For a WordPress site, use guidance that matches the platform and coordinate changes with your host. The WordPress.com hacked-site guide describes steps for WordPress.com sites; hosting arrangements and site configurations can differ, so confirm which instructions apply before acting.
Plan the next steps for sensitive or regulated information
If the website handles patient, financial, or other sensitive information, promptly involve the appropriate security and organizational leads. For a healthcare business, that includes the people responsible for privacy and security. Have qualified internal or external advisors assess what information may have been affected and whether any duties apply. Do not assume that a redirect alone proves data was exposed, or that the absence of a visible redirect proves it was not.
After the immediate issue is contained and evidence is preserved, use a coordinated plan to remove the cause, restore from a trusted source if appropriate, update affected systems, and verify the site before reopening it. CISA’s incident and vulnerability response playbooks provide broader response context; your organization’s systems and responsibilities will determine the right actions.
Frequently asked questions
Should I take my website offline if I think it has been hacked?
If visitors may be exposed to harmful redirects or content, ask your host or responder promptly about restricting access or using maintenance mode. Avoid taking technical steps you cannot safely reverse, and coordinate containment with the people investigating.
How can I tell whether a security warning means my site was compromised?
Capture the exact warning and ask your host to check the certificate, DNS, hosting, and site configuration. A warning warrants investigation, but it does not alone establish that malware or unauthorized access is present.
What if the redirect happens only for mobile visitors or search referrals?
Record the device, browser, network, page, and referral path associated with what you observed. Avoid repeatedly opening suspicious links; share those details with your host or responder for controlled testing.
How do I remove a Google Safe Browsing warning?
First investigate and fix the underlying issue. If Google Search Console reports a security issue, follow the report’s guidance for addressing it and requesting a review. Do not request review before the site has been checked and corrected.
Respond carefully, then verify
A redirect or browser warning calls for prompt, careful investigation, not guesswork. Protect visitors, preserve relevant evidence, and involve your hosting provider before attempting cleanup. Zevonix provides website management and security, cybersecurity, and managed IT services for businesses in Daytona Beach and surrounding Volusia County. Contact Zevonix to discuss your website’s security and support needs.