Is Clean-MX flagging your website or file?
If Clean-MX is flagging your site or a file — often showing up as URL listed as malware or phishing in the Clean-MX realtime database — it is either a real infection or a false positive from a past issue. Here is how to get it cleared.
Step 1 — Confirm it is really a false positive
Do not request removal while malware is still present, or the flag returns. Check first:
- Run my free Is My Site Hacked? checker.
- Cross-check on VirusTotal to see every engine flagging you.
If anything turns up, get it fully cleaned first — deleting the visible malware is not enough if a backdoor remains.
Step 2 — Report the false positive to Clean-MX
Clean-MX delisting is by email after you confirm your listing. Submit here: abuse@clean-mx.de (email)
- Look up your domain/URL in the Clean-MX realtime DB (viruses.php for malware, phishing.php for phishing).
- Clean the site and confirm it no longer serves the flagged content.
- Email abuse@clean-mx.de stating the listing is in error or resolved, with the exact URL and evidence.
- Request review/delisting.
Good to know: Email-only; no self-service form. The lookup pages can be flaky (HTTP 500), but abuse@clean-mx.de remains the official channel.
Step 3 — If the warning keeps coming back
A detection that returns after you have been cleared almost always means the infection was never fully removed — usually a backdoor in a theme file, a rogue admin user, or malware in the database. That is exactly what I fix. I am a USA-based WordPress security specialist: I remove the infection completely, submit the delisting on your behalf, and harden the site so it stays clean.
Get my site cleaned · See how it works · read my client reviews.
Frequently asked questions
How long does Clean-MX take to clear a false positive? Once the site/file is genuinely clean and you have submitted the request, most are resolved within a few days. Submitting while still infected only restarts the clock.
It keeps coming back — why? Because the real infection (a backdoor, rogue admin, or database payload) is still there. A full cleanup stops the loop.