Grok Log Checker

Paste lines from your server access log to find requests that use the reported xAI crawler names, GrokBot and xAI-SearchBot. See which IPs sent them and how often, so you can tell a steady crawler from someone borrowing the name. Everything runs in your browser; nothing is uploaded.

Tip: grep -iE "grok|xai" /var/log/nginx/access.log | tail -5000 gives you a manageable sample.

How to read the result

  • A few IPs, steady traffic. Consistent with a real crawler. Without published ranges from xAI you still cannot confirm it.
  • Many unrelated IPs, or bursts on one URL. Looks more like someone using the name as cover. Rate limit rather than trust it. See spoofed AI crawlers.
  • "Other xAI or Grok mention". A user agent mentions Grok, xAI or x.ai but is neither reported name. Treat it with care: no xAI source documents it.
  • Twitterbot. Builds link previews on X. It is not Grok, and blocking it breaks how your links look when shared.

To allow or block these names, use the Grok presets in the robots.txt generator, and read the Grok crawler user agent guide.

Frequently asked questions

Are my logs uploaded anywhere?

No. The checker runs entirely in your browser. Nothing you paste is sent to our servers or stored.

Can this prove a request came from xAI?

No. xAI publishes no IP ranges or reverse DNS pattern for GrokBot or xAI-SearchBot, so anyone can send those names. The checker shows which IPs used them and how often, which helps you spot impostors, but it cannot confirm the sender.

Will it find Grok Bot, the agent?

No. Grok Bot browses with an ordinary browser user agent and sends no xAI name. It can only be identified by the shared IP ranges xAI gives to its customers, which are not public.

What log formats does it read?

Any line that contains the user agent, including the common Nginx and Apache combined formats, where the user agent is the last quoted field and the client IP is the first field.