Last updated 30 August 2026
If you found SiteCheckBot in your server logs, this page is why. It belongs to Scan44, a service that checks a website for security problems and reports them to the person who asked for the check.
Somebody entered your address on our home page and asked for a check. We do not crawl the web, we do not keep a list of sites to visit, and we never visit a site that has not been typed into that box. If your site was checked, a person asked for it.
We do not verify that the person owns the site. There is no way to do that before making the first request, and we would rather say so than pretend otherwise. What we do instead is limit the damage: every check is passive, and the results go only to whoever started it.
It makes the same kind of requests any visitor's browser makes, reads the replies, and looks up public DNS records. Around sixty requests over about half a minute, spread out rather than sent at once.
It does not:
It reads what your server already hands to anyone who asks. If a file is downloadable without a login, we can download it, which is the entire point of telling you about it.
If your site answers with 429 or 503, we stop probing and honour the wait you ask for. That is deliberate: a check that knocks a small server over is worse than no check at all. If you are still seeing more traffic than you want, write to us and we will look at it the same day.
You have three ways, and all of them work:
SiteCheckBot/1.0. Block it in your firewall, in Cloudflare, or in robots.txt. Our scanner is not a search crawler, so blocking it costs you nothing anywhere else.A site on that list stays off it. We do not ask you to renew the request and we do not remove it when a customer types your address in.
The results of a check, so the person who asked for it can come back to their report. An unpaid check is deleted after two days, a paid one after ninety. We do not build a database of scanned sites and we do not sell anything to anyone.
The full detail is in our privacy policy.