Bad bot detection

See every bad bot that hits your site, and where it comes from

Fake Googlebots, scrapers, login probes and the bots that ignore your robots.txt, with the IPs, networks and countries behind them, straight from your server logs.

Get a demo

Free audit, no account needed. HoneyLog adds no JavaScript tag.

Malicious & suspicious bots

Unmask fake crawlers and unverified bots

Bad bots love a trusted name: they call themselves Googlebot or GPTBot to get through. HoneyLog checks every bot that claims a known identity against the IP ranges its company publishes, and labels the rest.

  • Fakes labeled malicious. A Googlebot or GPTBot from outside its company's IP ranges is a malicious bot, never counted as the real one.

  • Unverified bots, suspicious. Scrapers and tools that can't be verified, with the pages they hit and how often.

  • Where they come from. Datacenter, VPN, network and country for every bad bot, so you know what to block.

Example data

Real Time Logs

Watch the probes, and the IPs behind them

Most attacks start with a scan: logins, admin panels, config files, old plugins. HoneyLog shows every request as it reaches your server, so you see the scan while it runs and the IPs running it.

  • Every request, live. Time, IP, country, bot, URL and status code for each request of the last few days.

  • Top IPs and URLs. The addresses sending the most requests and the paths they keep hitting.

  • One IP, all its requests. Filter on an address to see everything it asked for, before you block it.

Example data

Robots.txt

Catch the bots that ignore your rules

Your robots.txt tells bots what to leave alone. Not every bot listens. HoneyLog checks every verified bot request against the robots.txt version that was live at that moment.

  • Every violation. Which bots fetched the paths you disallowed, how many times, and what your server answered.

  • Fair to the bots. After each change of your robots.txt, bots get 24 hours to read the new rules before a hit counts against them.

  • A record you can export. The violations per bot and per URL as CSV, for your security team or your legal one.

Example data

Questions about bad bots

No. HoneyLog is an analytics tool, not a firewall: it shows you which bots attack or probe your site, from which IPs, networks and countries, and what they asked for, so you can block them in your CDN, firewall or server. Then it shows you whether the block worked.

By checking every request that claims to be a known bot against the IP ranges its company publishes. A Googlebot or GPTBot from outside Google's or OpenAI's ranges is labeled a malicious bot. Bots that can't be verified at all are labeled suspicious, so you see them apart from the verified crawlers you want.

Yes. Real Time Logs lists the requests of the last few days with their time, IP, country, bot, URL and status code, and ranks the top IPs of the period. Filter on one IP to see everything it asked for, or on one path to see who keeps hitting it. (HoneyLog saves IPs only if the visit comes from a bot or an AI crawler: by default, HoneyLog does not save the IPs of human visitors, out of respect for privacy rules.)

Yes, by email. The malicious traffic alert fires on requests from bots pretending to be a known crawler, and the bot traffic spike alert fires when bot requests jump within an hour. Both can be filtered on the paths you care about, such as your login pages or your API.

No, it works next to them. A WAF blocks requests and a SIEM collects security events from many systems. HoneyLog shows, in clear dashboards, who is behind your traffic: humans, verified bots, suspicious and malicious ones. That makes it easier to write the right firewall rules and to check, afterwards, that they work.

More answers in the HoneyLog FAQ

Free AI audit

Your logs already know which bots are bad

Check how AI crawlers see your site in a minute, or book a demo and see HoneyLog with our team.

Get a demo

Free audit, no account needed. HoneyLog adds no JavaScript tag.