- Home
- Technical and performance
- Malware Checker
Malware Checker
Check whether Google considers a site dangerous, and what your visitors see.
A query to the Google Safe Browsing API, the database that feeds the warnings in Chrome, Firefox and Safari. Free, with no usage limit.
What this tool is for
Google maintains a database of addresses judged dangerous. It feeds the full-page warnings in Chrome, Firefox and Safari — that red screen warning the visitor before the site even displays.
Appearing in it is the most brutal sanction on the web. Traffic does not decline gradually: it stops. Search results show a warning, browsers block access, and nearly every visitor gives up.
The most disconcerting part is that you rarely learn it yourself. The site works normally for its owner — often logged in, often on a cached address — and the flag is discovered through a worried customer.
A check to run before buying a domain too: a flag travels with the domain name. An apparently attractive second-hand domain can arrive with that inheritance.
How to read the results
No threat detected means the address does not appear in the database. Reassuring without being a guarantee: Safe Browsing detects what is known, not what has just arrived.
Malicious code is the verdict when code meant to infect visitors is present. On a legitimate site that almost always results from a compromise through an unmaintained plugin.
Phishing signals a page built to capture credentials. On a hacked site, attackers often create pages imitating a bank in a discreet subfolder, invisible from normal navigation.
Social engineering designates deceptive content more broadly: fake download buttons, false alerts. That flag sometimes hits healthy sites where a third-party advert serves that kind of content — check your ad networks.
Unwanted software targets downloads that install something other than what they claim. Mostly concerns sites offering files.
Common mistakes
Requesting a review before cleaning up. A refusal lengthens the wait for later requests. Clean completely, check, then ask.
Removing the malicious code without closing the way in. If the flaw exploited is not fixed, reinfection follows within days. Update the core, the plugins, and change every credential.
Checking only the home page. Malicious pages are generally hidden in subfolders to delay discovery. Check the sections you never visit too.
Believing you are safe because the site is small. Compromises are automated: bots crawl the web looking for known vulnerable versions, with no regard for size or audience.
Neglecting prevention after cleaning up. A site already compromised is often targeted again. Security headers and a policy of regular updates markedly reduce the risk of a repeat.
Going further
- Blacklist CheckerPresence in spam blacklists
- Security Headers CheckerAudit the five HTTP headers that protect your visitors
- SSL Certificate CheckerValidity, chain of trust and expiry date of a certificate
- HTTP Status CheckerResponse code and availability
Frequently asked questions
My site is flagged, what do I do first?
Do not request a review before cleaning up: a refusal lengthens the handling time of later requests. Start by identifying and removing the malicious code, change every password, update the core and the plugins, and only then request the flag be lifted through Search Console.
How long does it take to lift a flag?
Generally twenty-four to seventy-two hours after an accepted review request. But traffic does not come back instantly: the warning stays cached in browsers for a few hours, and visitors’ trust takes longer to rebuild.
Does a clean result guarantee my site is healthy?
No, and that matters. Safe Browsing detects what is already known and catalogued. A recent infection, or code that only fires for certain visitors, can go unnoticed. A clean result means “nothing known”, not “nothing at all”.
How does a site get infected?
In the vast majority of cases through an unmaintained plugin or theme carrying a publicly documented flaw. Then come weak or reused passwords, and compromised FTP credentials. Sophisticated attacks on small sites are rare.
What does “social engineering” mean in the verdict?
That the site is flagged as deceptive: a page imitating a known service to capture credentials, or a disguised download button. That flag sometimes hits legitimate sites where a third-party advert displays that kind of content. Check your ad networks before concluding you were hacked.
Does a flag affect my positions?
The effect is far more brutal than losing positions. Chrome, Firefox and Safari display a full-page red warning before access, and Google marks the result as dangerous. Traffic does not fall, it stops.