Website Hacked? Who to Report It To, in Order
If your website was hacked, report it in this order: your hosting provider (or domain registrar), Google, your payment processor if customers' payments could be affected, and then law enforcement or your national CERT. Save your evidence first, because cleanup can erase it.
This guide is for owners of small websites (WordPress, Shopify, indie SaaS, local businesses) who just found something wrong and don't know who to call. You'll get a short evidence checklist, a reporting order you can follow today, and a message template for each recipient. If you need broader cleanup help, see our website hacked guide.
A quick definition: a CERT (Computer Emergency Response Team) is a national or regional team that takes cyber incident reports and helps coordinate a response.
Step 0: Stay calm and collect evidence first
Take 15 minutes before you delete anything. Hosts, banks and police all ask the same questions, and good notes get you faster help. If your checkout page is skimming card details or the site is actively spreading malware, put the site in maintenance mode first (Step 0.5), then collect evidence.
Evidence checklist:
- Screenshots of the defaced page, spam pages, redirects or browser warnings. Include the full address bar and the date and time.
- The exact URLs affected, copied into a text file.
- When you first noticed it, and when the site last looked normal.
- A list of recent changes: new plugins, theme updates, new admin users, password resets.
- Any alert emails from your host, Google, Stripe, PayPal or Shopify.
- A copy of your server's access and error logs (ask your host if you can't find them).
- A backup copy of the hacked files, kept somewhere safe and untouched.
If you have command-line (SSH) access, these two commands help. Replace the path with your site's folder.
find /var/www/html -type f -mtime -7 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r | head -50
tar -czf ~/evidence-$(date +%F).tar.gz /var/www/html
The first lists the 50 most recently changed files from the last 7 days. The second makes a dated archive. Download the archive and keep it offline.
Keep this archive private. Do not email it. Hand it only to your host or investigators if they ask, and rotate those credentials afterward. The web folder usually contains config files with database credentials (for example, wp-config.php on WordPress).
On WordPress with WP-CLI, wp core verify-checksums compares core files with the official versions. wp user list --role=administrator shows admin accounts, so you can spot ones you didn't create.
Never put passwords in a report. Describe what happened, not your credentials.
Step 0.5: Contain the damage
Do this from a device you trust, not one that might be infected.
- Change passwords for your host, domain registrar, CMS admin, database, FTP/SSH and email. Turn on two-factor authentication (an extra code besides your password).
- Remove admin users you don't recognize, but write them down first.
- Put the site in maintenance mode, or ask your host to suspend it, if it is serving malware or stealing data.
Who to report to, at a glance
| Order | Who | Report when | What they can do |
|---|---|---|---|
| 1 | Hosting provider or registrar | Always | Isolate the account, share logs, restore backups, fix DNS |
| 2 | You see a browser warning or spam in search results | Review and lift the warning after you clean up | |
| 3 | Payment processor | Checkout, card data or payouts may be affected | Watch for fraud, advise on card-data rules |
| 4 | Law enforcement or national CERT | Money lost, customer data exposed, or you want it on record | Log the crime, share threat info |
If your checkout page was changed, move the payment processor up to step 2. Card data is the most time-sensitive part.
1. Report to your hosting provider or registrar
Your host runs the server your site lives on. Your registrar is where you bought the domain name. Most owners need the host first. Contact the registrar first if your domain now points somewhere else or your DNS records changed.
Not sure which one it is? Check your name servers, address records and registrar:
dig +short NS example.com
dig +short A example.com
whois example.com
The name servers show who runs your DNS, which is not always your host or registrar. In the whois output, look for the "Registrar" line.
An A record (the IP address your domain points to) that you don't recognize is normal if you use a CDN (a content delivery network), Cloudflare or Shopify. Compare it with what your host or DNS panel shows before assuming tampering.
Website hacked on GoDaddy? Sign in to your GoDaddy account and open the Help or Support area to reach chat or phone. Tell them your site is compromised and ask whether your plan includes malware scanning or cleanup. GoDaddy sells a separate website security product, so check what you actually bought before you pay for more. The same approach works with most hosts, such as Bluehost, SiteGround, WP Engine or Hostinger.
Template for your host or registrar:
Subject: Urgent: my website appears to be compromised (example.com)
Hello,
I believe my website example.com (account/order #12345) was hacked.
I first noticed it on [date, time, timezone]. What I see: [defaced page /
spam pages / unknown redirects / unknown admin user].
Could you please:
1. Check the account for malware and unauthorized access.
2. Send me the access and error logs for [date range].
3. Tell me if a clean backup from before [date] is available.
4. Confirm whether other sites on the same server are affected.
I have changed my passwords and saved screenshots and file copies.
Thank you,
[Name, phone, email]
2. Tell Google (and fix the warning)
Google can't clean your site, but it controls the red warning screens and spam in search results. Use Google Search Console (a free tool that shows how Google sees your site).
- Verify your site in Search Console.
- Open Security & Manual Actions, then Security issues.
- Read what Google found, clean the site, then click Request review.
Google explains the full process in its hacked sites documentation.
If a copycat or phishing page is impersonating your business on another domain, report it through Google's Safe Browsing report page.
Template for the review request box:
The hacked content on example.com was caused by [outdated plugin / stolen
admin password / etc.]. On [date] I removed the malicious files and spam
pages, updated all software, removed unknown admin users and changed all
passwords. The site is now clean. Please review and remove the warning.
Only submit this once the site is actually clean. A rejected request can slow things down.
3. Tell your payment processor
Contact Stripe, PayPal, Square, Shopify Payments or whoever handles your payments if any of these are true:
- Your checkout page or payment form was changed.
- You see unexpected orders, refunds, payouts or new API keys.
- Customers report card fraud after buying from you.
If you take card payments directly, your merchant agreement and card-brand rules (the PCI DSS standard is part of this) expect you to report suspected card-data compromise to your processor. Redirecting buyers to a hosted checkout page, like Stripe Checkout, reduces the data that touches your site, but you should still report a tampered page.
Also rotate your payment API keys from the processor's dashboard.
Template for your payment processor:
Subject: Possible website compromise affecting my merchant account
Hello,
My website example.com (merchant ID: [ID]) was compromised on or around
[date]. [My checkout page was / may have been] modified between [date] and
[date]. I have rotated my API keys and secured the site.
Please advise on: (1) any unusual activity on my account, (2) whether I need
to take further steps, and (3) who to contact about affected customers.
[Name, business, phone, email]
4. Report to law enforcement or your national CERT
This step creates an official record. It may help with insurance claims, bank disputes and client questionnaires. It also helps agencies spot patterns across many victims. Don't expect police to clean your site or recover your data.
- United States: file a complaint at the FBI's Internet Crime Complaint Center (IC3). You can also report an incident to CISA at cisa.gov/report.
- United Kingdom: report fraud and cyber crime to Action Fraud (check police.uk for the current name and address, as the service is being renamed Report Fraud). Scotland: Police Scotland. The NCSC site has guidance for small businesses.
- Australia: use ReportCyber at cyber.gov.au.
- Elsewhere: find your country's CERT in the FIRST team directory, or search for "[your country] CSIRT report incident."
Template for a police or CERT report:
My business website example.com was compromised on or about [date].
Impact: [defacement / malware / stolen data / financial loss of $X].
What I observed: [short factual summary].
Steps taken: changed credentials, contacted hosting provider [name],
saved logs and screenshots.
Evidence available on request: screenshots, server logs, file archive.
Contact: [name, phone, email]
Don't forget your customers and the law
If customer personal data may have been exposed, you may have a legal duty to notify people or a regulator. Under the EU's GDPR, for example, Article 33 requires many organizations to notify the supervisory authority within 72 hours of becoming aware of a breach, where feasible, unless the breach is unlikely to result in risk to people. Other countries and US states have their own rules. This isn't legal advice, so ask a lawyer if personal data is involved.
Find out how they got in
Reporting is half the job. If you only restore a backup, the same weakness can let the attacker back in. Common causes include outdated plugins, reused or weak passwords, and exposed admin panels. Not sure where to start? Read our guide on whether your website is hackable or run the free website security check for a quick outside look.
Key takeaways
- Save screenshots, logs and a file copy before you clean anything.
- Report in this order: host or registrar, Google, payment processor, then police or your national CERT. Report to your payment processor sooner if checkout was touched.
- Change passwords and turn on two-factor authentication from a clean device.
- Only ask Google for a review after the site is truly clean.
- If customer data was exposed, check your legal notification duties.
What to do next
Reporting tells people what happened. It doesn't tell you how the attacker got in or what else is weak. A human-led check can answer that. Our Circuit audit is $49 one-time: a real security engineer reviews your site by hand and writes up every issue with evidence and exact fixes. It's a focused small-site audit, not a multi-week enterprise pentest or a compliance certification. If it fits, it's a sensible next step.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing